commit d6a14a14838ff2e7bd5f72633b0d9b6f6e12f20e
author karl ding <karlding@users.noreply.github.com> Tue May 28 12:32:12 2019 -0700
committer Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> Tue May 28 12:32:12 2019 -0700
tree 6f6b72f46790a72bbc8f80d6e8561e1305071d20
parent 95b7706a955e2144eb54d815ec24a7eb0dff0b97

[3.7] Fix typo in docs for socket.CAN_RAW_FD_FRAMES (GH-13635) (GH-13637)



There is an extra "one" in the text description for the constant
socket.CAN_RAW_FD_FRAMES
(cherry picked from commit 1b05aa219041eb1c9dbcb4ec6c1fa5b20f060bf5)

Doc/library/socket.rst

diff --git a/Doc/library/socket.rst b/Doc/library/socket.rst
index 37b1577..15c65b9 100644
--- a/Doc/library/socket.rst
+++ b/Doc/library/socket.rst
@@ -373,7 +373,7 @@
 
    Enables CAN FD support in a CAN_RAW socket. This is disabled by default.
    This allows your application to send both CAN and CAN FD frames; however,
-   you one must accept both CAN and CAN FD frames when reading from the socket.
+   you must accept both CAN and CAN FD frames when reading from the socket.
 
    This constant is documented in the Linux documentation.