Corrected some errors

Signed-off-by: Gbahdeyboh <[email protected]>
litmuschaos · Jul 23, 2021 · a029755 · a029755
1 parent ca99c33
commit a029755
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/.github/ISSUE_TEMPLATE/create-new-section-template.md b/.github/ISSUE_TEMPLATE/create-new-section-template.md
@@ -1,6 +1,6 @@
 ---
 name: Create a new section
-about: For issues requesting for the need of an entirely new section(sidebars) in the documentation
+about: For documentation issues requiring an entirely new section in the sidebar
 title: Create {section}
 labels: sections
 

diff --git a/website/docs/agent-installation.md b/website/docs/agent-installation.md
@@ -9,7 +9,7 @@ In Litmus the Agents can be classified into two, namely;
 - Self Agent
 - External Agent
 
-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 a part of the Litmus installation, by default, a self cluster would be registered as an Agent in the Portal. From the Portal you may 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.
 

diff --git a/website/docs/architecture.md b/website/docs/architecture.md
@@ -17,7 +17,7 @@ The above picture gives you a high-level architecture of the Litmus. At highleve
 
 **Agent** is the set of Litmus components which induces Chaos using the chaos workflows on the K8S cluster component.
 
-A typical user scenario would be when a user would installs litmus, this would in-turn install Portal and Agent on the self cluster. Using the portal user can create/schedule new chaos workflows on the Agents and observe the results from here. Users can also connect more clusters to the portal, and use the Portal as single window pane for cross cloud chaos management.
+A typical user scenario would be when a user would install litmus. This would, in turn, install Portal and Agent on the self cluster. Using the portal, the user can create/schedule new chaos workflows on the Agents and observe the results from here. Users can also connect more clusters to the portal, and use the Portal as single window pane for cross cloud chaos management.
 
 
 #### Portal Components