#15543: reflow paragraphs.
diff --git a/Doc/library/functions.rst b/Doc/library/functions.rst
index 4383cd4..8d80271 100644
--- a/Doc/library/functions.rst
+++ b/Doc/library/functions.rst
@@ -864,16 +864,15 @@
In addition to the standard :c:func:`fopen` values *mode* may be ``'U'`` or
``'rU'``. Python is usually built with :term:`universal newlines` support;
- supplying
- ``'U'`` opens the file as a text file, but lines may be terminated by any of the
- following: the Unix end-of-line convention ``'\n'``, the Macintosh convention
- ``'\r'``, or the Windows convention ``'\r\n'``. All of these external
- representations are seen as ``'\n'`` by the Python program. If Python is built
- without universal newlines support a *mode* with ``'U'`` is the same as normal
- text mode. Note that file objects so opened also have an attribute called
- :attr:`newlines` which has a value of ``None`` (if no newlines have yet been
- seen), ``'\n'``, ``'\r'``, ``'\r\n'``, or a tuple containing all the newline
- types seen.
+ supplying ``'U'`` opens the file as a text file, but lines may be terminated
+ by any of the following: the Unix end-of-line convention ``'\n'``, the
+ Macintosh convention ``'\r'``, or the Windows convention ``'\r\n'``. All of
+ these external representations are seen as ``'\n'`` by the Python program.
+ If Python is built without universal newlines support a *mode* with ``'U'``
+ is the same as normal text mode. Note that file objects so opened also have
+ an attribute called :attr:`newlines` which has a value of ``None`` (if no
+ newlines have yet been seen), ``'\n'``, ``'\r'``, ``'\r\n'``, or a tuple
+ containing all the newline types seen.
Python enforces that the mode, after stripping ``'U'``, begins with ``'r'``,
``'w'`` or ``'a'``.
diff --git a/Doc/library/io.rst b/Doc/library/io.rst
index bb7c34f..8994086 100644
--- a/Doc/library/io.rst
+++ b/Doc/library/io.rst
@@ -144,10 +144,9 @@
.. index::
single: universal newlines; open() (in module io)
- *newline* controls how :term:`universal newlines` works (it only applies
- to text
- mode). It can be ``None``, ``''``, ``'\n'``, ``'\r'``, and ``'\r\n'``. It
- works as follows:
+ *newline* controls how :term:`universal newlines` works (it only applies to
+ text mode). It can be ``None``, ``''``, ``'\n'``, ``'\r'``, and ``'\r\n'``.
+ It works as follows:
* On input, if *newline* is ``None``, universal newlines mode is enabled.
Lines in the input can end in ``'\n'``, ``'\r'``, or ``'\r\n'``, and these
@@ -765,13 +764,12 @@
``''``, ``'\n'``, ``'\r'``, and ``'\r\n'``. It works as follows:
* On input, if *newline* is ``None``, :term:`universal newlines` mode is
- enabled.
- Lines in the input can end in ``'\n'``, ``'\r'``, or ``'\r\n'``, and these
- are translated into ``'\n'`` before being returned to the caller. If it is
- ``''``, universal newlines mode is enabled, but line endings are returned to
- the caller untranslated. If it has any of the other legal values, input
- lines are only terminated by the given string, and the line ending is
- returned to the caller untranslated.
+ enabled. Lines in the input can end in ``'\n'``, ``'\r'``, or ``'\r\n'``,
+ and these are translated into ``'\n'`` before being returned to the
+ caller. If it is ``''``, universal newlines mode is enabled, but line
+ endings are returned to the caller untranslated. If it has any of the
+ other legal values, input lines are only terminated by the given string,
+ and the line ending is returned to the caller untranslated.
* On output, if *newline* is ``None``, any ``'\n'`` characters written are
translated to the system default line separator, :data:`os.linesep`. If
diff --git a/Doc/library/subprocess.rst b/Doc/library/subprocess.rst
index 9f82323..348c505 100644
--- a/Doc/library/subprocess.rst
+++ b/Doc/library/subprocess.rst
@@ -385,12 +385,11 @@
.. _side-by-side assembly: http://en.wikipedia.org/wiki/Side-by-Side_Assembly
- If *universal_newlines* is ``True``, the file objects *stdout* and *stderr* are
- opened as text files in :term:`universal newlines` mode. Lines may be
- terminated by any of ``'\n'``, the Unix
- end-of-line convention, ``'\r'``, the old Macintosh convention or ``'\r\n'``, the
- Windows convention. All of these external representations are seen as ``'\n'``
- by the Python program.
+ If *universal_newlines* is ``True``, the file objects *stdout* and *stderr*
+ are opened as text files in :term:`universal newlines` mode. Lines may be
+ terminated by any of ``'\n'``, the Unix end-of-line convention, ``'\r'``,
+ the old Macintosh convention or ``'\r\n'``, the Windows convention. All of
+ these external representations are seen as ``'\n'`` by the Python program.
.. note::
diff --git a/Doc/library/urllib.rst b/Doc/library/urllib.rst
index 1cb3faf..2008bdf 100644
--- a/Doc/library/urllib.rst
+++ b/Doc/library/urllib.rst
@@ -32,16 +32,17 @@
.. function:: urlopen(url[, data[, proxies]])
- Open a network object denoted by a URL for reading. If the URL does not have a
- scheme identifier, or if it has :file:`file:` as its scheme identifier, this
- opens a local file (without :term:`universal newlines`); otherwise it opens a socket to
- a server somewhere on the network. If the connection cannot be made the
- :exc:`IOError` exception is raised. If all went well, a file-like object is
- returned. This supports the following methods: :meth:`read`, :meth:`readline`,
- :meth:`readlines`, :meth:`fileno`, :meth:`close`, :meth:`info`, :meth:`getcode` and
- :meth:`geturl`. It also has proper support for the :term:`iterator` protocol. One
- caveat: the :meth:`read` method, if the size argument is omitted or negative,
- may not read until the end of the data stream; there is no good way to determine
+ Open a network object denoted by a URL for reading. If the URL does not
+ have a scheme identifier, or if it has :file:`file:` as its scheme
+ identifier, this opens a local file (without :term:`universal newlines`);
+ otherwise it opens a socket to a server somewhere on the network. If the
+ connection cannot be made the :exc:`IOError` exception is raised. If all
+ went well, a file-like object is returned. This supports the following
+ methods: :meth:`read`, :meth:`readline`, :meth:`readlines`, :meth:`fileno`,
+ :meth:`close`, :meth:`info`, :meth:`getcode` and :meth:`geturl`. It also
+ has proper support for the :term:`iterator` protocol. One caveat: the
+ :meth:`read` method, if the size argument is omitted or negative, may not
+ read until the end of the data stream; there is no good way to determine
that the entire stream from a socket has been read in the general case.
Except for the :meth:`info`, :meth:`getcode` and :meth:`geturl` methods,