Bug #1394868: doc typos

Doc/lib/liblogging.tex

@@ -59,7 +59,7 @@ generated. This is the basic mechanism controlling the verbosity of
 logging output.
 
 Logging messages are encoded as instances of the \class{LogRecord} class.
-When a logger decides to actually log an event, an \class{LogRecord}
+When a logger decides to actually log an event, a \class{LogRecord}
 instance is created from the logging message.
 
 Logging messages are subjected to a dispatch mechanism through the

Doc/lib/libstdtypes.tex

@@ -952,8 +952,8 @@ The conversion flag characters are:
              precede the conversion (overrides a "space" flag).}
 \end{tableii}
 
-The length modifier may be \code{h}, \code{l}, and \code{L} may be
-present, but are ignored as they are not necessary for Python.
+A length modifier (\code{h}, \code{l}, or \code{L}) may be
+present, but is ignored as it is not necessary for Python.
 
 The conversion types are:
 
@@ -1606,7 +1606,7 @@ flush the read-ahead buffer.
   defaults to the current position.  The current file position is
   not changed.  Note that if a specified size exceeds the file's
   current size, the result is platform-dependent:  possibilities
-  include that file may remain unchanged, increase to the specified
+  include that the file may remain unchanged, increase to the specified
   size as if zero-filled, or increase to the specified size with
   undefined new content.
   Availability:  Windows, many \UNIX{} variants.

Doc/lib/libsubprocess.tex

@@ -103,7 +103,7 @@ If \var{env} is not \code{None}, it defines the environment variables
 for the new process.
 
 If \var{universal_newlines} is \constant{True}, the file objects stdout
-and stderr are opened as a text files, but lines may be terminated by
+and stderr are opened as text files, but lines may be terminated by
 any of \code{'\e n'}, the Unix end-of-line convention, \code{'\e r'},
 the Macintosh convention or \code{'\e r\e n'}, the Windows convention.
 All of these external representations are seen as \code{'\e n'} by the