Made some more fixes

Signed-off-by: Gbadebo Bello <[email protected]>
litmuschaos · Jul 19, 2021 · f63a071 · f63a071
1 parent 0ec65b1
commit f63a071
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/website/docs/agent-installation.md b/website/docs/agent-installation.md
@@ -4,12 +4,12 @@ title: Litmus Chaos Agent Install
 sidebar_label: Chaos Agent
 ---
 
-In Litmus the Agents can be classified as two types
+In Litmus the Agents can be classified into two, namely;
 
 - Self Agent
 - External Agent
 
-As part of Litmus installation by default, a self cluster would be registered as Agent in the Portal. From Portal you induce chaos into self cluster and observe the results from the Portal.
+As a part of the Litmus installation, by default, a self cluster would be registered as Agent in the Portal. From the Portal you induce chaos into self cluster and observe the results from the Portal.
 
 As you are aware by now, Portal is a Cross Cloud Chaos Control plane. That is you can connect multiple external kubernetes agents to this portal. Once connected you can manage the chaos from the Portal that is you can induce chaos into this agent from the Portal and observe the results from the Portal. Using the command line utility _litmusctl_ you can connect the external agents to the Portal.
 
@@ -193,4 +193,4 @@ Installation Mode:  cluster
 👉 Litmus agents can be accessed here: http://172.17.0.2:31696/targets
 ```
 
-To verify, if the connection process was successful you can view the list of connected agents from the Targets section on your LitmusPortal and ensure that the connected agent is in Active State.
+To verify, if the connection process was successful you can view the list of connected agents from the targets section on your LitmusPortal and ensure that the connected agent is in Active State.
diff --git a/website/docs/observe-workflow.md b/website/docs/observe-workflow.md
@@ -8,7 +8,7 @@ sidebar_label: Observe Workflow
 
 ---
 
-After scheduling a workflow, the user can track the status of the workflow from the Browse Workflow section. The status that is currently displayed are :
+After scheduling a workflow, the user can track the status of the workflow from the Browse Workflow section. The status that is currently displayed are:
 
 - Failed
 - Running