Fix typos in documentation

This ensures the correct spelling of Kubernetes.

Author: MiLk

docs/content/releases/4.7.0.md

@@ -135,7 +135,7 @@ Note that PGO will rewrite some of your HBA rules when performing any TLS enable
 # Features
 
 - Custom labels can now be added and removed through the `userlabels` attribute on the `pgclusters.crunchydata.com` custom resource, in addition to extending this functionality of the `pgo label` and `pgo delete label` commands.
-- Custom labels are now applied to all of the managed Kubenretes objects associated with a Postgres cluster. These include: Deployments, Jobs, Pods, PVCs, ConfigMaps, and Secrets.
+- Custom labels are now applied to all of the managed Kubernetes objects associated with a Postgres cluster. These include: Deployments, Jobs, Pods, PVCs, ConfigMaps, and Secrets.
 - The default password hashing mechanism (`scram-sha-256`, `md5`) for PostgreSQL users can now be selected using the `--password-type` flag on [`pgo create cluster`](https://access.crunchydata.com/documentation/postgres-operator/latest/pgo-client/reference/pgo_create_cluster/). The `passwordType` attribute on the `pgclusters.crunchydata.com` custom resource can also be used for this purpose.
 - The size of the pgAdmin4 PVC can be set with the `--pvc-size` flag on the [`pgo create pgadmin`](https://access.crunchydata.com/documentation/postgres-operator/latest/pgo-client/reference/pgo_create_pgadmin/) command.
 - The storage configuration for pgAdmin 4 is now configurable. This can be configured either in the `pgo.yaml` ConfigMap in the `PGAdminStorage` section, or via the `--storage-config` flag on the [`pgo create pgadmin`](https://access.crunchydata.com/documentation/postgres-operator/latest/pgo-client/reference/pgo_create_pgadmin/) command. If nothing is set, it will default to the configuration based on `PrimaryStorage`.

docs/content/tutorial/create-cluster.md

@@ -68,7 +68,7 @@ So what just happened? Let's break down what occurs during the create cluster pr
   - The PostgreSQL Pod, when it is started, provisions a PostgreSQL database and performs other bootstrapping functions, such as creating `testuser`.
   - The pgBackRest Pod, when it is started, initializes a pgBackRest repository. Note that the pgBackRest repository is not yet ready to start taking backups, but will be after the next step!
 
-3. When the PostgreSQL Operator detects that the PostgreSQL and pgBackRest deployments are up and running, it creates a Kubenretes Job to create a pgBackRest stanza. This is necessary as part of intializing the pgBackRest repository to accept backups from our PostgreSQL cluster.
+3. When the PostgreSQL Operator detects that the PostgreSQL and pgBackRest deployments are up and running, it creates a Kubernetes Job to create a pgBackRest stanza. This is necessary as part of intializing the pgBackRest repository to accept backups from our PostgreSQL cluster.
 
 4. When the PostgreSQL Operator detects that the stanza creation is completed, it will take an initial backup of the cluster.
 

docs/content/tutorial/customize-cluster.md

@@ -126,7 +126,7 @@ pgo create cluster hippo \
 
 ## Create a High Availability PostgreSQL Cluster
 
-[High availability]({{< relref "architecture/high-availability/_index.md" >}}) allows you to deploy PostgreSQL clusters with redundancy that allows them to be accessible by your applications even if there is a downtime event to your primary instance. The PostgreSQL clusters use the distributed consensus storage system that comes with Kubernetes so that availability is tied to that of your Kubenretes clusters. For an in-depth discussion of the topic, please read the [high availability]({{< relref "architecture/high-availability/_index.md" >}}) section of the documentation.
+[High availability]({{< relref "architecture/high-availability/_index.md" >}}) allows you to deploy PostgreSQL clusters with redundancy that allows them to be accessible by your applications even if there is a downtime event to your primary instance. The PostgreSQL clusters use the distributed consensus storage system that comes with Kubernetes so that availability is tied to that of your Kubernetes clusters. For an in-depth discussion of the topic, please read the [high availability]({{< relref "architecture/high-availability/_index.md" >}}) section of the documentation.
 
 To create a high availability PostgreSQL cluster with one replica, you can run the following command:
 

internal/util/cluster.go

@@ -550,7 +550,7 @@ func StopPostgreSQLInstance(clientset kubernetes.Interface, restconfig *rest.Con
 // The name must be a valid DNS 1123 value
 // THe prefix must be a valid DNS 1123 subdomain
 //
-// The value can be validated by machinery provided by Kubenretes
+// The value can be validated by machinery provided by Kubernetes
 //
 // Ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/
 func ValidateLabels(labels map[string]string) error {