diff --git a/docs/docs/domains/index.md b/docs/docs/domains/index.md
index 4d639d8a07..036811d95f 100644
--- a/docs/docs/domains/index.md
+++ b/docs/docs/domains/index.md
@@ -1,5 +1,5 @@
 ## Task Domains
-Task domains helps support task development. The idea is same “task definition” can be implemented in different “domains”. A domain some arbitrary name that the developer controls. So when the workflow is started, the caller can specify, out of all the tasks in the workflow, which tasks need to run in a specific domain, this domain is then used to poll for task on the client side to execute it.  
+Task domains helps support task development. The idea is same “task definition” can be implemented in different “domains”. A domain is some arbitrary name that the developer controls. So when the workflow is started, the caller can specify, out of all the tasks in the workflow, which tasks need to run in a specific domain, this domain is then used to poll for task on the client side to execute it.  
 
 As an example if a workflow (WF1) has 3 tasks T1, T2, T3. The workflow is deployed and working fine, which means there are T2 workers polling and executing. If you modify T2 and run it locally there is no guarantee that your modified T2 worker will get the task that you are looking for as it coming from the general T2 queue. “Task Domain” feature solves this problem by splitting the T2 queue by domains, so when the app polls for task T2 in a specific domain, it get the correct task.