diff --git a/docs/en/Deployment/Distributed-Microservice.md b/docs/en/Deployment/Distributed-Microservice.md
index 450d968d84..9af4a1c839 100644
--- a/docs/en/Deployment/Distributed-Microservice.md
+++ b/docs/en/Deployment/Distributed-Microservice.md
@@ -1,10 +1,10 @@
 # Deploying Distributed / Microservice Solutions
 
-The ABP Framework is designed to consider distributed and microservice systems, where you have multiple applications and/or services communicating internally. All of its features are compatible with distributed scenarios. This document highlights some points you should care when you deploy your distributed or microservice solution.
+The ABP Framework is designed to consider distributed and microservice systems, where you have multiple applications and/or services communicating internally. All of its features are compatible with distributed scenarios. This document highlights some points you should care about when you deploy your distributed or microservice solution.
 
 ## Application Name & Instance Id
 
-ABP provides `IApplicationInfoAccessor` service that provides the following properties:
+ABP provides the `IApplicationInfoAccessor` service that provides the following properties:
 
 * `ApplicationName`: A human-readable name for an application. It is a unique value for an application.
 * `InstanceId`: A random (GUID) value generated by the ABP Framework each time you start the application.
@@ -32,7 +32,7 @@ await builder.AddApplicationAsync<OrderingServiceHttpApiHostModule>(options =>
 
 ## Using a Distributed Event Bus
 
-ABP's [Distributed Event Bus](../Distributed-Event-Bus.md) system provides a standard interface to communicate to other applications and services. While the name is "distributed", the default implementation is in-process. That means, your applications / services can not communicate to each other unless you explicitly configure a distributed event bus provider.
+ABP's [Distributed Event Bus](../Distributed-Event-Bus.md) system provides a standard interface to communicate with other applications and services. While the name is "distributed", the default implementation is in-process. That means, your applications / services can not communicate with each other unless you explicitly configure a distributed event bus provider.
 
 If you are building a distributed system, then the applications should communicate through an external distributed messaging server. Please follow the [Distributed Event Bus](../Distributed-Event-Bus.md) document to learn how to install and configure your distributed event bus provider.