docs(fix): typos in script-run.md and installation docs

docs/content/en/docs-dev/installation/install-control-plane/installing-controlplane-on-k8s.md

@@ -62,7 +62,7 @@ spec:
 
 See [ConfigurationReference](../../../user-guide/managing-controlplane/configuration-reference/) for the full configuration.
 
-After all, install the Control Plane as bellow:
+After that, install the Control Plane as below:
 
 ``` console
 helm upgrade -i pipecd oci://ghcr.io/pipe-cd/chart/pipecd --version {{< blocks/latest_version >}} --namespace={NAMESPACE} \

docs/content/en/docs-dev/user-guide/managing-application/customizing-deployment/script-run.md

@@ -93,13 +93,13 @@ For example, If you are using the container platform and the offcial piped conta
 
 The public piped image available in PipeCD main repo (ref: [Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/cmd/piped/Dockerfile)) is based on [alpine](https://hub.docker.com/_/alpine/) and only has a few UNIX commands available (ref: [piped-base Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/tool/piped-base/Dockerfile)). 
 
-If you want to use your commands, you can realize it with either step below.
+If you want to use your commands, you can do that with either of the following steps.
 - Prepare your own environment container image then add [piped binary](https://github.com/pipe-cd/pipecd/releases) to it.
 - Build your own container image based on `ghcr.io/pipe-cd/piped` image.
 
 ## Default environment values
 
-You can use the envrionment values related to the deployment.
+You can use the environment values related to the deployment.
 
 | Name | Description | Example |
 |-|-|-|

docs/content/en/docs-dev/user-guide/managing-piped/adding-a-platform-provider.md

@@ -100,7 +100,7 @@ It attempts to retrieve credentials in the following order:
 3. From the pod running in EKS cluster via STS (SecurityTokenService).
 4. From the EC2 Instance Role.
 
-Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write).
+Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write).
 
 See [ConfigurationReference](../configuration-reference/#platformproviderlambdaconfig) for the full configuration.
 

docs/content/en/docs-v0.39.x/installation/install-controlplane.md

@@ -62,7 +62,7 @@ spec:
 
 See [ConfigurationReference](../../user-guide/managing-controlplane/configuration-reference/) for the full configuration.
 
-After all, install the Control Plane as bellow:
+After that, install the Control Plane as below:
 
 ``` console
 helm upgrade -i pipecd oci://ghcr.io/pipe-cd/chart/pipecd --version {{< blocks/latest_version >}} --namespace={NAMESPACE} \

docs/content/en/docs-v0.39.x/user-guide/managing-piped/adding-a-cloud-provider.md

@@ -102,7 +102,7 @@ It attempts to retrieve credentials in the following order:
 3. From the pod running in EKS cluster via STS (SecurityTokenService).
 4. From the EC2 Instance Role.
 
-Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write).
+Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write).
 
 See [ConfigurationReference](../configuration-reference/#cloudproviderlambdaconfig) for the full configuration.
 

docs/content/en/docs-v0.39.x/user-guide/managing-piped/adding-a-platform-provider.md

@@ -100,7 +100,7 @@ It attempts to retrieve credentials in the following order:
 3. From the pod running in EKS cluster via STS (SecurityTokenService).
 4. From the EC2 Instance Role.
 
-Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write).
+Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write).
 
 See [ConfigurationReference](../configuration-reference/#platformproviderlambdaconfig) for the full configuration.
 

docs/content/en/docs-v0.40.x/installation/install-controlplane.md

@@ -62,7 +62,7 @@ spec:
 
 See [ConfigurationReference](../../user-guide/managing-controlplane/configuration-reference/) for the full configuration.
 
-After all, install the Control Plane as bellow:
+After that, install the Control Plane as below:
 
 ``` console
 helm upgrade -i pipecd oci://ghcr.io/pipe-cd/chart/pipecd --version {{< blocks/latest_version >}} --namespace={NAMESPACE} \

docs/content/en/docs-v0.40.x/user-guide/managing-piped/adding-a-cloud-provider.md

@@ -102,7 +102,7 @@ It attempts to retrieve credentials in the following order:
 3. From the pod running in EKS cluster via STS (SecurityTokenService).
 4. From the EC2 Instance Role.
 
-Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write).
+Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write).
 
 See [ConfigurationReference](../configuration-reference/#cloudproviderlambdaconfig) for the full configuration.
 

docs/content/en/docs-v0.40.x/user-guide/managing-piped/adding-a-platform-provider.md

@@ -100,7 +100,7 @@ It attempts to retrieve credentials in the following order:
 3. From the pod running in EKS cluster via STS (SecurityTokenService).
 4. From the EC2 Instance Role.
 
-Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write).
+Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write).
 
 See [ConfigurationReference](../configuration-reference/#platformproviderlambdaconfig) for the full configuration.
 

docs/content/en/docs-v0.41.x/installation/install-controlplane.md

@@ -62,7 +62,7 @@ spec:
 
 See [ConfigurationReference](../../user-guide/managing-controlplane/configuration-reference/) for the full configuration.
 
-After all, install the Control Plane as bellow:
+After that, install the Control Plane as below:
 
 ``` console
 helm upgrade -i pipecd oci://ghcr.io/pipe-cd/chart/pipecd --version {{< blocks/latest_version >}} --namespace={NAMESPACE} \

docs/content/en/docs-v0.41.x/user-guide/managing-piped/adding-a-cloud-provider.md

@@ -102,7 +102,7 @@ It attempts to retrieve credentials in the following order:
 3. From the pod running in EKS cluster via STS (SecurityTokenService).
 4. From the EC2 Instance Role.
 
-Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write).
+Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write).
 
 See [ConfigurationReference](../configuration-reference/#cloudproviderlambdaconfig) for the full configuration.
 

docs/content/en/docs-v0.41.x/user-guide/managing-piped/adding-a-platform-provider.md

@@ -100,7 +100,7 @@ It attempts to retrieve credentials in the following order:
 3. From the pod running in EKS cluster via STS (SecurityTokenService).
 4. From the EC2 Instance Role.
 
-Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write).
+Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write).
 
 See [ConfigurationReference](../configuration-reference/#platformproviderlambdaconfig) for the full configuration.
 

docs/content/en/docs-v0.42.x/installation/install-controlplane.md

@@ -62,7 +62,7 @@ spec:
 
 See [ConfigurationReference](../../user-guide/managing-controlplane/configuration-reference/) for the full configuration.
 
-After all, install the Control Plane as bellow:
+After that, install the Control Plane as below:
 
 ``` console
 helm upgrade -i pipecd oci://ghcr.io/pipe-cd/chart/pipecd --version {{< blocks/latest_version >}} --namespace={NAMESPACE} \

docs/content/en/docs-v0.42.x/user-guide/managing-piped/adding-a-cloud-provider.md

@@ -102,7 +102,7 @@ It attempts to retrieve credentials in the following order:
 3. From the pod running in EKS cluster via STS (SecurityTokenService).
 4. From the EC2 Instance Role.
 
-Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write).
+Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write).
 
 See [ConfigurationReference](../configuration-reference/#cloudproviderlambdaconfig) for the full configuration.
 

docs/content/en/docs-v0.42.x/user-guide/managing-piped/adding-a-platform-provider.md

@@ -100,7 +100,7 @@ It attempts to retrieve credentials in the following order:
 3. From the pod running in EKS cluster via STS (SecurityTokenService).
 4. From the EC2 Instance Role.
 
-Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write).
+Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write).
 
 See [ConfigurationReference](../configuration-reference/#platformproviderlambdaconfig) for the full configuration.
 

docs/content/en/docs-v0.43.x/installation/install-controlplane.md

@@ -62,7 +62,7 @@ spec:
 
 See [ConfigurationReference](../../user-guide/managing-controlplane/configuration-reference/) for the full configuration.
 
-After all, install the Control Plane as bellow:
+After that, install the Control Plane as below:
 
 ``` console
 helm upgrade -i pipecd oci://ghcr.io/pipe-cd/chart/pipecd --version {{< blocks/latest_version >}} --namespace={NAMESPACE} \

docs/content/en/docs-v0.43.x/user-guide/managing-piped/adding-a-cloud-provider.md

@@ -102,7 +102,7 @@ It attempts to retrieve credentials in the following order:
 3. From the pod running in EKS cluster via STS (SecurityTokenService).
 4. From the EC2 Instance Role.
 
-Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write).
+Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write).
 
 See [ConfigurationReference](../configuration-reference/#cloudproviderlambdaconfig) for the full configuration.
 

docs/content/en/docs-v0.43.x/user-guide/managing-piped/adding-a-platform-provider.md

@@ -100,7 +100,7 @@ It attempts to retrieve credentials in the following order:
 3. From the pod running in EKS cluster via STS (SecurityTokenService).
 4. From the EC2 Instance Role.
 
-Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write).
+Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write).
 
 See [ConfigurationReference](../configuration-reference/#platformproviderlambdaconfig) for the full configuration.
 

docs/content/en/docs-v0.44.x/installation/install-controlplane.md

@@ -62,7 +62,7 @@ spec:
 
 See [ConfigurationReference](../../user-guide/managing-controlplane/configuration-reference/) for the full configuration.
 
-After all, install the Control Plane as bellow:
+After that, install the Control Plane as below:
 
 ``` console
 helm upgrade -i pipecd oci://ghcr.io/pipe-cd/chart/pipecd --version {{< blocks/latest_version >}} --namespace={NAMESPACE} \

docs/content/en/docs-v0.44.x/user-guide/managing-application/customizing-deployment/custom-sync.md

@@ -43,7 +43,7 @@ spec:
 Note:
 1. You can use `CUSTOM_SYNC` with any current supporting application kind, but keep `alwaysUsePipeline` true to not run the application kind's default `QUICK_SYNC`.
 2. Only one `CUSTOM_SYNC` stage should be used in an application pipeline.
-3. The commands run with the enviroment variable `PATH` that refers `~/.piped/tools` at first.
+3. The commands run with the environment variable `PATH` that refers `~/.piped/tools` at first.
 
 The public piped image available in PipeCD main repo (ref: [Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/cmd/piped/Dockerfile)) is based on [alpine](https://hub.docker.com/_/alpine/) and only has a few UNIX command available (ref: [piped-base Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/tool/piped-base/Dockerfile)). If you want to use your commands (`sam` in the above example), you can:
 

docs/content/en/docs-v0.44.x/user-guide/managing-piped/adding-a-cloud-provider.md

@@ -102,7 +102,7 @@ It attempts to retrieve credentials in the following order:
 3. From the pod running in EKS cluster via STS (SecurityTokenService).
 4. From the EC2 Instance Role.
 
-Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write).
+Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write).
 
 See [ConfigurationReference](../configuration-reference/#cloudproviderlambdaconfig) for the full configuration.
 

docs/content/en/docs-v0.44.x/user-guide/managing-piped/adding-a-platform-provider.md

@@ -100,7 +100,7 @@ It attempts to retrieve credentials in the following order:
 3. From the pod running in EKS cluster via STS (SecurityTokenService).
 4. From the EC2 Instance Role.
 
-Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write).
+Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write).
 
 See [ConfigurationReference](../configuration-reference/#platformproviderlambdaconfig) for the full configuration.
 

docs/content/en/docs-v0.45.x/installation/install-control-plane/installing-controlplane-on-k8s.md

@@ -62,7 +62,7 @@ spec:
 
 See [ConfigurationReference](../../../user-guide/managing-controlplane/configuration-reference/) for the full configuration.
 
-After all, install the Control Plane as bellow:
+After that, install the Control Plane as below:
 
 ``` console
 helm upgrade -i pipecd oci://ghcr.io/pipe-cd/chart/pipecd --version {{< blocks/latest_version >}} --namespace={NAMESPACE} \

docs/content/en/docs-v0.45.x/user-guide/managing-application/customizing-deployment/custom-sync.md

@@ -43,7 +43,7 @@ spec:
 Note:
 1. You can use `CUSTOM_SYNC` with any current supporting application kind, but keep `alwaysUsePipeline` true to not run the application kind's default `QUICK_SYNC`.
 2. Only one `CUSTOM_SYNC` stage should be used in an application pipeline.
-3. The commands run with the enviroment variable `PATH` that refers `~/.piped/tools` at first.
+3. The commands run with the environment variable `PATH` that refers `~/.piped/tools` at first.
 
 The public piped image available in PipeCD main repo (ref: [Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/cmd/piped/Dockerfile)) is based on [alpine](https://hub.docker.com/_/alpine/) and only has a few UNIX command available (ref: [piped-base Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/tool/piped-base/Dockerfile)). If you want to use your commands (`sam` in the above example), you can:
 

docs/content/en/docs-v0.45.x/user-guide/managing-piped/adding-a-cloud-provider.md

@@ -102,7 +102,7 @@ It attempts to retrieve credentials in the following order:
 3. From the pod running in EKS cluster via STS (SecurityTokenService).
 4. From the EC2 Instance Role.
 
-Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write).
+Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write).
 
 See [ConfigurationReference](../configuration-reference/#cloudproviderlambdaconfig) for the full configuration.
 

docs/content/en/docs-v0.45.x/user-guide/managing-piped/adding-a-platform-provider.md

@@ -100,7 +100,7 @@ It attempts to retrieve credentials in the following order:
 3. From the pod running in EKS cluster via STS (SecurityTokenService).
 4. From the EC2 Instance Role.
 
-Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write).
+Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write).
 
 See [ConfigurationReference](../configuration-reference/#platformproviderlambdaconfig) for the full configuration.
 

docs/content/en/docs-v0.46.x/user-guide/managing-application/customizing-deployment/custom-sync.md

@@ -43,7 +43,7 @@ spec:
 Note:
 1. You can use `CUSTOM_SYNC` with any current supporting application kind, but keep `alwaysUsePipeline` true to not run the application kind's default `QUICK_SYNC`.
 2. Only one `CUSTOM_SYNC` stage should be used in an application pipeline.
-3. The commands run with the enviroment variable `PATH` that refers `~/.piped/tools` at first.
+3. The commands run with the environment variable `PATH` that refers `~/.piped/tools` at first.
 
 The public piped image available in PipeCD main repo (ref: [Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/cmd/piped/Dockerfile)) is based on [alpine](https://hub.docker.com/_/alpine/) and only has a few UNIX command available (ref: [piped-base Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/tool/piped-base/Dockerfile)). If you want to use your commands (`sam` in the above example), you can: