docs: fix grammar and spelling errors in v1 documentation

- Fix spelling: explaination → explanation
- Fix spelling: configuaration → configuration
- Fix grammar: that files → those files
- Fix grammar: the a piped → a piped
- Fix grammar: how install → how to install
- Fix grammar: Please checkout → Please check out
- Fix phrase: community built → community-built

Signed-off-by: ansita20 <ansitasingh20@gmail.com>

Author: Ansita20

docs/content/en/docs-v1.0.x/installation/install-piped/installing-on-kubernetes.md

@@ -3,7 +3,7 @@ title: "Installing on a Kubernetes cluster"
 linkTitle: "Installing on a Kubernetes cluster"
 weight: 1
 description: >
-  This page describes how install Piped on a Kubernetes cluster.
+  This page describes how to install Piped on a Kubernetes cluster.
 ---
 
 ## Prerequisites
@@ -16,7 +16,7 @@ description: >
 ### SSH Key for Git Repositories
 
 - If your Git repositories are private, `piped` requires a private SSH key to access those repositories.
-- Please checkout [this documentation](https://help.github.com/en/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) for how to generate a new SSH key pair. Then add the public key to your repositories. (If you are using GitHub, you can add it to Deploy Keys at the repository's Settings page.)
+- Please check out [this documentation](https://help.github.com/en/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) for how to generate a new SSH key pair. Then add the public key to your repositories. (If you are using GitHub, you can add it to Deploy Keys at the repository's Settings page.)
 
 If your Git repositories are private, `piped` needs an SSH key to access them.
 
@@ -27,11 +27,11 @@ If your Git repositories are private, `piped` needs an SSH key to access them.
 
 ## Installation
 
-### Preparing the `Piped` configuaration file
+### Preparing the `Piped` configuration file
 
  Plugins are external binaries that have to be referenced in the piped configuration file. There are no plugins set by default.
 
-An example of the a piped V1 configuration file using the Kubernetes plugin:
+An example of a piped V1 configuration file using the Kubernetes plugin:
 
 ```yaml
 apiVersion: pipecd.dev/v1beta1
@@ -52,7 +52,7 @@ spec:
 >**Note:**
 >`Piped`'s plugins are versioned independently from PipeCD. See the [latest releases](https://github.com/pipe-cd/pipecd/releases) for more information.
 >
->We now also have a repository for community built plugins. See the [Community plugins repository on GitHub](https://github.com/pipe-cd/community-plugins)  to know more.
+>We now also have a repository for community-built plugins. See the [Community plugins repository on GitHub](https://github.com/pipe-cd/community-plugins) to know more.
 
 ## In the cluster-wide mode
 

docs/content/en/docs-v1.0.x/installation/install-piped/installing-on-single-machine.md

@@ -17,7 +17,7 @@ description: >
 ### SSH Key for Git Repositories
 
 - If your Git repositories are private, `piped` requires a private SSH key to access those repositories.
-- Please checkout [this documentation](https://help.github.com/en/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) for how to generate a new SSH key pair. Then add the public key to your repositories. (If you are using GitHub, you can add it to Deploy Keys at the repository's Settings page.)
+- Please check out [this documentation](https://help.github.com/en/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) for how to generate a new SSH key pair. Then add the public key to your repositories. (If you are using GitHub, you can add it to Deploy Keys at the repository's Settings page.)
 
 If your Git repositories are private, `piped` needs an SSH key to access them.
 
@@ -32,11 +32,11 @@ Download the latest `piped` V1. See the [latest releases](https://github.com/pip
 
 ## Installation
 
-### Preparing the `Piped` configuaration file
+### Preparing the `Piped` configuration file
 
 Plugins are external binaries that have to be referenced in the piped configuration file. There are no plugins set by default.
 
-An example of the a piped V1 configuration file using the [Example-stage plugin](https://github.com/pipe-cd/community-plugins/tree/main/plugins/example-stage):
+An example of a piped V1 configuration file using the [Example-stage plugin](https://github.com/pipe-cd/community-plugins/tree/main/plugins/example-stage):
 
 ```yaml
 apiVersion: pipecd.dev/v1beta1
@@ -59,7 +59,7 @@ See [ConfigurationReference](../../../user-guide/managing-piped/configuration-re
 >**Note:**
 >`Piped`'s plugins are versioned independently from PipeCD. Official plugins are maintained and monitored by the PipeCD Maintainers. See the [latest releases](https://github.com/pipe-cd/pipecd/releases) for more information.
 >
->We now also have a repository for community built plugins. See the [Community plugins repository on GitHub](https://github.com/pipe-cd/community-plugins) to know more.
+>We now also have a repository for community-built plugins. See the [Community plugins repository on GitHub](https://github.com/pipe-cd/community-plugins) to know more.
 
 ## Run the `piped`
 

docs/content/en/docs-v1.0.x/overview/_index.md

@@ -6,7 +6,7 @@ description: >
   Overview about PipeCD.
 ---
 
-![PipeCD explaination](/images/pipecd-explanation.png)
+![PipeCD explanation](/images/pipecd-explanation.png)
 <p style="text-align: center;">
 PipeCD - a GitOps style continuous delivery solution
 </p>

docs/content/en/docs-v1.0.x/user-guide/managing-application/event-watcher.md

@@ -35,7 +35,7 @@ Therefore, you mainly need to:
 #### Use the `.pipe/` directory
 
 Prepare EventWatcher configuration files under the `.pipe/` directory at the root of your Git repository.
-In that files, you define which values in which files should be updated when the Piped found out a new Event.
+In those files, you define which values in which files should be updated when the Piped found out a new Event.
 
 For instance, suppose you want to update the Kubernetes manifest defined in `helloworld/deployment.yaml` when an Event with the name `helloworld-image-update` occurs: