typo

Author: vladvelici

src/pages/docs/guides/chat/build-embedded-chat.mdx

@@ -46,7 +46,7 @@ Each room includes all relevant participants: customers and agents in support, b
 Key considerations for embedded chat rooms:
 - When will the room be joined by participants and how will it be linked to the rest of your application (delivery, support ticket, game session and so on)? Examples:
   - For something like support, create a ticket when the user opens the chat window; optionally ask for some details before creating the ticket. Return an authentication token and room name with the new ticket details, the user will then join using this information.
-  - For games, use one room per game session for games such as chess, or for a MMORPG, allocate a room for each location of instance of a quest.
+  - For games, use one room per game session for games such as chess, or for a MMORPG, allocate a room for each location or instance of a quest.
   - For deliveries, appointments, or calls, there is a clear 1:1 mapping of task to room and users join the room when they join the task.
 - Will users be active at the same time, or will they come and go with periods of inactivity?
   - Only attaching to rooms when they are needed is more cost-effective and saves resources.