Fix Typos

Author: TotalDwarf03

docs/dashboard/index.md

@@ -15,7 +15,7 @@ Displays the compliance status of repositories against the GitHub Usage Policy.
 - **Filter Repositories:** Allows users to filter repositories based on a range of parameters.
 - **Rule Presets:** Provides predefined sets of rules for quick compliance checks.
 - **Display Rule Details:** Shows detailed information about each rule - promoting better understanding of compliance.
-- **Organisation Overview:** Offers a high-level view of the organization's compliance status, including which rule is broken the most.
+- **Organisation Overview:** Offers a high-level view of the organisation's compliance status, including which rule is broken the most.
 - **Repository Details:** Provides detailed information about individual repositories, including their compliance status and the rules they violate.
 - **Point of Contact:** Displays the point of contact for each repository, facilitating communication regarding compliance issues.
 
@@ -26,7 +26,7 @@ Displays the compliance status of repositories against the GitHub Usage Policy.
 Provides metrics on Secret Scanning alerts.
 
 - **Filter Alerts:** Allows users to filter alerts based on a range of parameters.
-- **Organisation Overview:** Offers a high-level view of the organization's secret scanning alerts, including the oldest open alert.
+- **Organisation Overview:** Offers a high-level view of the organisation's secret scanning alerts, including the oldest open alert.
 - **Respository Proportion:** Displays the proportion of repositories with secret scanning alerts - allowing users to highlight the organisation's worst repositories.
 - **Alert Details:** Shows information about individual alerts, promoting users to take action on them.
 
@@ -37,7 +37,7 @@ Provides metrics on Secret Scanning alerts.
 Displays metrics on Dependabot alerts.
 
 - **Filter Alerts:** Allows users to filter alerts based on a range of parameters.
-- **Organisation Overview:** Offers a high-level view of the organization's Dependabot alerts, including the oldest open alert and worst severity.
+- **Organisation Overview:** Offers a high-level view of the organisation's Dependabot alerts, including the oldest open alert and worst severity.
 - **Severity Proportion:** Displays the proportion of alerts by severity, allowing users to focus on the most critical issues.
 - **Repository Overview:** Provides a high-level view of the repositories with Dependabot alerts, including the number of alerts and their severity.
 - **Repository Severity Proportion:** Displays the proportion of alerts by severity for each repository, allowing users to identify the most critical issues.

docs/dashboard/repository_information.md

@@ -7,7 +7,7 @@ Dependabot and Secret Scanning alerts are collected from their respective GitHub
 - **Secret Scanning**: [`GET /orgs/{org}/secret-scanning/alerts`](https://docs.github.com/en/rest/secret-scanning/secret-scanning?apiVersion=2022-11-28#list-secret-scanning-alerts-for-an-organization)
 - **Dependabot**: [`GET /orgs/{org}/dependabot/alerts`](https://docs.github.com/en/rest/dependabot/alerts?apiVersion=2022-11-28#list-dependabot-alerts-for-an-organization)
 
-These endpoints list all alerts for the organization. The endpoint contains the name of the repository they belong to, but, unfortunately, does not contain the repository's visibility (public/private/internal) or if the repository is archived or not.
+These endpoints list all alerts for the organisation. The endpoint contains the name of the repository they belong to, but, unfortunately, does not contain the repository's visibility (public/private/internal) or if the repository is archived or not.
 
 This information is important to allow users to filter alerts appropriately, for example, any public Secret Scanning alerts are much more of a risk than private ones. We want users to be able to highlight these sorts of issues.
 

docs/dashboard/rulemap.md

@@ -6,7 +6,7 @@ In order to add more information about the rules applied to repositories, `rulem
 
 ## Where do the rules come from?
 
-All rules on the dashboard are derived from ONS' GitHub Usage Policy. This is available on Sharepoint at [GitHub Usage Policy](https://officenationalstatistics.sharepoint.com/sites/ONS_DDaT_Communities/Software%20Engineering%20Policies/Forms/AllItems.aspx?id=%2Fsites%2FONS%5FDDaT%5FCommunities%2FSoftware%20Engineering%20Policies%2FSoftware%20Engineering%20Policies%2FApproved%2FPDF%2FGitHub%20Usage%20Policy%2Epdf&parent=%2Fsites%2FONS%5FDDaT%5FCommunities%2FSoftware%20Engineering%20Policies%2FSoftware%20Engineering%20Policies%2FApproved%2FPDF) (requires ONS network access).
+All rules on the dashboard are derived from ONS' GitHub Usage Policy.
 
 ##  Format
 
@@ -97,7 +97,7 @@ Then in `rulemap.json`, you would add:
 }
 ```
 
-A new check should now appear in the Dashboard under the appropriate preset.
+A new check should now appear in the dashboard under the appropriate preset.
 
 ## Changing Rule Presets