Spelling Wave 2

Author: ArieHein

docs/pipelines/create-first-pipeline.md

@@ -173,7 +173,7 @@ Learn more about [working with JavaScript](ecosystems/javascript.md) in your pip
     az pipelines create --name "First-Java.CI" --org <organization> --project <project>
     ```
 
-    Replace `<organization>` and `<project>` with naem of your Azure DevOps organization and project.
+    Replace `<organization>` and `<project>` with name of your Azure DevOps organization and project.
 
     If you don't have the **azure-devops** Azure CLI extension, you'll be prompted to install it.
 

docs/pipelines/ecosystems/kubernetes/canary-demo.md

@@ -66,7 +66,7 @@ The GitHub repository contains the following files:
     variables:
       imageName: azure-pipelines-canary-k8s # name of ACR image
       dockerRegistryServiceConnection: azure-pipelines-canary-acr # name of ACR service connection
-      imageRepository: 'azure-pipelines-canary-k8s' # name of image repostory
+      imageRepository: 'azure-pipelines-canary-k8s' # name of image repository
       containerRegistry: example.azurecr.io # name of Azure container registry
       tag: '$(Build.BuildId)'
 
@@ -483,4 +483,4 @@ Once rejected, the pipeline prevents the code deployment.
 
 ## Clean up
 
- If you're not going to continue to use this application, delete the resource group in Azure portal and the project in Azure DevOps.
+ If you're not going to continue to use this application, delete the resource group in Azure portal and the project in Azure DevOps.

docs/pipelines/release/define-multistage-release-process.md

@@ -45,7 +45,7 @@ Enabling continuous deployment trigger will instruct the pipeline to automatical
 
 1. In **Azure Pipelines**, open the **Releases** tab. Select your release pipeline, then select **Edit**.
 
-   ![edit the release pipelin](media/define-multistage-release-process/open-for-edit.png)
+   ![edit the release pipeline](media/define-multistage-release-process/open-for-edit.png)
 
 1. Select the **Continuous deployment trigger** icon in the **Artifacts** section to open the trigger panel. Make sure this is enabled so that a new release is created after every new successful build is completed.
 

docs/pipelines/release/troubleshoot-workload-identity.md

@@ -115,7 +115,7 @@ You can fix the issuer URL by editing and saving the service connection to updat
 
 The next sections identify common issues and describe causes and resolutions.
 
-<a name='i-dont-have-permissions-to-create-a-service-principal-in-the-micrososft-entra-tenant'></a>
+<a name='i-dont-have-permissions-to-create-a-service-principal-in-the-microsoft-entra-tenant'></a>
 
 ### I don't have permissions to create a service principal in the Microsoft Entra tenant
 
@@ -152,4 +152,4 @@ The following table identifies common error messages and issues that might gener
 | **Script failed with error: UnrecognizedArgumentError: unrecognized arguments: --federated-token** | You're using an AzureCLI task on an agent that has an earlier version of the Azure CLI installed. Workload identity federation requires Azure CLI 2.30 or later. |
 | **Failed to create an app in Microsoft Entra ID. Error: Insufficient privileges to complete the operation in Microsoft Graph. Ensure that the user has permissions to create a Microsoft Entra Application.** | The ability to create app registrations was [disabled](/azure/active-directory/roles/delegate-app-roles#restrict-who-can-create-applications) in the Microsoft Entra tenant. Assign the user who is creating the service connection the [Application Developer](/azure/active-directory/roles/permissions-reference#application-developer) Microsoft Entra role. Alternatively, create the service connection manually by using a managed identity. For more information, see [Workload identity with managed identity](https://aka.ms/azdo-rm-workload-identity-manual). |
 
-Is the AADSTS error you see not listed above? Check [Microsoft Entra authentication and authorization error codes](/entra/identity-platform/reference-error-codes#aadsts-error-codes).
+Is the AADSTS error you see not listed above? Check [Microsoft Entra authentication and authorization error codes](/entra/identity-platform/reference-error-codes#aadsts-error-codes).

docs/pipelines/scripts/cli/pipeline-variable-group-secret-nonsecret-variables.md

@@ -24,7 +24,7 @@ With the sample in this guide, you learn how to:
 - Execute the pipeline using the Azure DevOps CLI and monitor the run processing and output.
 
 > [!NOTE]
-> This sample demostrates the functionality of Azure DevOps CLI with variable groups. For increased security, [define variables in variables groups in the Pipelines UI](../../library/variable-groups.md) or [link a variable group to secrets in Azure Key Vault](../../library/link-variable-groups-to-key-vaults.md). 
+> This sample demonstrates the functionality of Azure DevOps CLI with variable groups. For increased security, [define variables in variables groups in the Pipelines UI](../../library/variable-groups.md) or [link a variable group to secrets in Azure Key Vault](../../library/link-variable-groups-to-key-vaults.md). 
 
 [!INCLUDE [include](~/../docs/reusable-content/azure-cli/azure-cli-prepare-your-environment.md)]
 

docs/pipelines/troubleshooting/review-logs.md

@@ -378,7 +378,7 @@ steps:
     targetType: 'inline'
     script: '$(System.DefaultWorkingDirectory)\perfview.exe /accepteula /logfile:"PerfView.log" abort'
 
-- task: PowerShell@2 # add a sleep of 5 mins, to givet time for required for traces to be complete
+- task: PowerShell@2 # add a sleep of 5 mins, to give it time for required traces to be complete
   inputs:
     targetType: 'inline'
     script: 'Start-Sleep -Seconds 300'

docs/reference/add-portfolio-backlogs.md

@@ -57,7 +57,7 @@ This article walks you through adding a portfolio backlog to a project based on
 
 You can apply the same steps if you work with a project based on the [Scrum](../boards/work-items/guidance/scrum-process.md) or [CMMI](../boards/work-items/guidance/cmmi-process.md) process. When you're done, you'll get to manage your portfolio of projects by grouping work within these four levels: User Stories (or Product backlog items or Requirements), Features, Epics, and Initiatives.   
 
-For more informaiton, see [About processes and process templates](../boards/work-items/guidance/choose-process.md). For an overview of the three process models, see [Customize your work tracking experience](customize-work.md). 
+For more information, see [About processes and process templates](../boards/work-items/guidance/choose-process.md). For an overview of the three process models, see [Customize your work tracking experience](customize-work.md). 
 
 <a id="export-files">  </a>
 

docs/reference/on-premises-xml-process-model.md

@@ -31,7 +31,7 @@ For Azure DevOps Server 2019 and later versions, you have a choice of process mo
 
 
 > [!IMPORTANT]  
-> Migration of projects or collections from Hosted XML to the inherited model is not support for Azure DevOps Server. It is only available on the Azure DevOps Sevice.
+> Migration of projects or collections from Hosted XML to the inherited model is not support for Azure DevOps Server. It is only available on the Azure DevOps Services.
 > 
 > To customize an Azure DevOps Services project, see [About process customization and inherited processes](../organizations/settings/work/inheritance-process-model.md). This article applies to on-premises deployments only.  
 

docs/report/extend-analytics/aggregated-data-analytics.md

@@ -81,7 +81,7 @@ Using the `$apply` extension, you can obtain counts, sums, and additional inform
 
 The OData aggregation extension also supports a `groupby` clause that is identical to the SQL `GROUP BY` clause. You can use this clause to quickly break down numbers in more detail.  
 
-For example, thie following clause returns a  count of work items:
+For example, the following clause returns a count of work items:
 
 > [!div class="tabbedCodeSnippets"]
 > ```OData

docs/report/extend-analytics/analytics-metadata.md

@@ -106,7 +106,7 @@ ReferenceName is another common annotation used to define the system identifier
 
 Querying an individual Entity is useful. Eventually, you'll probably want to filter or expand details of another Entity. To do so, you need to understand how to use the [Navigational Properties](data-model-analytics-service.md) of the Entity model. 
 
-A `NavigationaProperty` with a collection type represents a many-to-many relationship in the model.
+A `NavigationProperty` with a collection type represents a many-to-many relationship in the model.
 
 > [!div class="tabbedCodeSnippets"]
 > ```XML

docs/report/sql-reports/migration-guide.md

@@ -42,7 +42,7 @@ As you migrate from using SQL Server Reporting Services to Analytics, note the f
 Several new features have been introduced to support data insights that weren't available with SQL Server Reporting services.   
 
 - **Dashboard widgets**: Many widgets have been added to support status and trend views, including ones based on Analytics data. For an overview, see the [widget catalog](../dashboards/widget-catalog.md).  
-- **Built-in Analytics reports**: Severa in-context reports have been added to support Azure Boards, Pipelines, and Test Plans. These reports display Analytics data as described in [About dashboards, charts, reports, & widgets](../dashboards/overview.md).
+- **Built-in Analytics reports**: Several in-context reports have been added to support Azure Boards, Pipelines, and Test Plans. These reports display Analytics data as described in [About dashboards, charts, reports, & widgets](../dashboards/overview.md).
 - **Rollup**: Rollup columns allow you to view progress bars or totals of numeric fields for descendant items within a work item hierarchy. You can add them to any backlog view. For more information, see [Display rollup progress or totals](../../boards/backlogs/display-rollup.md). 
 - **Query-based charts grouped by tags**: You can now generate query charts and add them to dashboards based on grouping by tags. 
 - **Traceability**: Increased support for tracking work from requirements to deployment. End-to-end traceability is supported by linking various objects such as work items, branches, commits, pull requests, builds, and releases. Built-in reports based on the Analytics service support the ability to monitor traceability in real time. For more information, see [End-to-end traceability](../../cross-service/end-to-end-traceability.md).

docs/repos/git/branch-permissions.md

@@ -65,7 +65,7 @@ The following permissions are automatically assigned to branch creators: **Contr
 
 
 > [!NOTE]
-> The **Exempt from policy enforcement** permission was removed for Azure DevOps Server 2019 and later versions. It's functionalilty is now supported with the following two permissions: 
+> The **Exempt from policy enforcement** permission was removed for Azure DevOps Server 2019 and later versions. It's functionality is now supported with the following two permissions: 
 >
 >- **Bypass policies when completing pull requests**
 >- **Bypass policies when pushing**

docs/repos/git/create-new-repo.md

@@ -66,7 +66,7 @@ To work with a Git repo, you clone it to your computer. Cloning a repo creates a
 
 2. Select **Clone** in the upper-right corner of the **Files** window and copy the clone URL.
 
-   ![Clone respository dialog.](./media/clone-repo/clone-repo.png)
+   ![Clone repository dialog.](./media/clone-repo/clone-repo.png)
 
 3. Open the Git command window (Git Bash on Git for Windows). Then, browse to the folder where you want the code from the repo stored on your computer. Run `git clone` followed by the path copied from the **Clone URL** in the previous section, as shown in the following example.
 

docs/repos/security/github-advanced-security-dependency-scanning.md

@@ -479,7 +479,7 @@ If alerts are created for new dependency changes in a pull request, the alert wi
 
 You can see the affected package manifest, see a summary of the finding, and resolve the annotation in the Overview section.
 
-[![Screenshot of active depenendency pull request annotation.](./media/pull-request-annotation-dependency-scanning.png)](./media/pull-request-annotation-dependency-scanning.png#lightbox)
+[![Screenshot of active dependency pull request annotation.](./media/pull-request-annotation-dependency-scanning.png)](./media/pull-request-annotation-dependency-scanning.png#lightbox)
 
 To dismiss pull request alerts, you must navigate to the alert detail view to close both the alert and resolve the annotation. Otherwise, simply changing the comment status (1) resolves the annotation but does not close or fix the underlying alert. 
 

docs/test/create-test-cases.md

@@ -259,7 +259,7 @@ You can assign an individual test case to a tester.
 2. Add or remove testers from the list. After you select the testers, tick the **Send email**
    checkbox and edit the message as required so they know that tests are ready for them to run.
 
-   ![Screenshot shwoing send emails to testers.](media/create-test-cases/AssignMultipleTestersEmail.png)
+   ![Screenshot showing send emails to testers.](media/create-test-cases/AssignMultipleTestersEmail.png)
 
    The email contains a link that testers can open to see the list of assigned tests.
    Testers need [Basic access](../organizations/security/access-levels.md)