Fix minor typos in k8s-monitoring chart's README (#2202)

* Fix minor typos in k8s-monitoring chart's README

* Bring changes from README to its template file

Signed-off-by: Pete Wall <[email protected]>

---------

Signed-off-by: Pete Wall <[email protected]>
Co-authored-by: Pete Wall <[email protected]>

Author: mihaelmiklec

charts/k8s-monitoring/README.md

@@ -16,8 +16,8 @@ Capture all telemetry data from your Kubernetes cluster.
 <!--alex disable hooks-->
 #### Alloy no longer deployed by hooks
 
-Version 3.3 deployed the Alloy instances during a post-install Helm hook. This cause problems where Alloy instances
-were not handle properly when running upgrades or when using deployment tools like ArgoCD.
+Version 3.3 deployed the Alloy instances during a post-install Helm hook. This caused problems where Alloy instances
+were not handled properly when running upgrades or when using deployment tools like ArgoCD.
 
 When upgrading to v3.4 or later, the Alloy resources will no longer be deployed by Helm hooks, but the upgrade may fail
 with this message:

charts/k8s-monitoring/README.md.gotmpl

@@ -17,8 +17,8 @@
 <!--alex disable hooks-->
 #### Alloy no longer deployed by hooks
 
-Version 3.3 deployed the Alloy instances during a post-install Helm hook. This cause problems where Alloy instances
-were not handle properly when running upgrades or when using deployment tools like ArgoCD.
+Version 3.3 deployed the Alloy instances during a post-install Helm hook. This caused problems where Alloy instances
+were not handled properly when running upgrades or when using deployment tools like ArgoCD.
 
 When upgrading to v3.4 or later, the Alloy resources will no longer be deployed by Helm hooks, but the upgrade may fail
 with this message: