[kube-prometheus-stack] Adjust comments in values.yaml file (#6242)

Author: karunsiri

charts/kube-prometheus-stack/values.yaml

@@ -34,7 +34,7 @@ crds:
   enabled: true
   ## The CRD upgrade job mitigates the limitation of helm not being able to upgrade CRDs.
   ## The job will apply the CRDs to the cluster before the operator is deployed, using helm hooks.
-  ## It deploy a corresponding clusterrole, clusterrolebinding and serviceaccount to apply the CRDs.
+  ## It deploys a corresponding clusterrole, clusterrolebinding and serviceaccount to apply the CRDs.
   ## This feature is in preview, off by default and may change in the future.
   upgradeJob:
     enabled: false
@@ -154,7 +154,7 @@ crds:
       seccompProfile:
         type: RuntimeDefault
 
-## custom Rules to override "for" and "severity" in defaultRules
+## Custom rules to override "for" and "severity" in defaultRules
 ##
 customRules: {}
   # AlertmanagerFailedReload:
@@ -260,7 +260,7 @@ defaultRules:
     prometheus: {}
     prometheusOperator: {}
 
-  ## Additional annotations for specific PrometheusRule alerts groups
+  ## Additional annotations for specific PrometheusRule alert groups
   additionalRuleGroupAnnotations:
     alertmanager: {}
     etcd: {}
@@ -338,7 +338,7 @@ global:
     ## Ref: https://kubernetes.io/docs/reference/access-authn-authz/rbac/#aggregated-clusterroles
     createAggregateClusterRoles: false
 
-  ## Global image registry to use if it needs to be overridden for some specific use cases (e.g local registries, custom images, ...)
+  ## Global image registry to use if it needs to be overridden for some specific use cases (e.g. local registries, custom images, ...)
   ##
   imageRegistry: ""
 
@@ -398,7 +398,7 @@ alertmanager:
   ##
   additionalLabels: {}
 
-  ## Api that prometheus will use to communicate with alertmanager. Possible values are v1, v2
+  ## API that Prometheus will use to communicate with alertmanager. Possible values are v1, v2
   ##
   apiVersion: v2
 
@@ -547,7 +547,7 @@ alertmanager:
     - '/etc/alertmanager/config/*.tmpl'
 
   ## Alertmanager configuration directives (as string type, preferred over the config hash map)
-  ## stringConfig will be used only, if tplConfig is true
+  ## stringConfig will be used only if tplConfig is true
   ## ref: https://prometheus.io/docs/alerting/configuration/#configuration-file
   ##      https://prometheus.io/webtools/alerting/routing-tree-editor/
   ##