From 984ad9d6c7917a2af8c9dc707b71a877c2740c85 Mon Sep 17 00:00:00 2001
From: Yang Hau <yuanyanghau@gmail.com>
Date: Tue, 22 Nov 2022 20:23:59 +0800
Subject: [PATCH] fix typos

---
 src/handshake/server.rs | 2 +-
 src/protocol/mod.rs     | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/handshake/server.rs b/src/handshake/server.rs
index 4cf1c5c..6be3b15 100644
--- a/src/handshake/server.rs
+++ b/src/handshake/server.rs
@@ -208,7 +208,7 @@ pub struct ServerHandshake<S, C> {
 
 impl<S: Read + Write, C: Callback> ServerHandshake<S, C> {
     /// Start server handshake. `callback` specifies a custom callback which the user can pass to
-    /// the handshake, this callback will be called when the a websocket client connnects to the
+    /// the handshake, this callback will be called when the a websocket client connects to the
     /// server, you can specify the callback if you want to add additional header to the client
     /// upon join based on the incoming headers.
     pub fn start(stream: S, callback: C, config: Option<WebSocketConfig>) -> MidHandshake<Self> {
diff --git a/src/protocol/mod.rs b/src/protocol/mod.rs
index 9e826ce..94397e9 100644
--- a/src/protocol/mod.rs
+++ b/src/protocol/mod.rs
@@ -204,7 +204,7 @@ impl<Stream: Read + Write> WebSocket<Stream> {
     /// There is no need to call it again. Calling this function is
     /// the same as calling `write_message(Message::Close(..))`.
     ///
-    /// After queing the close frame you should continue calling `read_message` or
+    /// After queuing the close frame you should continue calling `read_message` or
     /// `write_pending` to drive the close handshake to completion.
     ///
     /// The websocket RFC defines that the underlying connection should be closed