DOC: Fixed typos and errors in documentation (#816)

Author: michizhou

docs/setup/install/installation-configuration.md

@@ -27,10 +27,10 @@ helm install devtron devtron/devtron-operator --create-namespace --namespace dev
 |AZURE_BLOB_CONTAINER_CI_LOG | Name of container created for storing CI_LOG| ci-log-container| Optional|
 |AZURE_BLOB_CONTAINER_CI_CACHE | Name of container created for storing CI_CACHE| ci-cache-container| Optional|
 |BLOB_STORAGE_PROVIDER | Cloud provider name which you will use| MINIO| Mandatory (If using any cloud other than MINIO), MINIO/AZURE/S3|
-|DEFAULT_BUILD_LOGS_BUCKET | S3 Bucket name used for storing Build Logs| devtron-ci-log| Mandoatory (If using AWS)|
+|DEFAULT_BUILD_LOGS_BUCKET | S3 Bucket name used for storing Build Logs| devtron-ci-log| Mandatory (If using AWS)|
 |DEFAULT_CD_LOGS_BUCKET_REGION | Region of S3 Bucket where CD Logs are being stored| us-east-1| Mandatory (If using AWS)|
 |DEFAULT_CACHE_BUCKET | S3 Bucket name used for storing CACHE (Do not include s3://)| devtron-ci-cache| Mandatory (If using AWS)|
-|DEFAULT_CACHE_BUCKET_REGION | S3 Bucket region where Cache is being stored| us-east-1| Mandoatory (If using AWS)|
+|DEFAULT_CACHE_BUCKET_REGION | S3 Bucket region where Cache is being stored| us-east-1| Mandatory (If using AWS)|
 |EXTERNAL_SECRET_AMAZON_REGION | Region where the cluster is setup for Devtron installation| ""| Mandatory (If using AWS)|
 |ENABLE_INGRESS | To enable Ingress (True/False)| False| Optional|
 |INGRESS_ANNOTATIONS | Annotations for ingress| ""| Optional|

docs/setup/install/override-default-devtron-installation-configs.md

@@ -11,7 +11,7 @@ In order to modify particular object it looks in namespace `devtroncd` for corre
 |clair| clair-config-override-cm| clair configuration|
 |dashboard| dashboard-override-cm| ui of devtron|
 |gitSensor| git-sensor-override-cm| microservice for git interaction|
-|guard| guard-override-cm| validaing webhook to block images with security violations|
+|guard| guard-override-cm| validating webhook to block images with security violations|
 |postgresql| postgresql-override-cm| db store of devtron|
 |imageScanner| image-scanner-override-cm| image scanner for vulnerability|
 |kubewatch| kubewatch-override-cm| watches changes in ci and cd running in different clusters|
@@ -76,7 +76,7 @@ After files being applied, you are ready to install your Devtron instance with p
 ### Post-Devtron Installation
 If you have an existing Devtron instance and want to migrate it for production ready deployments, this is the right option for you.
 
-In the existing namesapce, apply the production overrides as we do it above.
+In the existing namespace, apply the production overrides as we do it above.
 ```bash
 kubectl apply -f prod-configs -n devtroncd
 ```

docs/user-guide/creating-application/deployment-template.md

@@ -131,11 +131,11 @@ ReadinessProbe:
 
 | Key | Description |
 | :--- | :--- |
-| `Path` | It define the path where the rediness needs to be checked. |
+| `Path` | It define the path where the readiness needs to be checked. |
 | `failureThreshold` | It defines the maximum number of failures that are acceptable before a given container is not considered as ready. |
 | `initialDelaySeconds` | It defines the time to wait before a given container is checked for readiness. |
 | `periodSeconds` | It defines the time to check a given container for readiness. |
-| `successThreshold` | It defines the number of successes required before a given container is said to fulfil the rediness probe. |
+| `successThreshold` | It defines the number of successes required before a given container is said to fulfill the readiness probe. |
 | `timeoutSeconds` | It defines the time for checking timeout. |
 | `httpHeader` | Custom headers to set in the request. HTTP allows repeated headers,You can override the default headers by defining .httpHeaders for the probe. |
 | `scheme` | Scheme to use for connecting to the host (HTTP or HTTPS). Defaults to HTTP.
@@ -231,7 +231,7 @@ Specialized containers that run before app containers in a Pod. Init containers
 ```yaml
 pauseForSecondsBeforeSwitchActive: 30
 ```
-To wait for given period of time before swith active the container.
+To wait for given period of time before switch active the container.
 
 ### Resources
 
@@ -474,7 +474,7 @@ serviceAccountName: orchestrator
 
 A service account provides an identity for the processes that run in a Pod.
 
-When you access the cluster, you are authenticated by the apiserver as a particular User Account. Processes in containers inside pod can also contact the apiserver. When you are authenticated as a particular Service Account.
+When you access the cluster, you are authenticated by the API server as a particular User Account. Processes in containers inside pod can also contact the API server. When you are authenticated as a particular Service Account.
 
 When you create a pod, if you do not create a service account, it is automatically assigned the default service account in the namespace.
 
@@ -492,7 +492,7 @@ You can specify `maxUnavailable` and `minAvailable` in a `PodDisruptionBudget`.
 
 With `minAvailable` of 1, evictions are allowed as long as they leave behind 1 or more healthy pods of the total number of desired replicas.
 
-With `maxAvailable` of 1, evictions are allowed as long as atmost 1 unhealthy replica among the total number of desired replicas.
+With `maxAvailable` of 1, evictions are allowed as long as at most 1 unhealthy replica among the total number of desired replicas.
 
 ### Application metrics Envoy Configurations
 

docs/user-guide/creating-application/git-material.md

@@ -29,7 +29,7 @@ Note:
 
 ## 3. Checkout Path
 
-After clicking on checbox, git checkout path field appears. The git checkout path is the directory where your code is pulled or cloned for the repository you specified in the previous step.
+After clicking on checkbox, git checkout path field appears. The git checkout path is the directory where your code is pulled or cloned for the repository you specified in the previous step.
 
 This field is optional in case of a single git repository application and you can leave the path as default. Devtron assigns a directory by itself when the field is left blank. The default value of this field is `./`
 

docs/user-guide/creating-application/secrets.md

@@ -29,7 +29,7 @@ There are five Data types that you can use to save your secret.
 * **Kubernetes External Secret**: The secret data of your application is fetched by Devtron externally. Then the Kubernetes External Secret is converted to Kubernetes Secret.
 * **AWS Secret Manager**: The secret data of your application is fetched from AWS Secret Manager and then converted to Kubernetes Secret from AWS Secret. 
 * **AWS System Manager**: The secret data for your application is fetched from AWS System Secret Manager and all the secrets stored in AWS System Manager are converted to Kubernetes Secret.
-* **Hashi Corp Vault**: The secret data for your application is fetched from Hashi Corp Vault and the secrets stored in Harshi Corp Vault are converted to Kubernetes Secret.
+* **Hashi Corp Vault**: The secret data for your application is fetched from Hashi Corp Vault and the secrets stored in Hashi Corp Vault are converted to Kubernetes Secret.
 
 *Note: The conversion of secrets from various data types to Kubernetes Secrets is done within Devtron and irrespective of the data type, after conversion, the Pods access `secrets` normally.*
 

docs/user-guide/global-configurations/manage-notification.md

@@ -22,7 +22,7 @@ Click on `Add` and configure SES.
 
 | Key | Description |
 | :--- | :--- |
-| `Configuation Name` | Give a name to the SES Configuration |
+| `Configuration Name` | Give a name to the SES Configuration |
 | `Access Key ID` | Valid AWS Access Key ID |
 | `Secret Access Key` | Valid AWS Secret Access Key |
 | `AWS Region` | Select the AWS Region from the drop-down menu |

docs/user-guide/global-configurations/user-access.md

@@ -3,7 +3,7 @@
 
 {% embed url="https://www.youtube.com/watch?v=VTqBRIFbuSU" caption="" %}
 
-Like any entreprise product, Devtron supports fine grained access control to the resources based on
+Like any enterprise product, Devtron supports fine grained access control to the resources based on
 1. Type of action allowed on the Devtron resources (Create Vs View)
 2. Sensitivity of the data (Editing image Vs Editing memory)
 

docs/user-guide/user-guide.md

@@ -16,8 +16,8 @@ It is designed as a self-serve platform for operationalizing and maintaining app
 
 #### Zero code software delivery workflow
 
-* Workflow which understands the domain of **kubernetes, testing, CD, SecOps** so that you dont have to write scripts
-* Reusable and composable components so that workflows are easy to contruct and reason through
+* Workflow which understands the domain of **kubernetes, testing, CD, SecOps** so that you don't have to write scripts
+* Reusable and composable components so that workflows are easy to construct and reason through
 
 #### Multi cloud deployment
 
@@ -53,7 +53,7 @@ It is designed as a self-serve platform for operationalizing and maintaining app
 
 #### Gitops aware
 
-* Gitops exposed through API and UI so that you dont have to interact with git cli
+* Gitops exposed through API and UI so that you don't have to interact with git cli
 * Gitops backed by postgres for easier analysis
 * Enforce finer access control than git