chore: Fix spelling mistakes reported by typos

Author: lfrancke

modules/ROOT/pages/kubernetes/gke.adoc

@@ -3,6 +3,6 @@
 
 https://cloud.google.com/kubernetes-engine[https://cloud.google.com/kubernetes-engine{external-link-icon}^]
 
-Autopilot clusters are not suported, as the xref:secret-operator:index.adoc[secret-operator] requires special privileges that are not granted in Autopilot clusters.
+Autopilot clusters are not supported, as the xref:secret-operator:index.adoc[secret-operator] requires special privileges that are not granted in Autopilot clusters.
 
 Other than that no special steps are needed.

modules/ROOT/pages/release-guide.adoc

@@ -1,7 +1,7 @@
 :description: Work-in-progress internal guide with the git and cargo steps to cut a release and bump the next development version.
 
 
-(this is work in progress that is why it's not explicitely linked in nav.doc)
+(this is work in progress that is why it's not explicitly linked in nav.doc)
 
 Prerequisites:
 

modules/ROOT/partials/release-notes/release-22.9.adoc

@@ -12,7 +12,7 @@ The following new major platform features were added:
 
 ===== OpenShift compatibility
 
-We have made continued progress towards OpenShift compability, and the following operators can now be previewed on OpenShift.
+We have made continued progress towards OpenShift compatibility, and the following operators can now be previewed on OpenShift.
 Further improvements are expected in future releases, but no stability or compatibility guarantees are currently made for OpenShift clusters.
 
 * https://github.com/stackabletech/airflow-operator/pull/127[Apache Airflow]

modules/ROOT/partials/release-notes/release-24.3.adoc

@@ -321,7 +321,7 @@ The `spec.version` field has been removed.
 
 The `spec.mode` field is now required and must be set to `cluster`.
 
-The `spec.mainClass` field is now required and must point to a location on ths file system or S3 where the main class is located.
+The `spec.mainClass` field is now required and must point to a location on the file system or S3 where the main class is located.
 ====
 
 * https://github.com/stackabletech/spark-k8s-operator/pull/355[Remove usage of `userClassPathFirst` properties]

modules/ROOT/partials/release-notes/release-24.7.adoc

@@ -259,7 +259,7 @@ Use "stackablectl release list" to list available releases.
 Afterwards you will need to upgrade the CustomResourceDefinitions (CRDs) installed by the Stackable Platform.
 The reason for this is that helm will uninstall the operators but not the CRDs. This can be done using `kubectl replace`.
 
-NOTE: The cluster name for the hello-world operator has been changed in this release so the CRD cannot be patched in-place. For this reason in the snipets below the CRD for this operator will be subject to a `delete` command (plus an `apply` as part of the operator rollout in the new release) instead of a `replace`.
+NOTE: The cluster name for the hello-world operator has been changed in this release so the CRD cannot be patched in-place. For this reason in the snippets below the CRD for this operator will be subject to a `delete` command (plus an `apply` as part of the operator rollout in the new release) instead of a `replace`.
 
 [source]
 ----
@@ -406,5 +406,5 @@ spec:
 IMPORTANT: Do not override this property for the 1.27 cluster version.
 
 This is necessary because the 2.x versions do not support the XML format for flow definitions anymore.
-Support for the JSON format has been addded in version 1.16 and both formats have been maintained up to (excluding) version 2.0.
+Support for the JSON format has been added in version 1.16 and both formats have been maintained up to (excluding) version 2.0.
 The next SDP release 24.11 will automatically take care of this step for you.

modules/compliance/pages/licenses.adoc

@@ -35,4 +35,4 @@ https://github.com/stackabletech/stackablectl/blob/main/LICENSE[License{external
 https://github.com/stackabletech/docker-images/blob/main/LICENSE[License{external-link-icon}^] for the product Docker images.
 
 The Docker images are built on the https://catalog.redhat.com/software/containers/ubi9-minimal/61832888c0d15aff4912fe0d[Red Hat ubi9-minimal base image{external-link-icon}^].
-It is https://www.redhat.com/licenses/EULA_Red_Hat_Universal_Base_Image_English_20190422.pdf[licensed seperately{external-link-icon}^].
+It is https://www.redhat.com/licenses/EULA_Red_Hat_Universal_Base_Image_English_20190422.pdf[licensed separately{external-link-icon}^].

modules/concepts/pages/artifact-registries/container-images.adoc

@@ -9,7 +9,7 @@ The core artifacts of the Stackable Data Platform are container images of Kubern
 
 == Images overview
 
-Every operator is packaged into its own image and every product is also packaged into its own, seperate image.
+Every operator is packaged into its own image and every product is also packaged into its own, separate image.
 Products that require multiple different processes to run, such as a coordinator and a worker, still only run off of one image;
 usually these products also only provide a single artifact that is used to run all processes.
 

modules/concepts/pages/index.adoc

@@ -3,7 +3,7 @@
 
 == Overview
 
-The xref:overview.adoc[Platform overview] is a good starting point to understand the Stackable Data Platform covering the overall architecture, deployement and configuration.
+The xref:overview.adoc[Platform overview] is a good starting point to understand the Stackable Data Platform covering the overall architecture, deployment and configuration.
 
 == General configuration mechanisms
 
@@ -19,8 +19,8 @@ Learn about how to access xref:experimental-arm64-support[ARM64-support].
 == Connectivity
 
 Many Platform components depend on other components or expose functionality that you can connect to.
-This connectivity is achived with xref:service-discovery.adoc[service discovery ConfigMaps].
-To access your Stackable operated products from outside the Kuberenetes cluster learn more about xref:service-exposition.adoc[].
+This connectivity is achieved with xref:service-discovery.adoc[service discovery ConfigMaps].
+To access your Stackable operated products from outside the Kubernetes cluster learn more about xref:service-exposition.adoc[].
 
 == Security
 

modules/concepts/pages/overrides.adoc

@@ -163,7 +163,7 @@ All override property values must be strings.
 
 For a role or role group, at the same level of `config`, you can specify `podOverrides` for any of the attributes you can configure on a Pod.
 Every Stacklet contains one or more StatefulSets, DaemonSets, or Deployments, which in turn contain a Pod template that is used by Kubernetes to create the Pods that make up the Stacklet.
-The `podOverrides` allow you to specify a fragment of a Pod template that is then overlayed over the one created by the operator.
+The `podOverrides` allow you to specify a fragment of a Pod template that is then overlaid over the one created by the operator.
 
 An example for an HDFS cluster looks as follows:
 

modules/concepts/pages/s3.adoc

@@ -119,7 +119,7 @@ spec:
 ==== Stand-alone resources
 
 To reuse S3Buckets across different applications, they can be defined as stand-alone resources. In a similar fashion, S3Connections can also be defined as stand-alone resources.
-In the example below, ony bucket is used by a DruidCluster and a second bucket is used by both a TrinoCluster and a SparkCluster. Both buckets reference the same S3Connection.
+In the example below, one bucket is used by a DruidCluster and a second bucket is used by both a TrinoCluster and a SparkCluster. Both buckets reference the same S3Connection.
 
 image::s3-fully-separated.drawio.svg[One S3Connection is referenced by two different S3Buckets. The first Bucket is referenced by a DruidCluster and the second bucket is referenced by a SparkCluster and TrinoCluster. No object is inlined.]