From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Date: Tue, 4 Apr 2023 22:55:11 +0000 (-0700)
Subject: Improve some grammar in the socket docs (GH-103254)
X-Git-Tag: v3.10.12~17^2
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=d76a5c6f7b1caf55c2162fd66bcdb9d8dd890005;p=thirdparty%2FPython%2Fcpython.git

Improve some grammar in the socket docs (GH-103254)

(cherry picked from commit bceb9e00ad2998e5193ad5b477e92a114dd31024)

Co-authored-by: Tim Burke <tim.burke@gmail.com>
---

diff --git a/Doc/library/socket.rst b/Doc/library/socket.rst
index 6fb6d5fd8b1b..cd0d2ce0f112 100644
--- a/Doc/library/socket.rst
+++ b/Doc/library/socket.rst
@@ -1596,7 +1596,7 @@ to sockets.
    much data, if any, was successfully sent.
 
    .. versionchanged:: 3.5
-      The socket timeout is no more reset each time data is sent successfully.
+      The socket timeout is no longer reset each time data is sent successfully.
       The socket timeout is now the maximum total duration to send all data.
 
    .. versionchanged:: 3.5
@@ -1814,8 +1814,8 @@ can be changed by calling :func:`setdefaulttimeout`.
 
 * In *non-blocking mode*, operations fail (with an error that is unfortunately
   system-dependent) if they cannot be completed immediately: functions from the
-  :mod:`select` can be used to know when and whether a socket is available for
-  reading or writing.
+  :mod:`select` module can be used to know when and whether a socket is available
+  for reading or writing.
 
 * In *timeout mode*, operations fail if they cannot be completed within the
   timeout specified for the socket (they raise a :exc:`timeout` exception)
@@ -2004,7 +2004,7 @@ manager protocol instead, open a socket with::
     socket.socket(socket.AF_CAN, socket.SOCK_DGRAM, socket.CAN_BCM)
 
 After binding (:const:`CAN_RAW`) or connecting (:const:`CAN_BCM`) the socket, you
-can use the :meth:`socket.send`, and the :meth:`socket.recv` operations (and
+can use the :meth:`socket.send` and :meth:`socket.recv` operations (and
 their counterparts) on the socket object as usual.
 
 This last example might require special privileges::