Update src/content/docs/durable-objects/best-practices/websockets.mdx

Author: Oxyjun

src/content/docs/durable-objects/best-practices/websockets.mdx

@@ -30,7 +30,7 @@ In addition to [the Web Standard WebSocket API](/workers/runtime-apis/websockets
 
 When a Durable Object receives no events or messages for 10 seconds, the Durable Object is evicted from memory to avoid unnecessary usage. The WebSocket clients remain connected to the Cloudflare network. When your Durable Object receives an event during hibernation, it is re-instantiated, its `constructor` function is called, and it can access the WebSocket clients with the `this.ctx.getWebSockets()` function.
 
-When the Durable Object is evicted from memory, it's in-memory state is reset. It is common to rely on in-memory state to organize your WebSockets (ex: keeping your WebSockets in rooms with a Map<WebSocket, Object> data type). With Hibernation, you must restore the in-memory state of your Durable Object within the `constructor` function.
+When the Durable Object is evicted from memory, its in-memory state is reset. It is common to rely on in-memory state to organize your WebSockets (for example, keeping your WebSockets in rooms with a `Map<WebSocket, Object>` data type). With Hibernation, you must restore the in-memory state of your Durable Object within the `constructor` function.
 
 To do this, you can use the `serializeAttachment` to persist additional data with the Durable Object WebSocket class, which will persist the data to the Durable Object's storage. Upon re-initialization of the Durable Object, you can access this data with `deserializeAttachment`.