Apply suggestions from code review

Co-authored-by: Chetan Banavikalmutt <[email protected]>

Author: jgwest

docs/api.md

@@ -288,9 +288,9 @@ See the [GitOpsDeploymentSyncRun API reference](https://redhat-appstudio.github.
 ## GitOps Service: Stonesoup Environment APIs
 
 The Stonesoup Environment API is based on the [Application](https://redhat-appstudio.github.io/book/ref/application-environment-api.html#application), and [Component](https://redhat-appstudio.github.io/book/ref/application-environment-api.html#component) APIs, which are primarily handled by the [application-service](https://github.com/redhat-appstudio/application-service) component. 
-- These APIs are opinionated representations of the constituent parts of a user's application: a application (e.g. a loan applicatin of a bank) contains multiple components (e.g. Node frontend, Java backend, Postgresql database).
+- These APIs are opinionated representations of the constituent parts of a user's application: a application (e.g. a loan application of a bank) contains multiple components (e.g. Node frontend, Java backend, Postgresql database).
 
-The Stonesoup Environment APIs -- which are simultaneosly reconciled by multiple Stonesoup components -- are all related to provisioning or deploying K8s resources to external environments, such as external K8s clusters/namespaces or local namespaces.
+The Stonesoup Environment APIs -- which are simultaneously reconciled by multiple Stonesoup components -- are all related to provisioning or deploying K8s resources to external environments, such as external K8s clusters/namespaces or local namespaces.
 
 ### Environment
 

docs/building.md

@@ -37,7 +37,7 @@ The final binaries are then copied into `/usr/local/bin`, which is where they ar
 
 ### Build and push: using docker/podman
 
-You may user docker or podman to build the containers. 
+You may use docker or podman to build the containers. 
 - To use podman, pass `DOCKER=podman` on the `make` calls. 
 - For example: `USERNAME=(your quay.io username) DOCKER=podman make docker-build docker-push`
 

docs/debug.md

@@ -14,7 +14,7 @@ To reset the database to a clean state, run `./reset-db.sh`.
 
 ## Run PostgreSQL in Kubernetes
 
-* **Note**: When developing in your local development environment, it is usually easier to run Kubernetes on your local machine using `create-dev-env.sh`, as described above.
+* **Note**: When developing in your local development environment, it is usually easier to run PostgreSQL on your local machine using `create-dev-env.sh`, as described above.
 
 ### Deploy PostgreSQL
 

docs/development.md

@@ -48,7 +48,7 @@ To do that, follow these steps:
 
 For your curiosity, this _make target_ is making sure that:
 
-* cluster-agent/bacckend/backend-shared/appstudio-controller/application-api CRDs and RBAC resources are applied into the cluster 
+* cluster-agent/backend/backend-shared/appstudio-controller/application-api CRDs and RBAC resources are applied into the cluster 
 * postgres full deployment is running on the cluster
 
 In the end, you will see a similar output:

docs/install.md

@@ -12,7 +12,7 @@ make install-all-k8s IMG=quay.io/pgeorgia/gitops-service:latest # replace the IM
 ```
 
 This will automatically install all the required components into your Kubernetes cluster, in the `gitops` namespace.
-Notice that, the [Cluster-Agent] operator requires the `gitops-service-argocd` namespace which will also be created as well.
+Notice that, the [Cluster-Agent] controller requires the `gitops-service-argocd` namespace which will also be created as well.
 
 ```shell
 $ kubectl -n gitops get all