Typo fixes

.cspell.json

@@ -460,7 +460,6 @@
     "Wireframes",
     "WORKDIR",
     "workstream",
-    "worspace",
     "yapf",
     "Zipkin",
     "zstd",
@@ -474,7 +473,6 @@
     "Automator",
     "Playstore",
     "avds",
-    "runing",
     "printscren",
     "webdriverio",
     "wdio"

docs/CI-CD/dev-sec-ops/azure-devops-service-connection-security.md

@@ -49,7 +49,7 @@ Since Service Connections can have a lot of permissions in the external service,
 
 ## Service Connection Checks
 
-To prevent accidental mis-use of Service Connections there are several checks that can be configured. These checks are configured on the Service Connection itself and therefore can only be configured by the owner or administrator of that Service Connection. A user of a certain YAML Pipeline cannot modify these checks since the checks are not defined in the YAML file itself.
+To prevent accidental misuse of Service Connections there are several checks that can be configured. These checks are configured on the Service Connection itself and therefore can only be configured by the owner or administrator of that Service Connection. A user of a certain YAML Pipeline cannot modify these checks since the checks are not defined in the YAML file itself.
 Configuration can be done in the Approvals and Checks menu on the Service Connection.
 ![ApprovalsAndChecks](./images/approvals-and-checks.png)
 
@@ -60,7 +60,7 @@ By configuring Branch Control on a Service Connection, you can control that the
 By configuring Branch Control to only allow the main branch (and potentially release branches) you can ensure a YAML Pipeline can only use the Service Connection after any changes to that pipeline have been merged into the main branch, and therefore has passed any Pull Requests checks and Code Reviews.
 As an additional check, Branch Control can verify if Branch Protections (like required Pull Requests and Code Reviews) are actually configured on the allowed branches.
 
-With Branch Control in place, in combination with Branch Protections, it is not possible anymore to run any commands against a Service Connection without having multiple persons review the commands. Therefore accidental, or malicious, mis-use of the permissions a Service Connection has is not possible anymore.
+With Branch Control in place, in combination with Branch Protections, it is not possible anymore to run any commands against a Service Connection without having multiple persons review the commands. Therefore accidental, or malicious, misuse of the permissions a Service Connection has is not possible anymore.
 
 > **Note:** When setting a wildcard for the Allowed Branches, anyone could still create a branch matching that wildcard and would be able to use the Service Connection. Using [git permissions](https://learn.microsoft.com/en-us/azure/devops/repos/git/require-branch-folders#enforce-permissions) it can be configured so only administrators are allowed to create certain branches, like release branches.*
 

docs/CI-CD/gitops/secret-management/README.md

@@ -34,7 +34,7 @@ Some of the key points of using Sealed Secrets are:
 - If the private key in the cluster is lost for some reason all secrets need to be re-encrypted followed by a new key-pair generation
 - Does not scale with multi-cluster, because every cluster will require a controller having its own key pair
 - Can only encrypt `secret` resource type
-- The Flux documentation has inconsistences in the Azure Key Vault examples
+- The Flux documentation has inconsistencies in the Azure Key Vault examples
 
 ### [Mozilla SOPS](https://github.com/mozilla/sops)
 

docs/agile-development/advanced-topics/effective-organization/scrum-of-scrums.md

@@ -4,7 +4,7 @@ Scrum of scrums is a technique used to scale Scrum to a larger group working tow
 
 ## Goals
 
-The goal of the scrum of scrums ceremony is to give sub-teams the agility they need while not loosing visibility and coordination. It also helps to ensure that the sub-teams are achieving their sprint goals, and they are going in the right direction to achieve the overall project goal.
+The goal of the scrum of scrums ceremony is to give sub-teams the agility they need while not losing visibility and coordination. It also helps to ensure that the sub-teams are achieving their sprint goals, and they are going in the right direction to achieve the overall project goal.
 
 The scrum of scrums ceremony happens every day and can be seen as a regular stand-up:
 

docs/automated-testing/ui-testing/teams-tests.md

@@ -180,13 +180,13 @@ Solution to fix it:
 
 Inspecting the app is highly valuable when writing new tests, as it enables you to identify the unique IDs of various elements displayed on the screen. This process is similar to using DevTools, which allows you to navigate through the Document Object Model (DOM) of a web page.
 
-[Appium Inspector](https://inspector.appiumpro.com/) is a very useful tool that allows you to inspect an app runing on an emulator.
+[Appium Inspector](https://inspector.appiumpro.com/) is a very useful tool that allows you to inspect an app running on an emulator.
 
 > Note: This section assumes that you have already performed the prerequisites from **How to run mobile test locally on a Windows machine using AVD?**
 
 ##### Steps
 
-1. Run the appium server with [--alow-cors flag](https://appium.readthedocs.io/en/latest/en/writing-running-appium/server-args/) by running the following command in a terminal:
+1. Run the appium server with [--allow-cors flag](https://appium.readthedocs.io/en/latest/en/writing-running-appium/server-args/) by running the following command in a terminal:
 
     ```cmd
     appium --allow-cors

docs/developer-experience/devcontainers-going-further.md

@@ -186,7 +186,7 @@ As you can see, `${localEnv:HOME}` returns the host `home` folder, and it maps i
 ```yaml
 version: '3'
 services:
-  my-worspace:
+  my-workspace:
     env_file: ../configs/.env
     build:
       context: .

docs/observability/observability-databricks.md

@@ -29,7 +29,7 @@ log are structured - Timestamp, Event Type and Details. Unfortunately, there is
 ### VM Performance Metrics (OMS)
 
 [Log Analytics Agent](https://learn.microsoft.com/en-us/azure/virtual-machines/extensions/oms-linux) provides insights into the performance counters from the Cluster VMs and helps to understand the
-Cluster Utilization patters. Leveraging Linux OMX Agent to onboard VMs into Log Analytics, helps provide insights into the VM metrics, performance, inventory and syslog metrics. It is important to
+Cluster Utilization patterns. Leveraging Linux OMX Agent to onboard VMs into Log Analytics, helps provide insights into the VM metrics, performance, inventory and syslog metrics. It is important to
 note that Linux OMS Agent is not specific to Azure Databricks.
 
 ### Application Logging