typo fixed in REVIEW_GUIDELINES.md (#15006)

Signed-off-by: Rajiv Ranjan Singh <[email protected]>

REVIEW_GUIDELINES.md

@@ -14,13 +14,13 @@ Note, if a reviewer who is not an approver in an OWNERS file leaves a comment of
 
 ## Immutability
 
-Chart releases must be immutable. Any change to a chart warrants a chart version bump even if it is only changes to the documentation.
+Chart releases must be immutable. Any change to a chart warrants a chart version bump even if it is only changed to the documentation.
 
 ## Versioning
 
 The chart `version` should follow [semver](https://semver.org/).
 
-Stable charts should start at `1.0.0` (for maintainability don't create new PRs for stable charts only to meet this criteria, but when reviewing PRs take the opportunity to ensure that this is met).
+Stable charts should start at `1.0.0` (for maintainability don't create new PRs for stable charts only to meet these criteria, but when reviewing PRs take the opportunity to ensure that this is met).
 
 Any breaking (backwards incompatible) changes to a chart should:
 
@@ -40,7 +40,7 @@ The `Chart.yaml` should be as complete as possible. The following fields are man
 
 ## Dependencies
 
-Stable charts should not depend on charts in incubator.
+Stable charts should not depend on charts in the incubator.
 
 ## Names and Labels
 
@@ -74,7 +74,7 @@ selector:
 If a chart has multiple components, a `component` label should be added to the selector (see above).
 
 `spec.selector.matchLabels` defined in `Deployments`/`StatefulSets`/`DaemonSets` `>=v1/beta2` **must not** contain `helm.sh/chart` label or any label containing a version of the chart, because the selector is immutable.
-The chart label string contains the version, so if it is specified, whenever the the Chart.yaml version changes, Helm's attempt to change this immutable field would cause the upgrade to fail.
+The chart label string contains the version, so if it is specified, whenever the Chart.yaml version changes, Helm's attempt to change this immutable field would cause the upgrade to fail.
 
 #### Fixing Selectors
 
@@ -327,24 +327,24 @@ spec:
 
 ## Documentation
 
-`README.md` and `NOTES.txt` are mandatory. `README.md` should contain a table listing all configuration options. `NOTES.txt` should provide accurate and useful information how the chart can be used/accessed.
+`README.md` and `NOTES.txt` are mandatory. `README.md` should contain a table listing all configuration options. `NOTES.txt` should provide accurate and useful information on how the chart can be used/accessed.
 
 ## Compatibility
 
-We officially support compatibility with the current and the previous minor version of Kubernetes. Generated resources should use the latest possible API versions compatible with these versions. For extended backwards compatibility conditional logic based on capabilities may be used (see [built-in objects](https://github.com/helm/helm/blob/master/docs/chart_template_guide/builtin_objects.md)).
+We officially support compatibility with the current and the previous minor version of Kubernetes. Generated resources should use the latest possible API versions compatible with these versions. For extended backwards compatibility, conditional logic based on capabilities may be used (see [built-in objects](https://github.com/helm/helm/blob/master/docs/chart_template_guide/builtin_objects.md)).
 
 ## Kubernetes Native Workloads
 
 While reviewing Charts that contain workloads such as [Deployments](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/), [StatefulSets](https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/), [DaemonSets](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/) and [Jobs](https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/) the below points should be considered.  These are to be seen as best practices rather than strict enforcement.
 
-1. Any workload that are stateless and long running (servers) in nature are to be created as Deployments.  Deployments in turn create ReplicaSets.
+1. Any workload that is stateless and long-running (servers) in nature are to be created as Deployments.  Deployments, in turn, create ReplicaSets.
 2. Unless there is a compelling reason, ReplicaSets or ReplicationControllers should be avoided as workload types.
 3. Workloads that are stateful in nature such as databases, key-value stores, message queues, in-memory caches are to be created as StatefulSets
 4. It is recommended that Deployments and StatefulSets configure their workloads with a [Pod Disruption Budget](https://kubernetes.io/docs/concepts/workloads/pods/disruptions/) for high availability.
 5. For workloads such as databases, KV stores, etc., that replicate data, it is recommended to configure interpod anti-affinity.
 6. It is recommended to have a default workload update strategy configured that is suitable for this chart.
 7. Batch workloads are to be created using Jobs.
-8. It is best to always create workloads with the latest supported [api version](https://v1-8.docs.kubernetes.io/docs/api-reference/v1.8/) as older version are either deprecated or soon to be deprecated.
+8. It is best to always create workloads with the latest supported [api version](https://v1-8.docs.kubernetes.io/docs/api-reference/v1.8/) as the older version are either deprecated or soon to be deprecated.
 9. It is generally not advisable to provide hard [resource limits](https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/#resource-requests-and-limits-of-pod-and-container) to workloads and leave it configurable unless the workload requires such quantity bare minimum to function.
 10. As much as possible complex pre-app setups are configured using [init containers](https://kubernetes.io/docs/concepts/workloads/pods/init-containers/).
 
@@ -358,4 +358,3 @@ This repository follows a [test procedure](https://github.com/helm/charts/blob/m
 The `ci` directory of a given Chart allows testing different use cases, by allowing you to define different sets of values overriding `values.yaml`, one file per set. See the [documentation](https://github.com/helm/charts/blob/master/test/README.md#providing-custom-test-values) for more information.
 
 This directory MUST exist with at least one test file in it.
-