Update processing.md (#67)

occuring -> occurring

website/docs/dev/processing.md

@@ -11,7 +11,7 @@ Messages to Garnet server are processed once the networking layer reads the inco
 Within a session, the `TryConsumeMessages` method is responsible for processing the incoming messages by
 * Measuring and tracking latency of processing along with bytes consumed and operations performed.
 * Process messages further using the `ProcessMessages` method.
-* Acts as the catch all for any exceptions occuring during message processing. This ensures that the server continues to run, even if processing of a message causes a critical unhandled exception and all resources are being freed up correctly.
+* Acts as the catch all for any exceptions occurring during message processing. This ensures that the server continues to run, even if processing of a message causes a critical unhandled exception and all resources are being freed up correctly.
 
 The `ProcessMessages` method does a fast parsing of the incoming data to quickly identify the right command type. Based on the type of the command, further processing is performed by one of the below methods.
 
@@ -34,4 +34,4 @@ specific parameters from the incoming network buffer. Once the necessary argumen
 For example, see `NetworkIncrement` method in `BasicCommands.cs`.
 
 The storage layer methods perform the actual processing logic of the command. They do utilize the underlying Tsavorite layer's APIs for performing operations like Read, RMW, Upset, Delete. Also, additional processing logic is implemented in the Tsavorite callbacks.
-For example, see `Increment` method in `MainStoreOps.cs` and related methods in `MainStoreFunctions`.
+For example, see `Increment` method in `MainStoreOps.cs` and related methods in `MainStoreFunctions`.