Skip to content

Commit c9536ed

Browse files
cclaussKriechi
authored andcommitted
Fix typos discovered by codespell
1 parent 820701b commit c9536ed

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

CHANGELOG.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -143,7 +143,7 @@ Release History
143143
if isinstance(event, Ping):
144144
bytes_to_send = connection.send(event.response())
145145
- Separate the handshake from the active connection handling. This
146-
allows the handshake and connection to be seperately used. By
146+
allows the handshake and connection to be separately used. By
147147
default though WSConnection does both.
148148
- ``receive_bytes`` is renamed to ``receive_data`` and
149149
``WSConnection`` should be imported from ``wsproto`` rather than
@@ -155,7 +155,7 @@ Release History
155155
- Support h11 ~0.8.1.
156156
- Support Python 3.7.
157157
- Make the close-handshake more explicit, by sending a close frame on
158-
reciept of a close frame.
158+
receipt of a close frame.
159159
- Bugfix fix deflate after a non-compressable message.
160160
- Bugfix connection header acceptance, by accepting Connection header
161161
values that are comma separated lists.

docs/source/advanced-usage.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ A WebSocket connection starts with a handshake, which is an agreement
5656
to use the WebSocket protocol, and on which sub-protocol and
5757
extensions to use. It can be advantageous to perform this handshake
5858
outside of `wsproto`, for example in a dual stack setup whereby the
59-
HTTP handling is completed seperately. In this case the
59+
HTTP handling is completed separately. In this case the
6060
:class:`Connection <wsproto.connection.Connection>` class can be used
6161
directly.
6262

0 commit comments

Comments
 (0)