Fixed typos in various files

cert-manager/uninstall.sh

@@ -6,5 +6,5 @@ helm delete cert-manager -n=cert-manager
 # Delete the custom CRDs
 kubectl delete -f https://github.com/jetstack/cert-manager/releases/download/v1.0.2/cert-manager.crds.yaml
 
-# Delete the namaespace
+# Delete the namespace
 kubectl delete namespace cert-manager

docker-registry/post_install.md

@@ -2,8 +2,8 @@
 
 ### Creation of the certificate
 
-This will help you to create a valid certifica for your registry, you need apply this YAML file,
-you only need remplase only `registry.example.com` by your valid domain
+This will help you to create a valid certificate for your registry, you need apply this YAML file,
+you only need replace only `registry.example.com` by your valid domain
 ```yaml
 apiVersion: cert-manager.io/v1alpha2
 kind: Certificate
@@ -57,5 +57,5 @@ spec:
           serviceName: private-registry-docker-registry
           servicePort: 5000
 ```
-You only need remplase only `registry.example.com` by your valid domain.
+You only need replace only `registry.example.com` by your valid domain.
 This will open up http://registry.example.com (assuming you pointed that non-real domain record to your cluster's IPs) to the whole world.

ghost/post_install.md

@@ -22,7 +22,7 @@ By default ghost create user name `Ghost` and create example post in your blog.
 
 * Login to your ghost admin url `http://ghost.YOUR_CLUSTER_ID.k8s.civo.com/ghost`.  
 * Click the `Staff` menu in the left column.  
-* In the righ column, click the user name `Ghost`.  
+* In the right column, click the user name `Ghost`.  
 * Click the option button in the upper right ( in the left of save button ).  
 * Chose `Delete button`
 
@@ -33,7 +33,7 @@ Follow this step to create your first blog post :
 * To begin your first blog post login to ghost admin url `http://ghost.YOUR_CLUSTER_ID.k8s.civo.com/ghost`.  
 * Inside the ghost admin menu, click `Posts` menu at the left column. Click `New post` button in the upper right.  
 * Write your blog.  
-* If you want to publish your blog, click the `publish` button in the upper right. If you want to publish it later, Click the `< Posts` button in the upper left, your article should be automaticaly saved as draft.
+* If you want to publish your blog, click the `publish` button in the upper right. If you want to publish it later, Click the `< Posts` button in the upper left, your article should be automatically saved as draft.
 
 ## Modify URL
 

kubenav/uninstall.sh

@@ -3,5 +3,5 @@
 # Delete the app
 helm delete -f app.yaml
 
-# Delete the namaespace
+# Delete the namespace
 kubectl delete namespace kubenav

longhorn/post_install.md

@@ -2,7 +2,7 @@
 
 ### Installation note:
 
-Longhorn requires a minimum of 3 nodes to function, if you attempt to install Longhorn on cluster smaller than this, it will not function properly. If you have installed Longhorn on a cluster that is too small, you will encounter errors from Longhorn, but you can simply scale the cluster up to a 3 node minimum and the issue will resolve itself automatically. 
+Longhorn requires a minimum of 3 nodes to function, if you attempt to install Longhorn on cluster smaller than this, it will not function properly. If you have installed Longhorn on a cluster that is too small, you will encounter errors from Longhorn, but you can simply scale the cluster up to a 3 node minimum and the issue will resolve itself automatically.
 
 ### External access
 

maesh/post_install.md

@@ -2,4 +2,4 @@
 
 ### Usage instruction
 
-You configure your services to use Maesh with a simple annontation. For more instructions on configuring your services to use Maesh see [their website](https://docs.mae.sh/configuration/).
+You configure your services to use Maesh with a simple annotation. For more instructions on configuring your services to use Maesh see [their website](https://docs.mae.sh/configuration/).

prometheus-operator/uninstall.sh

@@ -3,5 +3,5 @@
 # Delete the custom CRDs
 kubectl delete -f app.yaml
 
-# Delete the namaespace
+# Delete the namespace
 kubectl delete namespace monitoring

system-upgrade-controller/post_install.md

@@ -10,8 +10,8 @@ Full documentation is available from Rancher at [system-upgrade-controller](http
 
 There are some [example-plans](https://github.com/rancher/system-upgrade-controller#example-plans) for you to consider using.
 
-A plan is need to start upgrade process on cluster. This is easliy by applying the following yaml manifests to your cluster with
-`kubectl apply -f civo-plan.yaml` (or whatenver you call the file containing the contents below):
+A plan is need to start upgrade process on cluster. This is easily by applying the following yaml manifests to your cluster with
+`kubectl apply -f civo-plan.yaml` (or whatever you call the file containing the contents below):
 
 ```
 # Server plan

tekton/post_install.md

@@ -12,7 +12,7 @@ This marketplace application installs three components of the Tekton Suite.  Tho
 ### Dashboard Access
 
 By default external access to the Tekton Dashboard isn't available.  As there is no built-in authentication method, it should not be exposed
-via an Ingress without additional authentication methods in place.  To easily and securly access the dashboard, use port forwarding, which will make the dashboard available at <http://localhost:9097>
+via an Ingress without additional authentication methods in place.  To easily and securely access the dashboard, use port forwarding, which will make the dashboard available at <http://localhost:9097>
 
 ```sh
 kubectl --namespace tekton-pipelines port-forward svc/tekton-dashboard 9097:9097
@@ -23,7 +23,7 @@ kubectl --namespace tekton-pipelines port-forward svc/tekton-dashboard 9097:9097
 Incoming triggers can be exposed through an Ingress.  [The core instructions](https://tekton.dev/docs/triggers/exposing-eventlisteners/) can be used with the following modifications:
 
 1. Skip step one under "Using Nginx Ingress", as the Traefik ingress should work
-2. Obtain the eventlister with a `kubectl get el <EVENTLISTENR_NAME> -o=jsonpath='{.status.configuration.generatedName}'` command
+2. Obtain the event-lister with a `kubectl get el <EVENTLISTENR_NAME> -o=jsonpath='{.status.configuration.generatedName}'` command
 3. With the service name, create an ingress as below:
    ```yaml
     apiVersion: extensions/v1beta1
@@ -42,4 +42,4 @@ Incoming triggers can be exposed through an Ingress.  [The core instructions](ht
                   servicePort: 8080
    ```
 
-This will open up http://eventlistenername.YOUR_CLUSTER_ID.k8s.civo.com to trigger the service.  Ensure your eventlistener has the necessary interceptor configuration in place to prevent unauthorized triggering of the pipeline.
+This will open up http://eventlistenername.YOUR_CLUSTER_ID.k8s.civo.com to trigger the service.  Ensure your event-listener has the necessary interceptor configuration in place to prevent unauthorized triggering of the pipeline.