Add missed comma (dotnet#25401)

Author: volo-v

docs/architecture/microservices/multi-container-microservice-net-applications/integration-event-based-microservice-communications.md

@@ -91,7 +91,7 @@ In Figure 6-20, you can see an abstraction of an event bus with multiple impleme
 
 **Figure 6- 20.** Multiple implementations of an event bus
 
-It's good to have the event bus defined through an interface so it can be implemented with several technologies, like RabbitMQ Azure Service bus or others. However, and as mentioned previously, using your own abstractions (the event bus interface) is good only if you need basic event bus features supported by your abstractions. If you need richer service bus features, you should probably use the API and abstractions provided by your preferred commercial service bus instead of your own abstractions.
+It's good to have the event bus defined through an interface so it can be implemented with several technologies, like RabbitMQ, Azure Service bus or others. However, and as mentioned previously, using your own abstractions (the event bus interface) is good only if you need basic event bus features supported by your abstractions. If you need richer service bus features, you should probably use the API and abstractions provided by your preferred commercial service bus instead of your own abstractions.
 
 ### Defining an event bus interface