Fix typos (#1756)

* childs -> children

* toogle -> toggle

* controll -> controller

* overwride -> overwrite

* requsites -> requisites

* Isntances -> Instances

* intergration -> integration

* fix newlines

* sme -> some

Author: xrstf

.codespell.exclude

@@ -1,3 +1,2 @@
 iam
 aks
-childs

content/kubeone/v1.0/prerequisites/_index.en.md

@@ -26,7 +26,7 @@ Make sure that you have:
 
 [getting-kubeone]: {{< ref "../getting_kubeone" >}}
 [kubeone-terraform-configs]: {{< ref "../concepts#example-terraform-configs" >}}
-[kubeone-terraform-integration]: {{< ref "../concepts#kubeone-terraform-intergration" >}}
+[kubeone-terraform-integration]: {{< ref "../concepts#kubeone-terraform-integration" >}}
 [install-terraform]: https://learn.hashicorp.com/terraform/getting-started/install.html
 [compatibility]: {{< ref "../compatibility_info#supported-terraform-versions" >}}
 [config-credentials]: {{< ref "./credentials" >}}

content/kubeone/v1.2/prerequisites/_index.en.md

@@ -26,7 +26,7 @@ Make sure that you have:
 
 [getting-kubeone]: {{< ref "../getting_kubeone" >}}
 [kubeone-terraform-configs]: {{< ref "../concepts#example-terraform-configs" >}}
-[kubeone-terraform-integration]: {{< ref "../concepts#kubeone-terraform-intergration" >}}
+[kubeone-terraform-integration]: {{< ref "../concepts#kubeone-terraform-integration" >}}
 [install-terraform]: https://learn.hashicorp.com/terraform/getting-started/install.html
 [compatibility]: {{< ref "../compatibility_info#supported-terraform-versions" >}}
 [config-credentials]: {{< ref "./credentials" >}}

content/kubermatic/main/cheat-sheets/etcd/legacy-restore/_index.en.md

@@ -8,7 +8,7 @@ weight = 20
 {{% notice warning %}}
 This page documents a **manual** restore procedure in case the legacy backup controllers were used to create
 the backup object in question. KKP v2.24 has removed the legacy backup controllers. The current implementation
-supports [automated restores]({{< ref "../../../tutorials-howtos/etcd-backups/" >}}), so this procedure should 
+supports [automated restores]({{< ref "../../../tutorials-howtos/etcd-backups/" >}}), so this procedure should
 **not** be used. Use the restore functionality in KKP directly instead.
 {{% /notice %}}
 

content/kubermatic/main/installation/upgrading/upgrade-from-2.24-to-2.25/_index.en.md

@@ -34,7 +34,7 @@ For KKP 2.25 several charts for user cluster MLA (`loki-distributed` and `cortex
 
 The default values shipped with KKP have been updated accordingly:
 
-- [`values.yaml` for `loki-distributed`](https://github.com/kubermatic/kubermatic/blob/v2.25.0/charts/mla/loki-distributed/values.yaml) 
+- [`values.yaml` for `loki-distributed`](https://github.com/kubermatic/kubermatic/blob/v2.25.0/charts/mla/loki-distributed/values.yaml)
 - [`values.yaml` for `cortex`](https://github.com/kubermatic/kubermatic/blob/v2.25.0/charts/mla/cortex/values.yaml)
 
 If the `values.yaml` shipped by default in KKP have been copied / modified to be used for passing configuration, the modifications need to be migrated to the new structure before upgrading the user cluster MLA stack. Full upstream values are linked from each default values shipped by KKP.

content/kubermatic/main/tutorials-howtos/administration/admin-panel/custom-links/_index.en.md

@@ -49,7 +49,7 @@ After enabling demo information checkbox `Demo system` information will be shown
 
 ## What's New
 
-After enabling What's new checkbox, `What's New` option will be shown in the KKP UI help panel. It links to release 
+After enabling What's new checkbox, `What's New` option will be shown in the KKP UI help panel. It links to release
 notes in the docs which displays new features and breaking or action required changes in the current release.
 
 ![Help Panel](@/images/ui/help-panel.png?classes=shadow,border "Help Panel")

content/kubermatic/main/tutorials-howtos/applications/_index.en.md

@@ -7,4 +7,4 @@ weight = 5
 This section provides guides on applications in KKP. For a more details on Applications refer to our [Applications Primer]({{< ref "../../architecture/concept/kkp-concepts/applications/" >}}).
 
 {{% children depth=5 %}}
-{{% /children %}}
+{{% /children %}}

content/kubermatic/main/tutorials-howtos/applications/default-enforced-applications/_index.en.md

@@ -110,4 +110,4 @@ If `defaultVersion` is specified in the `ApplicationDefinition`, it will be used
 
 ### Configuring default and enforced applications
 
-Applications can be be marked as default and enforced from the admin panel in KKP UI as well as from the APIs directly. For more details refer to the [Applications]({{< ref "../../administration/admin-panel/applications/" >}}) section.
+Applications can be be marked as default and enforced from the admin panel in KKP UI as well as from the APIs directly. For more details refer to the [Applications]({{< ref "../../administration/admin-panel/applications/" >}}) section.

content/kubermatic/main/tutorials-howtos/kkp-configuration/custom-certificates/_index.en.md

@@ -78,7 +78,7 @@ Re-deploy the `iap` Helm chart to perform the changes and update the `Certificat
 
 ### External
 
-If issuing certificates inside the cluster is not possible, static certificates can also be provided from 
+If issuing certificates inside the cluster is not possible, static certificates can also be provided from
 `Secret` resources. The cluster admin is responsible for renewing and updating them as needed. A TLS secret
 can be created via `kubectl` when certificate and private key are available:
 
@@ -181,7 +181,7 @@ spec:
   # master cluster and on all seeds, user clusters.
   caBundle:
     kind: ConfigMap
-    # name of the ConfigMap; e.g. 'ca-bundle-customized' if you created your CA bundle ConfigMap. 
+    # name of the ConfigMap; e.g. 'ca-bundle-customized' if you created your CA bundle ConfigMap.
     # must be in the same namespace as KKP.
     name: ca-bundle
 ```

content/kubermatic/main/tutorials-howtos/monitoring-logging-alerting/master-seed/installation/_index.en.md

@@ -126,32 +126,32 @@ With this file prepared, we can now install all required charts:
 Output will be similar to this:
 ```bash
 INFO[0000] 🚀 Initializing installer…                     edition="Community Edition" version=X.Y
-INFO[0000] 🚦 Validating the provided configuration…     
-INFO[0000] ✅ Provided configuration is valid.           
-INFO[0000] 🚦 Validating existing installation…          
-INFO[0000] ✅ Existing installation is valid.            
-INFO[0000] 🛫 Deploying KKP Seed MLA Stack…              
-INFO[0000]    📦 Deploying Node Exporter ...             
-INFO[0006]    ✅ Success.                                
-INFO[0006]    📦 Deploying Kube State Metrics…           
-INFO[0022]    ✅ Success.                                
-INFO[0022]    📦 Deploying Grafana…                      
-INFO[0055]    ✅ Success.                                
-INFO[0055]    📦 Deploying Blackbox Exporter…            
-INFO[0064]    ✅ Success.                                
-INFO[0064]    📦 Deploying Alert Manager…                
-INFO[0074]    ✅ Success.                                
-INFO[0074]    📦 Deploying Prometheus…                   
-INFO[0075]    ✅ Success.                                
-INFO[0075]    📦 Deploying Helm Exporter…                
-INFO[0076]    ✅ Success.                                
-INFO[0076]    📦 Deploying Karma…                        
-INFO[0078]    ✅ Success.                                
-INFO[0078]    📦 Deploying Loki…                         
-INFO[0164]    ✅ Success.                                
-INFO[0164]    📦 Deploying Promtail…                     
-INFO[0166]    ✅ Success.                                
-INFO[0166] 🛬 Installation completed successfully. Time for a break, maybe? ☺ 
+INFO[0000] 🚦 Validating the provided configuration…
+INFO[0000] ✅ Provided configuration is valid.
+INFO[0000] 🚦 Validating existing installation…
+INFO[0000] ✅ Existing installation is valid.
+INFO[0000] 🛫 Deploying KKP Seed MLA Stack…
+INFO[0000]    📦 Deploying Node Exporter ...
+INFO[0006]    ✅ Success.
+INFO[0006]    📦 Deploying Kube State Metrics…
+INFO[0022]    ✅ Success.
+INFO[0022]    📦 Deploying Grafana…
+INFO[0055]    ✅ Success.
+INFO[0055]    📦 Deploying Blackbox Exporter…
+INFO[0064]    ✅ Success.
+INFO[0064]    📦 Deploying Alert Manager…
+INFO[0074]    ✅ Success.
+INFO[0074]    📦 Deploying Prometheus…
+INFO[0075]    ✅ Success.
+INFO[0075]    📦 Deploying Helm Exporter…
+INFO[0076]    ✅ Success.
+INFO[0076]    📦 Deploying Karma…
+INFO[0078]    ✅ Success.
+INFO[0078]    📦 Deploying Loki…
+INFO[0164]    ✅ Success.
+INFO[0164]    📦 Deploying Promtail…
+INFO[0166]    ✅ Success.
+INFO[0166] 🛬 Installation completed successfully. Time for a break, maybe? ☺
 ```
 
 ### Going Further

content/kubermatic/main/tutorials-howtos/networking/expose-strategies/_index.en.md

@@ -29,7 +29,7 @@ which limits the number of total clusters per Seed based on the NodePort range c
 
 By default, the nodeport-proxy is enabled for this expose strategy. If services of type LoadBalancer are
 available in the Seed, all the services of all user clusters will be made available through a single LoadBalancer
-service in front of the nodeport-proxy. This approach however has a limitation on sme cloud platforms, where the
+service in front of the nodeport-proxy. This approach however has a limitation on some cloud platforms, where the
 number of listeners per load balancer is limited, which can limit the total number of user clusters per Seed even more.
 [The nodeport-proxy can be disabled](#disabling-nodeport-proxy-for-the-nodeport-expose-strategy)
 if your platform doesn't support LoadBalancer services or if the front LoadBalancer service is not required.

content/kubermatic/main/tutorials-howtos/storage/disable-csi-driver/_index.en.md

@@ -48,4 +48,4 @@ spec:
   disableCsiDriver: true
 ```
 
-User clusters that already have the CSI driver addon installed can also be updated to disable the CSI driver addon using the `disableCsiDriver: true` option. However, before doing this the cluster admin must ensure that none of the PVCs & PVs that belong to the storage class that has the CSI driver as the provisioner are in use, if there is any PVC that belongs to a storage class that uses the CSI driver KKP will not disable it. If for any reason the admin removes the storage class even if it has PVs that are in use & then disables the CSI driver, it will have an undesired impact on the cluster. Hence, it is expected that the admin is careful while making this change & does not remove the storage class before disabling the CSI driver.
+User clusters that already have the CSI driver addon installed can also be updated to disable the CSI driver addon using the `disableCsiDriver: true` option. However, before doing this the cluster admin must ensure that none of the PVCs & PVs that belong to the storage class that has the CSI driver as the provisioner are in use, if there is any PVC that belongs to a storage class that uses the CSI driver KKP will not disable it. If for any reason the admin removes the storage class even if it has PVs that are in use & then disables the CSI driver, it will have an undesired impact on the cluster. Hence, it is expected that the admin is careful while making this change & does not remove the storage class before disabling the CSI driver.

content/kubermatic/v2.12/advanced/addons/_index.en.md

@@ -57,7 +57,7 @@ helm upgrade --install --wait --timeout 300 --values values.yaml --namespace kub
 
 ##### Setting a custom docker registry
 
-In case you want to set a custom registry for all addons, you can specify the `-overwrideRegistry` flag on the `kubermatic-controller-manager` or via the helm setting `kubermatic.controller.overwriteRegistry`.
+In case you want to set a custom registry for all addons, you can specify the `-overwriteRegistry` flag on the `kubermatic-controller-manager` or via the helm setting `kubermatic.controller.overwriteRegistry`.
 It will set the specified registry on all control plane components & addons.
 
 ### How to Add a Custom Addon

content/kubermatic/v2.12/advanced/oidc_auth/_index.en.md

@@ -78,7 +78,7 @@ This is best done by directly changing the entries in the corresponding `values.
 The value for `.Values.kubermatic.auth.issuerCookieKey` can be randomly generated (e.g. `openssl rand -hex 32`) and should have 32 or 64 bytes.
 {{% /notice %}}
 
-`kubermatic-controll-manager` must be run with the following flags:
+`kubermatic-controller-manager` must be run with the following flags:
 
 ```plaintext
 --feature-gates={{ .Values.kubermatic.controller.featureGates }}  # must contain "OpenIDAuthPlugin=true"
@@ -96,7 +96,7 @@ You can set it by changing the `kubermatic.ui.config` entry in the `values.yaml`
 
 ### Root CA Certificates Chain
 
-In order to verify OIDC provider's certificate in `kubermatic-controll-manager` when establishing TLS connection a public root CA certificate is required. Ideally the whole
+In order to verify OIDC provider's certificate in `kubermatic-controller-manager` when establishing TLS connection a public root CA certificate is required. Ideally the whole
 chain including all intermediary CAs certificates. Note that we expect that all certificates will be PEM encoded.
 
 For example if the certificate used by your provider was issued by Let's Encrypt. You can visit [Let's Encrypt](https://letsencrypt.org/certificates) to download the necessary certificates

content/kubermatic/v2.13/advanced/addons/_index.en.md

@@ -57,7 +57,7 @@ helm upgrade --install --wait --timeout 300 --values values.yaml --namespace kub
 
 ##### Setting a Custom Docker Registry
 
-In case you want to set a custom registry for all addons, you can specify the `-overwrideRegistry` flag on the `kubermatic-controller-manager` or via the helm setting `kubermatic.controller.overwriteRegistry`.
+In case you want to set a custom registry for all addons, you can specify the `-overwriteRegistry` flag on the `kubermatic-controller-manager` or via the helm setting `kubermatic.controller.overwriteRegistry`.
 It will set the specified registry on all control plane components & addons.
 
 ### Accessible Addons

content/kubermatic/v2.13/advanced/oidc_auth/_index.en.md

@@ -78,7 +78,7 @@ This is best done by directly changing the entries in the corresponding `values.
 The value for `.Values.kubermatic.auth.issuerCookieKey` can be randomly generated (e.g. `openssl rand -hex 32`) and should have 32 or 64 bytes.
 {{% /notice %}}
 
-`kubermatic-controll-manager` must be run with the following flags:
+`kubermatic-controller-manager` must be run with the following flags:
 
 ```plaintext
 --feature-gates={{ .Values.kubermatic.controller.featureGates }}  # must contain "OpenIDAuthPlugin=true"
@@ -96,7 +96,7 @@ You can set it by changing the `kubermatic.ui.config` entry in the `values.yaml`
 
 ### Root CA Certificates Chain
 
-In order to verify OIDC provider's certificate in `kubermatic-controll-manager` when establishing TLS connection a public root CA certificate is required. Ideally the whole
+In order to verify OIDC provider's certificate in `kubermatic-controller-manager` when establishing TLS connection a public root CA certificate is required. Ideally the whole
 chain including all intermediary CAs certificates. Note that we expect that all certificates will be PEM encoded.
 
 For example if the certificate used by your provider was issued by Let's Encrypt. You can visit [Let's Encrypt](https://letsencrypt.org/certificates) to download the necessary certificates

content/kubermatic/v2.14/advanced/oidc_auth/_index.en.md

@@ -78,7 +78,7 @@ This is best done by directly changing the entries in the corresponding `values.
 The value for `.Values.kubermatic.auth.issuerCookieKey` can be randomly generated (e.g. `openssl rand -hex 32`) and should have 32 or 64 bytes.
 {{% /notice %}}
 
-`kubermatic-controll-manager` must be run with the following flags:
+`kubermatic-controller-manager` must be run with the following flags:
 
 ```plaintext
 --feature-gates={{ .Values.kubermatic.controller.featureGates }}  # must contain "OpenIDAuthPlugin=true"
@@ -96,7 +96,7 @@ You can set it by changing the `kubermatic.ui.config` entry in the `values.yaml`
 
 ### Root CA Certificates Chain
 
-In order to verify OIDC provider's certificate in `kubermatic-controll-manager` when establishing TLS connection a public root CA certificate is required. Ideally the whole
+In order to verify OIDC provider's certificate in `kubermatic-controller-manager` when establishing TLS connection a public root CA certificate is required. Ideally the whole
 chain including all intermediary CAs certificates. Note that we expect that all certificates will be PEM encoded.
 
 For example if the certificate used by your provider was issued by Let's Encrypt. You can visit [Let's Encrypt](https://letsencrypt.org/certificates) to download the necessary certificates

content/kubermatic/v2.21/architecture/supported-providers/kubevirt/kubevirt.en.md

@@ -446,9 +446,9 @@ What happens if we update a `VirtualMachineInstancePreset` existing in the `defa
 - The updated `VirtualMachineInstancePreset` will be reconciled from the `default` namespace into the `cluster-xyz` namespace.
 Give it some time to be reconciled. The reconciliation interval is configurable (refer to `providerReconciliationInterval`
 in [Seed configuration]({{< ref "../../../tutorials-howtos/project-and-cluster-management/seed-cluster/" >}})
-- For all `VirtualMachineIsntances` already created, this will have no impact.
+- For all `VirtualMachineInstances` already created, this will have no impact.
 Please refer to [KubeVirt Preset documentation](https://kubevirt.io/user-guide/virtual_machines/presets/#updating-a-virtualmachineinstancepreset)
-- The update will then be effective for new `VirtualMachineIsntances`.
+- The update will then be effective for new `VirtualMachineInstances`.
 
 *Note 2:* Limitation of the list of reconciled fields.
 

content/kubermatic/v2.22/tutorials-howtos/networking/expose-strategies/_index.en.md

@@ -25,7 +25,7 @@ which limits the number of total clusters per Seed based on the NodePort range c
 
 By default, the nodeport-proxy is enabled for this expose strategy. If services of type LoadBalancer are
 available in the Seed, all the services of all user clusters will be made available through a single LoadBalancer
-service in front of the nodeport-proxy. This approach however has a limitation on sme cloud platforms, where the
+service in front of the nodeport-proxy. This approach however has a limitation on some cloud platforms, where the
 number of listeners per load balancer is limited, which can limit the total number of user clusters per Seed even more.
 [The nodeport-proxy can be disabled](#disabling-nodeport-proxy-for-the-nodeport-expose-strategy)
 if your platform doesn't support LoadBalancer services or if the front LoadBalancer service is not required.

content/kubermatic/v2.23/tutorials-howtos/networking/expose-strategies/_index.en.md

@@ -28,7 +28,7 @@ which limits the number of total clusters per Seed based on the NodePort range c
 
 By default, the nodeport-proxy is enabled for this expose strategy. If services of type LoadBalancer are
 available in the Seed, all the services of all user clusters will be made available through a single LoadBalancer
-service in front of the nodeport-proxy. This approach however has a limitation on sme cloud platforms, where the
+service in front of the nodeport-proxy. This approach however has a limitation on some cloud platforms, where the
 number of listeners per load balancer is limited, which can limit the total number of user clusters per Seed even more.
 [The nodeport-proxy can be disabled](#disabling-nodeport-proxy-for-the-nodeport-expose-strategy)
 if your platform doesn't support LoadBalancer services or if the front LoadBalancer service is not required.

content/kubermatic/v2.24/tutorials-howtos/monitoring-logging-alerting/master-seed/customization/thanos.md

@@ -7,7 +7,7 @@ weight = 20
 
 This page explains how we can integrate [Thanos](https://thanos.io/) long term storage of metrics with KKP seed Prometheus
 
-## Pre-requsites
+## Prerequisites
 1. Helm is installed.
 1. KKP v2.22.4+ is installed in the cluster.
 1. KKP Prometheus chart has been deployed in each seed where you want to store long term metrics
@@ -20,16 +20,16 @@ Below page outlines
 
 ## Install thanos chart
 
-You can install the Thanos Helm chart from Bitnami chart repository 
+You can install the Thanos Helm chart from Bitnami chart repository
 ```shell
 HELM_EXPERIMENTAL_OCI=1 helm upgrade --install thanos \
   --namespace monitoring --create-namespace\
    --version 12.8.6 \
   -f thanos-values.yaml \
-  oci://registry-1.docker.io/bitnamicharts/thanos 
+  oci://registry-1.docker.io/bitnamicharts/thanos
 ```
 
-### Basic Thanos Customization file 
+### Basic Thanos Customization file
 You can configure Thanos to store the metrics in any s3 compatible storage as well as many other popular cloud storage solutions.
 
 Below yaml snippet uses Azure Blob storage configuration. You can refer to all [supported object storage configurations](https://thanos.io/tip/thanos/storage.md/#supported-clients).
@@ -93,7 +93,7 @@ prometheus:
     - name: thanos
       mountPath: /etc/thanos
       secretName: prometheus-thanos
-  
+
   # Add thanos sidecar to prometheus pods
   sidecarContainers:
     thanos: