From edf29e828c09f6537e79a66e53f6ce8e55ad0607 Mon Sep 17 00:00:00 2001
From: Github Actions <>
Date: Sat, 31 Dec 2022 22:55:24 +0000
Subject: [PATCH] docs(ci): Update generated docs - 079ab31 [skip ci]

---
 docs/generated/protocol.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/generated/protocol.md b/docs/generated/protocol.md
index e6a20633..11d1006e 100644
--- a/docs/generated/protocol.md
+++ b/docs/generated/protocol.md
@@ -63,7 +63,7 @@ These steps should be followed precisely. Failure to connect to the server as in
 
 - The server receives and processes the `Identify` sent by the client.
   - If authentication is required and the `Identify` message data does not contain an `authentication` string, or the string is not correct, the connection is closed with `WebSocketCloseCode::AuthenticationFailed`
-  - If the client has requested an `rpcVersion` which the server cannot use, the connection is closed with `WebSocketCloseCode::UnsupportedRpcVersion`. This system allows both the server and client to have seamless backwards compatability.
+  - If the client has requested an `rpcVersion` which the server cannot use, the connection is closed with `WebSocketCloseCode::UnsupportedRpcVersion`. This system allows both the server and client to have seamless backwards compatibility.
   - If any other parameters are malformed (invalid type, etc), the connection is closed with an appropriate close code.
 
 - Once identification is processed on the server, the server responds to the client with an [OpCode 2 `Identified`](#identified-opcode-2).