@@ -1775,7 +1775,7 @@ to sockets.
1775
1775
much data, if any, was successfully sent.
1776
1776
1777
1777
.. 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.
1779
1779
The socket timeout is now the maximum total duration to send all data.
1780
1780
1781
1781
.. versionchanged :: 3.5
@@ -1998,8 +1998,8 @@ can be changed by calling :func:`setdefaulttimeout`.
1998
1998
1999
1999
* In *non-blocking mode *, operations fail (with an error that is unfortunately
2000
2000
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.
2003
2003
2004
2004
* In *timeout mode *, operations fail if they cannot be completed within the
2005
2005
timeout specified for the socket (they raise a :exc: `timeout ` exception)
@@ -2188,7 +2188,7 @@ manager protocol instead, open a socket with::
2188
2188
socket.socket(socket.AF_CAN, socket.SOCK_DGRAM, socket.CAN_BCM)
2189
2189
2190
2190
After 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
2192
2192
their counterparts) on the socket object as usual.
2193
2193
2194
2194
This last example might require special privileges::
0 commit comments