chore: UK to US words

(cherry picked from commit 49d4947)

Author: mcanouil

docs/triaging/index.qmd

@@ -2,7 +2,7 @@
 title: "Issue and Discussion Triage"
 description: |
   This guide provides instructions for effectively triaging issues and discussions on Quarto CLI GitHub repository.
-  The primary goal is to ensure that all issues and discussions are managed efficiently, helping maintain a clear and organised project workflow.
+  The primary goal is to ensure that all issues and discussions are managed efficiently, helping maintain a clear and organized project workflow.
 engine: markdown
 toc-depth: 4
 ---
@@ -12,21 +12,21 @@ toc-depth: 4
 ### Purpose
 
 This guide provides instructions for effectively triaging issues and discussions on a Quarto CLI GitHub repository.
-The primary goal is to ensure that all issues and discussions are managed efficiently, helping maintain a clear and organised project workflow.
+The primary goal is to ensure that all issues and discussions are managed efficiently, helping maintain a clear and organized project workflow.
 
 ### Scope
 
 The document covers the processes for identifying, reviewing, and managing issues and discussions.
-This includes assigning responsibilities, prioritising tasks, and ensuring all issues are directed towards the appropriate project milestones.
+This includes assigning responsibilities, prioritizing tasks, and ensuring all issues are directed towards the appropriate project milestones.
 
 ### Tech Lead Engagement
 
 Tech leads and other maintainers will be actively engaged in the ongoing triage of new project issues.
-Their involvement is crucial to maintaining the project's organisation and ensuring that issues are handled promptly and effectively.
+Their involvement is crucial to maintaining the project's organization and ensuring that issues are handled promptly and effectively.
 
-### Organisation of Issues
+### Organization of Issues
 
-Issues will be continuously organised into milestones based on a clear [Planning Horizon](#planning-horizon).
+Issues will be continuously organized into milestones based on a clear [Planning Horizon](#planning-horizon).
 This ensures that the team has a structured approach to managing the project's progress and addressing issues in a timely manner.
 
 ### All Issues and Discussions Managed in Quarto CLI Repository
@@ -67,10 +67,10 @@ All issues beyond the next Milestone will be triaged to the "Future" milestone,
 
 - Use clear and consistent labels such as [`bug`](https://github.com/quarto-dev/quarto-cli/labels/bug), [`enhancement`](https://github.com/quarto-dev/quarto-cli/labels/enhancement), [`support`](https://github.com/quarto-dev/quarto-cli/labels/support), [`maintenance`](https://github.com/quarto-dev/quarto-cli/labels/maintenance), and [`documentation`](https://github.com/quarto-dev/quarto-cli/labels/documentation) to define the nature of the issue.
   Issues are expected to have exactly one of these labels.
-- Assign additional [labels](https://github.com/quarto-dev/quarto-cli/labels/) to categorise issues based on their type such as `html`, `website`, `installers`, `crossref`, *etc.*
-- Create custom labels if necessary to better categorise issues.
+- Assign additional [labels](https://github.com/quarto-dev/quarto-cli/labels/) to categories issues based on their type such as `html`, `website`, `installers`, `crossref`, *etc.*
+- Create custom labels if necessary to better categories issues.
 
-#### Prioritisation
+#### Prioritization
 
 - Assess the severity and impact of issues to determine priority, *e.g.*:
   - use the [`regression` label](https://github.com/quarto-dev/quarto-cli/labels/regression) for bugs that appeared in a recent release
@@ -120,11 +120,11 @@ In such cases, we encourage the following actions:
 
 #### Categories
 
-- Ensure discussions are categorised based on their nature, such as [`Features Requests`](https://github.com/quarto-dev/quarto-cli/discussions/categories/feature-requests), [`Q&A`](https://github.com/quarto-dev/quarto-cli/discussions/categories/q-a), and [`Show and tell`](https://github.com/quarto-dev/quarto-cli/discussions/categories/show-and-tell).
+- Ensure discussions are categorized based on their nature, such as [`Features Requests`](https://github.com/quarto-dev/quarto-cli/discussions/categories/feature-requests), [`Q&A`](https://github.com/quarto-dev/quarto-cli/discussions/categories/q-a), and [`Show and tell`](https://github.com/quarto-dev/quarto-cli/discussions/categories/show-and-tell).
 
 #### Labels
 
-- Assign [labels](https://github.com/quarto-dev/quarto-cli/labels/) to categorise issues based on their type such as `html`, `website`, `installers`, `crossref`, *etc.*
+- Assign [labels](https://github.com/quarto-dev/quarto-cli/labels/) to categorize issues based on their type such as `html`, `website`, `installers`, `crossref`, *etc.*
 
 ### Participation