docs: Update spelling to US English (#196)

izmalk · web-flow · commit 8521e0b15177 · 2026-02-27T10:36:15.000Z
diff --git a/docs/explanation/cryptography.md b/docs/explanation/cryptography.md
@@ -17,7 +17,7 @@ All three charms in the Charmed Apache Spark solution employ pinned revisions of
 * Integration Hub for Apache Spark
 * Charmed Apache Kyuubi
 
-The Spark History Server and Charmed Apache Kyuubi use different flavours of the
+The Spark History Server and Charmed Apache Kyuubi use different flavors of the
 [Charmed Apache Spark Rock image](https://github.com/canonical/charmed-spark-rock/) whereas the Integration Hub for
 Apache Spark uses the [Integration Hub for Apache Spark Rock image](https://github.com/canonical/spark-integration-hub-rock).
 
@@ -166,4 +166,4 @@ For more information about the Kyuubi Client, see the
 The Spark History Server provides authentication integrated using the Canonical Identity Platform in combination
 with a custom design [servlet filter](https://code.launchpad.net/~data-platform/soss/+source/charmed-spark-servlet-filters/+git/charmed-spark-servlet-filters).
 This feature can be enabled by following the steps in the
-[Spark History Server authorisation How-to guide](https://charmhub.io/spark-k8s-bundle/docs/h-history-server-authorization).
+[Spark History Server authorization How-to guide](https://charmhub.io/spark-k8s-bundle/docs/h-history-server-authorization).
diff --git a/docs/explanation/security.md b/docs/explanation/security.md
@@ -80,7 +80,7 @@ Charmed Apache Spark K8s runs on top of a set of Rockcraft-based images, all bas
 available in the [Apache Spark release page](https://launchpad.net/spark-releases), on top of Ubuntu 22.04.
 The images that can be found in the [Charmed Apache Spark rock images GitHub repository](https://github.com/canonical/charmed-spark-rock) are used as the base 
 images for pods both for Spark jobs and charms. 
-The following table summarises the relation between the component and its underlying base image.
+The following table summarizes the relation between the component and its underlying base image.
 
 | Component                          | Image                                                                                                       |
 |------------------------------------|-------------------------------------------------------------------------------------------------------------|
@@ -195,7 +195,7 @@ a cloud native Identity & Access Proxy (IAP) and Access Control Decision API abl
 and mutate incoming HTTP(s) requests, fully-integrated with the Canonical Identity Platform.
 
 Refer to the [how-to enable authorization in the Spark history server](how-to-spark-history-server-auth) guide
-for more information. From a permission-wise point of view, white lists of authorised users
+for more information. From a permission-wise point of view, white lists of authorized users
 can be provided using the Spark History Server
 [charm configuration option](https://charmhub.io/spark-history-server-k8s/configurations?channel=3.4/edge).
 
@@ -214,7 +214,7 @@ Refer to the
 [COS production deployments best practices](https://charmhub.io/topics/canonical-observability-stack/reference/best-practices)
 page for more information.
 
-For more information on how to enable and customise monitoring with COS,
+For more information on how to enable and customize monitoring with COS,
 see the [Monitoring](how-to-monitoring) guide.
 
 ## Additional resources
diff --git a/docs/how-to/enable-monitoring.md b/docs/how-to/enable-monitoring.md
@@ -165,7 +165,7 @@ Congratulations, the COS now monitors the two charms.
 
 ## Customize dashboards and alert rules
 
-The `cos-configuration-k8s` charm included in the bundle can be used to customise the Grafana dashboards and alert rules.
+The `cos-configuration-k8s` charm included in the bundle can be used to customize the Grafana dashboards and alert rules.
 If needed, we provide a [default dashboard](https://github.com/canonical/spark-k8s-bundle/blob/main/releases/3.4/resources/grafana) as part
 of the bundle and dedicated dashboards for the [Spark History Server](https://github.com/canonical/spark-history-server-k8s-operator/tree/3/edge/src/grafana_dashboards)
 and [Charmed Apache Kyuubi](https://github.com/canonical/kyuubi-k8s-operator/tree/3.4/edge/src/grafana_dashboards) charms.
diff --git a/docs/how-to/index.md b/docs/how-to/index.md
@@ -49,7 +49,7 @@ See our [Monitoring](how-to-monitoring) guide.
 
 We have guides for using Spark History Server with Charmed Apache Spark:
 
-* [Authentication and authorisation](how-to-spark-history-server-auth)
+* [Authentication and authorization](how-to-spark-history-server-auth)
 * [Expose web GUI](how-to-spark-history-server-expose-web-gui)
 
 ## Security
diff --git a/docs/how-to/spark-history-server/index.md b/docs/how-to/spark-history-server/index.md
@@ -13,6 +13,6 @@ see the [Tutorial](tutorial-4-history-server) and the following guides:
 ```{toctree}
 :titlesonly:
 
-Authentication and authorisation<auth.md>
+Authentication and authorization<auth.md>
 Expose web GUI<expose-web-gui.md>
 ```
diff --git a/docs/index.md b/docs/index.md
@@ -38,7 +38,7 @@ easy-to-use application integration, and monitoring.
 | **Apache Kyuubi** | [External connections](how-to-apache-kyuubi-external-connections) • [Integrate](how-to-apache-kyuubi-integrate-with-applications) • [Metastore](how-to-apache-kyuubi-external-metastore) • [Backups](how-to-apache-kyuubi-back-up-and-restore) • [Upgrades](how-to-apache-kyuubi-upgrade) • [GPU support](how-to-apache-kyuubi-gpu) |
 | **Security** | [Overview](explanation-security) • [Enable encryption (Apache Kyuubi)](how-to-apache-kyuubi-encryption-and-passwords) • [Cryptography](explanation-cryptography) • [Self-signed certificates](how-to-self-signed-certificates) |
 
-## How the documentation is organised
+## How the documentation is organized
 
 [Tutorial](tutorial-introduction): For new users needing to learn how to use Charmed Apache Kafka <br>
 [How-to guides](how-to-index): For users needing step-by-step instructions to achieve a practical goal <br>
diff --git a/docs/tutorial/2-distributed-data-processing.md b/docs/tutorial/2-distributed-data-processing.md
@@ -316,5 +316,5 @@ The result should look similar to the following:
 2025-04-07T11:32:44.872Z [sparkd] Number of tweets containing Ubuntu: 54
 ```
 
-By default, Apache Spark stores the logs of drivers and executors as pod logs in the local file systems, which are lost once the pods are deleted. Apache Spark can store these logs in a persistent object storage system, like S3, so that they can later be retrieved and visualised by a component called Spark History Server.
+By default, Apache Spark stores the logs of drivers and executors as pod logs in the local file systems, which are lost once the pods are deleted. Apache Spark can store these logs in a persistent object storage system, like S3, so that they can later be retrieved and visualized by a component called Spark History Server.
 
diff --git a/docs/tutorial/6-apache-kyuubi.md b/docs/tutorial/6-apache-kyuubi.md
@@ -228,7 +228,7 @@ juju scale-application kyuubi-k8s 3
 
 Wait for the deployment to complete and check the model status with the `juju status` command.
 The `kyuubi-k8s` units are all in the `blocked` state now, with a message “Missing ZooKeeper integration”.
-That is because multi-node Apache Kyuubi deployments require Apache ZooKeeper for synchronisation.
+That is because multi-node Apache Kyuubi deployments require Apache ZooKeeper for synchronization.
 
 Now, deploy [Apache ZooKeeper K8s](https://charmhub.io/zookeeper-k8s) charm (three nodes, since we want high availability) and integrate it with Apache Kyuubi:
 
