Define spelling rule to British English

MattiSG · MattiSG · commit edce46997d7d · 2025-05-29T12:27:54.000+02:00
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
@@ -6,15 +6,15 @@ We as members, contributors, and leaders pledge to make participation in our
 community a harassment-free experience for everyone, regardless of age, body
 size, visible or invisible disability, ethnicity, sex characteristics, gender
 identity and expression, level of experience, education, socio-economic status,
-nationality, personal appearance, race, caste, color, religion, or sexual
+nationality, personal appearance, race, caste, colour, religion, or sexual
 identity and orientation.
 
 We pledge to act and interact in ways that contribute to an open, welcoming,
 diverse, inclusive, and healthy community.
 
 ## Our Standards
 
-Examples of behavior that contributes to a positive environment for our
+Examples of behaviour that contributes to a positive environment for our
 community include:
 
 - Demonstrating empathy and kindness toward other people
@@ -25,7 +25,7 @@ community include:
 - Focusing on what is best not just for us as individuals, but for the overall
   community
 
-Examples of unacceptable behavior include:
+Examples of unacceptable behaviour include:
 
 - The use of sexualized language or imagery, and sexual attention or advances of
   any kind
@@ -39,8 +39,8 @@ Examples of unacceptable behavior include:
 ## Enforcement Responsibilities
 
 Community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
+acceptable behaviour and will take appropriate and fair corrective action in
+response to any behaviour that they deem inappropriate, threatening, offensive,
 or harmful.
 
 Community leaders have the right and responsibility to remove, edit, or reject
@@ -58,7 +58,7 @@ representative at an online or offline event.
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
+Instances of abusive, harassing, or otherwise unacceptable behaviour may be
 reported to the community leaders responsible for enforcement at
 `moderators@opentermsarchive.org`.
 All complaints will be reviewed and investigated promptly and fairly.
@@ -73,19 +73,19 @@ the consequences for any action they deem in violation of this Code of Conduct:
 
 ### 1. Correction
 
-**Community Impact**: Use of inappropriate language or other behavior deemed
+**Community Impact**: Use of inappropriate language or other behaviour deemed
 unprofessional or unwelcome in the community.
 
 **Consequence**: A private, written warning from community leaders, providing
 clarity around the nature of the violation and an explanation of why the
-behavior was inappropriate. A public apology may be requested.
+behaviour was inappropriate. A public apology may be requested.
 
 ### 2. Warning
 
 **Community Impact**: A violation through a single incident or series of
 actions.
 
-**Consequence**: A warning with consequences for continued behavior. No
+**Consequence**: A warning with consequences for continued behaviour. No
 interaction with the people involved, including unsolicited interaction with
 those enforcing the Code of Conduct, for a specified period of time. This
 includes avoiding interactions in community spaces as well as external channels
@@ -95,7 +95,7 @@ ban.
 ### 3. Temporary Ban
 
 **Community Impact**: A serious violation of community standards, including
-sustained inappropriate behavior.
+sustained inappropriate behaviour.
 
 **Consequence**: A temporary ban from any sort of interaction or public
 communication with the community for a specified period of time. No public or
@@ -106,7 +106,7 @@ Violating these terms may lead to a permanent ban.
 ### 4. Permanent Ban
 
 **Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior, harassment of an
+standards, including sustained inappropriate behaviour, harassment of an
 individual, or aggression toward or disparagement of classes of individuals.
 
 **Consequence**: A permanent ban from any sort of public interaction within the
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -15,7 +15,9 @@ This documentation follows the [Diátaxis](https://diataxis.fr) approach and str
 - **References:** comprehensive technical documentation detailing configuration options and specifications for advanced users.
 - **Explanations:** background knowledge that enables understanding the constraints and how choices that are made.
 
+## Copywriting
 
+- Use [British English spelling](https://en.wikipedia.org/wiki/American_and_British_English_spelling_differences), not American English.
 
 ## Modifying content
 
diff --git a/content/_index.md b/content/_index.md
@@ -29,7 +29,7 @@ This documentation follows the [Diátaxis](https://diataxis.fr) approach and str
 
 ### Table of contents
 
-- **Analysis:** guidance on how to analyze terms changes, from navigating through the history of tracked terms to publishing memos about significant changes.
+- **Analysis:** guidance on how to analyse terms changes, from navigating through the history of tracked terms to publishing memos about significant changes.
 - **Community:** information on how to participate in the Open Terms Archive community.
 - **Terms:** guidance on tracking and maintaining terms declarations.
 - **Collections:** guidance on creating and managing collections of tracked terms.
diff --git a/content/analysis/how-to/navigate-history.md b/content/analysis/how-to/navigate-history.md
@@ -40,7 +40,7 @@ For this guide, we will use the example of the Demo collection. The terms of thi
 
   ![One GitHub Privacy Policy change with source diff view](/images/navigate-history/source-diff.png)
 
-- You can choose from two types of display with the icons in the grey bar above the document. The first one (which is also the default one), named _source diff_ displays the previous version and the next one either [side by side](https://github.com/OpenTermsArchive/demo-versions/commit/e9a781797041a6b593967ba9e7bb2c7404390e76?diff=split) or in a [consolidated way (with one line under the other)](https://github.com/OpenTermsArchive/demo-versions/commit/e9a781797041a6b593967ba9e7bb2c7404390e76?diff=unified). The second one, named _rich diff_ displays all the changes [in a single document](https://github.com/OpenTermsArchive/demo-versions/commit/e9a781797041a6b593967ba9e7bb2c7404390e76?short_path=060f2c2#diff-060f2c2cc43c2415e0d388f0061c37472277e76eafc9c0df269713b150a52909). In this view, beyond green and red, the yellow color shows modified paragraphs. Be careful, this display does not show some changes such as hyperlinks and text style's changes:
+- You can choose from two types of display with the icons in the grey bar above the document. The first one (which is also the default one), named _source diff_ displays the previous version and the next one either [side by side](https://github.com/OpenTermsArchive/demo-versions/commit/e9a781797041a6b593967ba9e7bb2c7404390e76?diff=split) or in a [consolidated way (with one line under the other)](https://github.com/OpenTermsArchive/demo-versions/commit/e9a781797041a6b593967ba9e7bb2c7404390e76?diff=unified). The second one, named _rich diff_ displays all the changes [in a single document](https://github.com/OpenTermsArchive/demo-versions/commit/e9a781797041a6b593967ba9e7bb2c7404390e76?short_path=060f2c2#diff-060f2c2cc43c2415e0d388f0061c37472277e76eafc9c0df269713b150a52909). In this view, beyond green and red, the yellow colour shows modified paragraphs. Be careful, this display does not show some changes such as hyperlinks and text style's changes:
 
   ![One GitHub Privacy Policy change with rich diff view](/images/navigate-history/rich-diff.png)
 
diff --git a/content/collections/how-to/create-repositories.md b/content/collections/how-to/create-repositories.md
@@ -24,7 +24,7 @@ Before starting, ensure you have:
 ### Create from template
 
 1. Go to the [`demo-declarations`](https://github.com/OpenTermsArchive/demo-declarations) repository
-2. Click "Use this template" dropdown and select "Create a new repository"
+2. Click the "Use this template" drop-down menu and select "Create a new repository"
 3. Name it `<collection_id>-declarations` (e.g. `pga-declarations`)
 4. Wait 1-2 minutes for automatic setup to complete (check `first-time-setup` action status)
 
diff --git a/content/collections/how-to/terminate.md b/content/collections/how-to/terminate.md
@@ -5,7 +5,7 @@ weight: 4
 
 # How to terminate a collection
 
-If you don't have the resources to maintain a collection anymore, follow these steps to properly terminate it. This will make it clear to users and potential successors that it is no longer actively maintained and can be taken over.
+If you don't have the resources to maintain a collection any more, follow these steps to properly terminate it. This will make it clear to users and potential successors that it is no longer actively maintained and can be taken over.
 
 ## Steps
 
diff --git a/content/collections/reference/roles.md b/content/collections/reference/roles.md
@@ -119,7 +119,7 @@ Analyses terms changes to identify significant changes and produce reports in va
 
 #### Responsibilities
 
-- Identify and analyze meaningful terms changes
+- Identify and analyse meaningful terms changes
 - Produce insights from changes
 
 #### Tasks
diff --git a/content/collections/reference/status.md b/content/collections/reference/status.md
@@ -31,6 +31,6 @@ Collection may be functional but shows clear signs of neglect.
 
 Collection has voluntarily ceased all operational activities.
 
-- No terms are tracked anymore, though historical records remain accessible for reference purposes.
+- No terms are tracked any more, though historical records remain accessible for reference purposes.
 - No technical maintenance is performed.
 - All [roles]({{< relref "collections/reference/roles" >}}) are inactive.
diff --git a/content/deployment/how-to/deploy.md b/content/deployment/how-to/deploy.md
@@ -156,7 +156,7 @@ This section uses [Ansible Vault](https://docs.ansible.com/ansible/latest/vault_
    ansible-vault encrypt .env
    ```
 
-   > **Note**: Running the command from the `deployment` folder will ensure that the `vault.key` file is used as vault key, since this folder contains an `ansible.cfg` file that explicitly configures this behavior.
+   > **Note**: Running the command from the `deployment` folder will ensure that the `vault.key` file is used as vault key, since this folder contains an `ansible.cfg` file that explicitly configures this behaviour.
    >
    > To decrypt an encrypted file, use:
    >
diff --git a/content/deployment/reference/architecture.md b/content/deployment/reference/architecture.md
@@ -67,7 +67,7 @@ The engine automatically creates issues in the declarations repository to notify
 
 ## Configuration files
 
-The system's behavior is controlled through several key configuration files:
+The system's behaviour is controlled through several key configuration files:
 
 - `inventory.yml`: Defines server address and deployment parameters
 - `production.json`: Stores application-specific settings
diff --git a/content/terms/guideline/declaring.md b/content/terms/guideline/declaring.md
@@ -11,9 +11,9 @@ aliases:
 
 ### Casing
 
-- In order to find the service name casing, rely first on the page title (easily found in search results). Do not rely on the logo as it can be stylized differently. Example with Facebook:
-![facebook search](https://user-images.githubusercontent.com/222463/91416484-baaa3a00-e84f-11ea-94cf-8805d17aa711.png)
-- If it is still ambiguous, rely on Wikipedia as a source. However, make sure to differentiate the _service_ from the _provider_ company's name. Example with “DeviantArt”, a service (which used to be stylized deviantArt until 2014) by the limited liability company “deviantArt”:
+- In order to find the service name casing, rely first on the page title (easily found in search results). Do not rely on the logo as it can be stylised differently. Example with Facebook:
+![Facebook search](https://user-images.githubusercontent.com/222463/91416484-baaa3a00-e84f-11ea-94cf-8805d17aa711.png)
+- If it is still ambiguous, rely on Wikipedia as a source. However, make sure to differentiate the _service_ from the _provider_ company's name. Example with “DeviantArt”, a service (which used to be stylised deviantArt until 2014) by the limited liability company “deviantArt”:
 ![deviantArt search](https://user-images.githubusercontent.com/222463/91416936-5b98f500-e850-11ea-80fe-a50be27356e3.png)
 
 ### Terms used by several services
diff --git a/content/terms/guideline/reviewing.md b/content/terms/guideline/reviewing.md
@@ -75,7 +75,7 @@ The pull request created will consist of fewer checks than those that add declar
 For pull requests that update declarations, you should focus should be on two things: history file and declaration.
 
 - **History file:** The history file is a JSON file that keeps track of a service declaration changes. It contains a `validUntil` property that specifies the date a specific version of a service declaration was last effective. You have to confirm that this date is the same as the date in the issue opened for the declaration when the bot couldn't track it for the first time. This issue is usually included in the pull request message. The history file is updated with every `update` pull request. You can find more information about the history file [here]({{< relref "terms/explanation/declarations-maintenance" >}}).
-- **Declaration:** for `update` pull requests, you only look at the selectors to make sure they are **simple** and also verify the **generated version** is ok.
+- **Declaration:** for `update` pull requests, you only look at the selectors to make sure they are **simple** and also verify the **generated version** is okay.
 
 ### Step-by-step Review Guide
 
@@ -129,7 +129,7 @@ Once the pull request has been merged, delete the copy you made of the branch wi
 
 When tests fail, you can follow these steps to diagnose and address the issue:
 
-1. Begin by analyzing any error messages or warnings provided by the test output. These messages can often provide meaningful information to identify the source of the problem. Pay attention to specific issues such as schema validation errors, inaccessible web locations or inaccessible content selection.
+1. Begin by analysing any error messages or warnings provided by the test output. These messages can often provide meaningful information to identify the source of the problem. Pay attention to specific issues such as schema validation errors, inaccessible web locations or inaccessible content selection.
 
 2. For a deeper investigation, you can access the snapshots and versions generated during the test run. Navigate to the summary page of the failing workflow. Scroll down to the "Artifacts" section located at the bottom of the page. Click on `snapshots_and_versions` to download them.
 

Original file line number	Diff line number	Diff line change
`@@ -156,7 +156,7 @@ This section uses [Ansible Vault](https://docs.ansible.com/ansible/latest/vault_`
`156`	`156`	`ansible-vault encrypt .env`
`157`	`157`	```
`158`	`158`
`159`		- > Note: Running the command from the `deployment` folder will ensure that the `vault.key` file is used as vault key, since this folder contains an `ansible.cfg` file that explicitly configures this behavior.
	`159`	+ > Note: Running the command from the `deployment` folder will ensure that the `vault.key` file is used as vault key, since this folder contains an `ansible.cfg` file that explicitly configures this behaviour.
`160`	`160`	`>`
`161`	`161`	`> To decrypt an encrypted file, use:`
`162`	`162`	`>`