fix: typo and grammar

Author: e-esakman

ADOPTERS.md

@@ -1,6 +1,6 @@
 # Adopters
 
-This list represents the collection of organizations that are using PipeCD within their environments. If you are currently utilizing PipeCD and not yet on this list, we strongly encourage you to add your organization here as well!
+This list represents the collection of organizations that are using PipeCD within their environments. If you are currently using PipeCD and not yet on this list, we strongly encourage you to add your organization here as well!
 
 The objective of this list is to serve as a comprehensive and authoritative resource for the entire PipeCD adopter community, while also inspiring those who are embarking on their PipeCD journey.
 

docs/rfcs/0002-lambda-deployment.md

@@ -3,7 +3,7 @@
 
 # Summary
 
-This RFC proposes adding a new service deployment from PipeCD: AWS Lambda deployment. Similar to the current [Google clould run deployment](https://pipecd.dev/docs/feature-status/#cloudrun-deployment).
+This RFC proposes adding a new service deployment from PipeCD: AWS Lambda deployment. Similar to the current [Google cloud run deployment](https://pipecd.dev/docs/feature-status/#cloudrun-deployment).
 
 # Motivation
 
@@ -58,7 +58,7 @@ Lambda function could also be deployed via source code by 2 steps method:
 1. Configure piped to be able to clone the source of Lambda function ( on the same repo which deployment be handled by piped or via remote git repo ).
 2. Compress the source code and deploy with [SAM](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-sam-cli-command-reference.html) or using [aws-sdk](https://github.com/aws/aws-lambda-go) ( piped handle the deployment ).
 
-The deployment configuration sample as bellow:
+The deployment configuration sample as below:
 
 In case of source code for Lambda function is on the same repo handled by Piped
 ```yaml

docs/rfcs/0007-deployment-chain.md

@@ -105,7 +105,7 @@ The above configuration will provide a deployment chain as follow
 
 ## More examples regards known use-cases
 
-The above configuration contains sample for a completely flexsible deployment chain (multiple applications with difference kinds deployed across environment). For clarity, here are some examples for each known use-cases listed in [above section](#motivation)
+The above configuration contains a sample for a completely flexible deployment chain (multiple applications with different kinds deployed across environments). For clarity, here are some examples for each known use-cases listed in [above section](#motivation)
 
 ### Use-case <1>: chain of deployments contains multiple applications cross kinds
 ![image](assets/deployment-chain-kind.png)

docs/rfcs/0014-multi-cluster-deployment-for-k8s.md

@@ -247,14 +247,13 @@ Performs Drift Detection based on the livestate of all platform providers deploy
 Currently, we need to prepare the kubeconfig file manually.
 But it would be nice to prepare it automatically.
 
-It might realize it by using cloud vender feature, for example using Workload Identity on GKE, or IRSA on EKS.
-It means piped get kubeconfig when it starts by using them.
+It might be possible by using cloud vendor features, for example Workload Identity on GKE or IRSA on EKS. This would allow piped to obtain the kubeconfig at startup.
 
 # Alternatives
 
 ## Idea: Execute Stages in parallel within a pipeline
 
-![image](assets/0014-pipeline-paralell-stage.png)
+![image](assets/0014-pipeline-parallel-stage.png)
 
 ### UX
 

docs/rfcs/0017-deployment-trace.md

@@ -44,7 +44,7 @@ message DeploymentTrace {
 }
 ```
 
-The idea is to use `commit_hash` to the reference keys to link between a deployment trace with all deployments triggred by the same change in application repo (commit_hash referrenced commit). Once we could built the deploymen trace object that contains commit_hash and add `commit_hash` value to deployment model objects, we can query for deployment trace and show it to the UI.
+The idea is to use `commit_hash` to the reference keys to link between a deployment trace with all deployments triggered by the same change in application repo (commit_hash referenced commit). Once we build the deployment trace object that contains commit_hash and add `commit_hash` value to deployment model objects, we can query for deployment trace and show it to the UI.
 
 The deployment model will add one field like this