@@ -1775,7 +1775,7 @@ to sockets.
17751775 much data, if any, was successfully sent.
17761776
17771777 .. versionchanged :: 3.5
1778- The socket timeout is no more reset each time data is sent successfully.
1778+ The socket timeout is no longer reset each time data is sent successfully.
17791779 The socket timeout is now the maximum total duration to send all data.
17801780
17811781 .. versionchanged :: 3.5
@@ -1998,8 +1998,8 @@ can be changed by calling :func:`setdefaulttimeout`.
19981998
19991999* In *non-blocking mode *, operations fail (with an error that is unfortunately
20002000 system-dependent) if they cannot be completed immediately: functions from the
2001- :mod: `select ` can be used to know when and whether a socket is available for
2002- reading or writing.
2001+ :mod: `select ` module can be used to know when and whether a socket is available
2002+ for reading or writing.
20032003
20042004* In *timeout mode *, operations fail if they cannot be completed within the
20052005 timeout specified for the socket (they raise a :exc: `timeout ` exception)
@@ -2188,7 +2188,7 @@ manager protocol instead, open a socket with::
21882188 socket.socket(socket.AF_CAN, socket.SOCK_DGRAM, socket.CAN_BCM)
21892189
21902190After binding (:const: `CAN_RAW `) or connecting (:const: `CAN_BCM `) the socket, you
2191- can use the :meth: `socket.send `, and the :meth: `socket.recv ` operations (and
2191+ can use the :meth: `socket.send ` and :meth: `socket.recv ` operations (and
21922192their counterparts) on the socket object as usual.
21932193
21942194This last example might require special privileges::
0 commit comments