From 079ab31f88424aeab450bbadf4cfc209196ac019 Mon Sep 17 00:00:00 2001
From: tyami94 <31934451+tyami94@users.noreply.github.com>
Date: Sat, 31 Dec 2022 12:34:52 -0500
Subject: [PATCH] docs: Fix small typo in introduction.md

- Corrected 'compatability' to 'compatibility' in docs/docs/partials/introduction.md
---
 docs/docs/partials/introduction.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/docs/partials/introduction.md b/docs/docs/partials/introduction.md
index 59a29de3..982e1c9a 100644
--- a/docs/docs/partials/introduction.md
+++ b/docs/docs/partials/introduction.md
@@ -61,7 +61,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).