Merge pull request #125091 from ArieHein/Spelling-Wave-19

Spelling Fixes

Author: v-dirichards

articles/deployment-environments/concept-azure-developer-cli-with-deployment-environments.md

@@ -17,7 +17,7 @@ In this article, you learn about Azure Developer CLI (`azd`) and how it works wi
 
 `azd` is an open-source command-line tool that provides developer-friendly commands that map to key stages in your workflow. You can install `azd` locally on your machine or use it in other environments.
 
-With ADE, you can create environments from an environment definition in a catalog attached to your dev center, or by using the [ADE extensibilty model to execute deployments](how-to-configure-extensibility-model-custom-image.md). By adding `azd`, you can streamline the process of provisioning infrastructure and deploying code to the cloud.
+With ADE, you can create environments from an environment definition in a catalog attached to your dev center, or by using the [ADE extensibility model to execute deployments](how-to-configure-extensibility-model-custom-image.md). By adding `azd`, you can streamline the process of provisioning infrastructure and deploying code to the cloud.
 
 ## How does `azd` work with ADE?
 

articles/deployment-environments/quickstart-create-and-configure-devcenter.md

@@ -176,7 +176,7 @@ To configure a project, add a [project environment type](how-to-configure-projec
 
 
 > [!NOTE]
-> At least one identity (system-assigned or user-assigned) must be enabled for deployment identity. The identity is used to perform the environment deployment on behalf of the developer. Additionally, the identity attached to the dev center should be [assigned the Contributor and the User Access Admistrator roles](how-to-configure-managed-identity.md) for access to the deployment subscription for each environment type.
+> At least one identity (system-assigned or user-assigned) must be enabled for deployment identity. The identity is used to perform the environment deployment on behalf of the developer. Additionally, the identity attached to the dev center should be [assigned the Contributor and the User Access Administrator roles](how-to-configure-managed-identity.md) for access to the deployment subscription for each environment type.
 
 ## Give access to the development team
 

articles/dev-box/quickstart-team-customizations.md

@@ -146,7 +146,7 @@ To create a dev box pool that's associated with a project:
    | **Time zone** | Select the time zone for the stop time. |
    | **Licensing** | Select this checkbox to confirm that your organization has Azure Hybrid Benefit licenses that you want to apply to the dev boxes in this pool. |
 
-   :::image type="content" source="media/quickstart-team-customizations/create-pool-basics.png" alt-text="Screenshot of the pane for entering basic information about a new a dev box pool, including fields for name and definition. The image definition MyImageDefintion.yaml is highlighted.":::
+   :::image type="content" source="media/quickstart-team-customizations/create-pool-basics.png" alt-text="Screenshot of the pane for entering basic information about a new a dev box pool, including fields for name and definition. The image definition MyImageDefinition.yaml is highlighted.":::
 
 1. Select **Create**.
 

articles/devtest-labs/create-environment-service-fabric-cluster.md

@@ -23,7 +23,7 @@ Service Fabric clusters are created using environments in DevTest Labs. Each env
 2. Confirm that the Service Fabric provider is registered for your subscription by following these steps:
     1. Select **Subscriptions** on the left navigational menu, and select your **Subscription**
     2. On the **Subscription** page, select **Resource providers** in the **Settings** section on the left menu. 
-    3. If **Microsoft.ServiecFabric** isn't registered, select **Register**. 
+    3. If **Microsoft.ServiceFabric** isn't registered, select **Register**. 
 3. On the **DevTest Lab** page for your lab, select **+ Add** on the toolbar. 
 
     ![Screenshot that shows the Add button on the toolbar.](./media/create-environment-service-fabric-cluster/add-button.png)

articles/digital-twins/how-to-move-regions.md

@@ -148,4 +148,4 @@ To delete the instance by using the Azure portal, [open the portal](https://port
 
 Select the **Delete** button, and follow the prompts to finish the deletion.
 
-:::image type="content" source="media/how-to-move-regions/delete-instance.png" alt-text="Sscreenshot of the Azure Digital Twins instance details in the Azure portal, on the Overview tab. The Delete button is highlighted.":::
+:::image type="content" source="media/how-to-move-regions/delete-instance.png" alt-text="Screenshot of the Azure Digital Twins instance details in the Azure portal, on the Overview tab. The Delete button is highlighted.":::

articles/dns/dns-private-resolver-get-started-template.md

@@ -65,7 +65,7 @@ templateUri="https://raw.githubusercontent.com/Azure/azure-quickstart-templates/
 
 az group create \
 --name $resourceGroupName \
---locataion $location
+--location $location
 
 az deployment group create \
 --resource-group $resourceGroupName \

articles/dns/dns-sdk.md

@@ -73,7 +73,7 @@ dnsClient.SubscriptionId = subscriptionId;
 
 To create a DNS zone, you first need to create a "Zone" object containing the DNS zone parameters. Since DNS zones aren't linked to a specific region, the location is set to 'global'. In this example, an [Azure Resource Manager 'tag'](https://azure.microsoft.com/updates/organize-your-azure-resources-with-tags/) is also added to the zone.
 
-To create or update the zone in Azure DNS, the zone object containing the zone parameters is passed to the `DnsManagementClient.Zones.CreateOrUpdateAsyc` method.
+To create or update the zone in Azure DNS, the zone object containing the zone parameters is passed to the `DnsManagementClient.Zones.CreateOrUpdateAsync` method.
 
 > [!NOTE]
 > DnsManagementClient supports three modes of operation: synchronous ('CreateOrUpdate'), asynchronous ('CreateOrUpdateAsync'), or asynchronous with access to the HTTP response ('CreateOrUpdateWithHttpMessagesAsync').  You can choose any of these modes, depending on your application needs.

articles/dns/private-dns-import-export-portal.md

@@ -103,7 +103,7 @@ The following notes provide more details about the zone import process.
 6. Select **Review + Create** and then select **Create**.
 7. When deployment is complete, select **Go to resource** and then select **Recordsets**. An SOA record compatible with Azure Private DNS is automatically added to the zone. See the following example:
 
-    [ ![creenshot showing the private.contoso.com zone record sets.](./media/private-dns-import-export-portal/recordsets.png) ](./media/private-dns-import-export-portal/recordsets.png#lightbox)
+    [ ![Screenshot showing the private.contoso.com zone record sets.](./media/private-dns-import-export-portal/recordsets.png) ](./media/private-dns-import-export-portal/recordsets.png#lightbox)
 
 ## Export a zone file
 

articles/dns/tutorial-alias-rr.md

@@ -59,7 +59,7 @@ Create an alias record that points to a resource record in the zone.
 1. Select the **server** record for the **Zone record set**.
 1. Select **OK**.
 
-    :::image type="content" source="./media/tutorial-alias-rr/add-alias-record-set-inline.png" alt-text="Screentshot of adding the alias record set in the Add record set page." lightbox="./media/tutorial-alias-rr/add-alias-record-set-expanded.png":::
+    :::image type="content" source="./media/tutorial-alias-rr/add-alias-record-set-inline.png" alt-text="Screenshot of adding the alias record set in the Add record set page." lightbox="./media/tutorial-alias-rr/add-alias-record-set-expanded.png":::
 
 ## Test the alias record
 

articles/energy-data-services/troubleshoot-manifest-ingestion.md

@@ -25,7 +25,7 @@ One single manifest file is used to trigger the manifest ingestion workflow.
 |`update_status_running_task` | Calls the workflow service and marks the status of the DAG as `running` in the database.        |
 |`check_payload_type` | Validates whether the type of ingestion is batch or single manifest.|
 |`validate_manifest_schema_task` | Ensures that all the schema types mentioned in the manifest are present and there's referential schema integrity. All invalid values are evicted from the manifest. |
-|`provide_manifest_intergrity_task` | Validates references inside the OSDU® R3 manifest and removes invalid entities. This operator is responsible for parent/child validation. All orphan-like entities are logged and excluded from the validated manifest. Any external referenced records are searched. If none are found, the manifest entity is dropped. All surrogate key references are also resolved. |
+|`provide_manifest_integrity_task` | Validates references inside the OSDU® R3 manifest and removes invalid entities. This operator is responsible for parent/child validation. All orphan-like entities are logged and excluded from the validated manifest. Any external referenced records are searched. If none are found, the manifest entity is dropped. All surrogate key references are also resolved. |
 |`process_single_manifest_file_task` | Performs ingestion of the final manifest entities obtained from the previous step. Data records are ingested via the storage service. |
 |`update_status_finished_task` | Calls the workflow service and marks the status of the DAG as `finished` or `failed` in the database. |
 
@@ -38,7 +38,7 @@ Multiple manifest files are part of the same workflow service request. The manif
 |`update_status_running_task` | Calls the workflow service and marks the status of the DAG as `running` in the database.        |
 |`check_payload_type` | Validates whether the type of ingestion is batch or single manifest.|
 |`batch_upload` | Divides the list of manifests into three batches to be processed in parallel. (No task logs are emitted.) |
-|`process_manifest_task_(1 / 2 / 3)` | Divides the list of manifests into groups of three and processes them. All the steps performed in `validate_manifest_schema_task`, `provide_manifest_intergrity_task`, and `process_single_manifest_file_task` are condensed and performed sequentially in these tasks. |
+|`process_manifest_task_(1 / 2 / 3)` | Divides the list of manifests into groups of three and processes them. All the steps performed in `validate_manifest_schema_task`, `provide_manifest_integrity_task`, and `process_single_manifest_file_task` are condensed and performed sequentially in these tasks. |
 |`update_status_finished_task` | Calls the workflow service and marks the status of the DAG as `finished` or `failed` in the database. |
 
 Based on the payload type (single or batch), the `check_payload_type` task chooses the appropriate branch and skips the tasks in the other branch.