Fix typos in documentation

Author: umlaeute

docs/docs/partials/introduction.md

@@ -32,7 +32,7 @@ obs-websocket provides a feature-rich RPC communication protocol, giving access
 - Abstraction of identification, events, requests, and batch requests into dedicated message types
 - Conformity of request naming using similar terms like `Get`, `Set`, `Get[x]List`, `Start[x]`, `Toggle[x]`
 - Conformity of OBS data field names like `sourceName`, `sourceKind`, `sourceType`, `sceneName`, `sceneItemName`
-- Error code response system - integer corrosponds to type of error, with optional comment
+- Error code response system - integer corresponds to type of error, with optional comment
 - Possible support for multiple message encoding options: JSON and MessagePack
 - PubSub system - Allow clients to specify which events they do or don't want to receive from OBS
 - RPC versioning - Client and server negotiate the latest version of the obs-websocket protocol to communicate with.
@@ -255,7 +255,7 @@ Authentication is not required
 
 - Sent from: obs-websocket
 - Sent to: All subscribed and identified clients
-- Description: An event coming from OBS has occured. Eg scene switched, source muted.
+- Description: An event coming from OBS has occurred. Eg scene switched, source muted.
 
 **Data Keys:**
 

docs/generated/protocol.json

@@ -4,7 +4,7 @@
       "enumType": "EventSubscription",
       "enumIdentifiers": [
         {
-          "description": "Subcription value used to disable all events.",
+          "description": "Subscription value used to disable all events.",
           "enumIdentifier": "None",
           "rpcVersion": "1",
           "deprecated": false,
@@ -6710,4 +6710,4 @@
       ]
     }
   ]
-}
+}

docs/generated/protocol.md

@@ -34,7 +34,7 @@ obs-websocket provides a feature-rich RPC communication protocol, giving access
 - Abstraction of identification, events, requests, and batch requests into dedicated message types
 - Conformity of request naming using similar terms like `Get`, `Set`, `Get[x]List`, `Start[x]`, `Toggle[x]`
 - Conformity of OBS data field names like `sourceName`, `sourceKind`, `sourceType`, `sceneName`, `sceneItemName`
-- Error code response system - integer corrosponds to type of error, with optional comment
+- Error code response system - integer corresponds to type of error, with optional comment
 - Possible support for multiple message encoding options: JSON and MessagePack
 - PubSub system - Allow clients to specify which events they do or don't want to receive from OBS
 - RPC versioning - Client and server negotiate the latest version of the obs-websocket protocol to communicate with.
@@ -257,7 +257,7 @@ Authentication is not required
 
 - Sent from: obs-websocket
 - Sent to: All subscribed and identified clients
-- Description: An event coming from OBS has occured. Eg scene switched, source muted.
+- Description: An event coming from OBS has occurred. Eg scene switched, source muted.
 
 **Data Keys:**
 
@@ -1162,7 +1162,7 @@ The combination of request fields cannot be used to perform an action.
 
 ### EventSubscription::None
 
-Subcription value used to disable all events.
+Subscription value used to disable all events.
 
 - Identifier Value: `0`
 - Latest Supported RPC Version: `1`