Spelling Fixes

ArieHein · ArieHein · commit 737329be77f9 · 2024-12-15T00:22:46.000+01:00
diff --git a/includes/business-continuity-center-view-fired-alerts.md b/includes/business-continuity-center-view-fired-alerts.md
@@ -12,7 +12,7 @@ To monitor the alerts, follow these steps:
 
    The count of all alert rules appears that have at least one or more fired alerts in the selected time range.
 
-   :::image type="content" source="./media/business-continuity-center-view-fired-alerts/view-triggered-alerts-in-selected-time-range.png" alt-text="Screemshot shows the triggered alerts in a selected time range." lightbox="./media/business-continuity-center-view-fired-alerts/view-triggered-alerts-in-selected-time-range.png":::
+   :::image type="content" source="./media/business-continuity-center-view-fired-alerts/view-triggered-alerts-in-selected-time-range.png" alt-text="Screenshot shows the triggered alerts in a selected time range." lightbox="./media/business-continuity-center-view-fired-alerts/view-triggered-alerts-in-selected-time-range.png":::
 
 2. On **Alerts**, filter the list by *severity of alert*, *category of alert*, *time range* (up to last 15 days), and other parameters.
 
diff --git a/includes/cdn-classic-retirement.md b/includes/cdn-classic-retirement.md
@@ -13,4 +13,4 @@
 > [!IMPORTANT]
 > Azure CDN Standard from Microsoft (classic) will be retired on **September 30, 2027**. To avoid any service disruption, it is important that you [**migrate your Azure CDN Standard from Microsoft (classic) profiles**](../articles/cdn/migrate-tier.md) to Azure Front Door Standard or Premium tier by September 30, 2027. For more information, see [**Azure CDN Standard from Microsoft (classic) retirement**](https://azure.microsoft.com/updates/v2/Azure-CDN-Standard-from-Microsoft-classic-will-be-retired-on-30-September-2027).
 >
-> Azure CDN from Edgio will be retired on **Januray 15, 2025**. You must [migrate your workload](../articles/frontdoor/migrate-cdn-to-front-door.md) to Azure Front Door before this date to avoid service disruption. For more information, see [**Azure CDN from Edgio retirement FAQ**](../articles/cdn/edgio-retirement-faq.md).
+> Azure CDN from Edgio will be retired on **January 15, 2025**. You must [migrate your workload](../articles/frontdoor/migrate-cdn-to-front-door.md) to Azure Front Door before this date to avoid service disruption. For more information, see [**Azure CDN from Edgio retirement FAQ**](../articles/cdn/edgio-retirement-faq.md).
diff --git a/includes/container-apps/sessions-tutorial-deploy-autogen.md b/includes/container-apps/sessions-tutorial-deploy-autogen.md
@@ -27,11 +27,11 @@ You then need to configure managed identity for the app and assign it the proper
         --resource-group $RESOURCE_GROUP_NAME \
         --location $SESSION_POOL_LOCATION \
         --environment $ENVIRONMENT_NAME \
-        --env-vars 'OAI_CONFIG_LIST=[{"model": "gpt-4", "api_key": "<AZURE_OPENAI_KEY>", "api_type": "azure", "base_url": "<AZURE_OPENAI_ENDPOINT>", "api_version": "2023-12-01-preview"}]' 'POOL_MANAGEMENT_ENDPOINT=<SESSION_POOL_MANAGMENT_ENDPOINT>' \
+        --env-vars 'OAI_CONFIG_LIST=[{"model": "gpt-4", "api_key": "<AZURE_OPENAI_KEY>", "api_type": "azure", "base_url": "<AZURE_OPENAI_ENDPOINT>", "api_version": "2023-12-01-preview"}]' 'POOL_MANAGEMENT_ENDPOINT=<SESSION_POOL_MANAGEMENT_ENDPOINT>' \
         --source .
     ```
 
-    Replace `<AZURE_OPENAI_ENDPOINT>` with the Azure OpenAI account endpoint, `<AZURE_OPENAI_KEY>` with the Azure OpenAI key, and `<SESSION_POOL_MANAGMENT_ENDPOINT>` with the session pool management endpoint.
+    Replace `<AZURE_OPENAI_ENDPOINT>` with the Azure OpenAI account endpoint, `<AZURE_OPENAI_KEY>` with the Azure OpenAI key, and `<SESSION_POOL_MANAGEMENT_ENDPOINT>` with the session pool management endpoint.
 
 1. Enable the system-assigned managed identity for the app:
 
diff --git a/includes/container-apps/sessions-tutorial-deploy.md b/includes/container-apps/sessions-tutorial-deploy.md
@@ -28,11 +28,11 @@ You then need to configure managed identity for the app and assign it the proper
         --resource-group $RESOURCE_GROUP_NAME \
         --location $SESSION_POOL_LOCATION \
         --environment $ENVIRONMENT_NAME \
-        --env-vars "AZURE_OPENAI_ENDPOINT=<OPEN_AI_ENDPOINT>" "POOL_MANAGEMENT_ENDPOINT=<SESSION_POOL_MANAGMENT_ENDPOINT>" \
+        --env-vars "AZURE_OPENAI_ENDPOINT=<OPEN_AI_ENDPOINT>" "POOL_MANAGEMENT_ENDPOINT=<SESSION_POOL_MANAGEMENT_ENDPOINT>" \
         --source .
     ```
 
-    Replace `<OPEN_AI_ENDPOINT>` with the Azure OpenAI account endpoint and `<SESSION_POOL_MANAGMENT_ENDPOINT>` with the session pool management endpoint.
+    Replace `<OPEN_AI_ENDPOINT>` with the Azure OpenAI account endpoint and `<SESSION_POOL_MANAGEMENT_ENDPOINT>` with the session pool management endpoint.
 
 1. Enable the system-assigned managed identity for the app:
 
diff --git a/includes/cost-management-billing-transform-data-before-using-large-usage-files.md b/includes/cost-management-billing-transform-data-before-using-large-usage-files.md
@@ -7,7 +7,7 @@ ms.subservice: billing
 ms.topic: include
 ms.date: 10/09/2020
 ms.author: banders
-ms.reviwer: 
+ms.reviewer: 
 ms.custom: include file
 ---
 
diff --git a/includes/data-box-shares.md b/includes/data-box-shares.md
@@ -19,7 +19,7 @@ The following table shows the UNC path to the shares on your Data Box and Azure
 | Blobs and Files | Paths and URLs |
 | --------------- | -------------- |
 | Azure Block blobs | <li>UNC path to shares: `\\<DeviceIPAddress>\<StorageAccountName_BlockBlob>\<ContainerName>\files\a.txt`</li><li>Azure Storage URL: `https://<StorageAccountName>.blob.core.windows.net/<ContainerName>/files/a.txt`</li> |  
-| Azure Page blobs  | <li>UNC path to shares: `\\<DeviceIPAddres>\<StorageAccountName_PageBlob>\<ContainerName>\files\a.txt`</li><li>Azure Storage URL: `https://<StorageAccountName>.blob.core.windows.net/<ContainerName>/files/a.txt`</li>   |  
-| Azure Files       |<li>UNC path to shares: `\\<DeviceIPAddres>\<StorageAccountName_AzFile>\<ShareName>\files\a.txt`</li><li>Azure Storage URL: `https://<StorageAccountName>.file.core.windows.net/<ShareName>/files/a.txt`</li>        |      
+| Azure Page blobs  | <li>UNC path to shares: `\\<DeviceIPAddress>\<StorageAccountName_PageBlob>\<ContainerName>\files\a.txt`</li><li>Azure Storage URL: `https://<StorageAccountName>.blob.core.windows.net/<ContainerName>/files/a.txt`</li>   |  
+| Azure Files       |<li>UNC path to shares: `\\<DeviceIPAddress>\<StorageAccountName_AzFile>\<ShareName>\files\a.txt`</li><li>Azure Storage URL: `https://<StorageAccountName>.file.core.windows.net/<ShareName>/files/a.txt`</li>        |      
 
 
diff --git a/includes/functions-create-container-prereq.md b/includes/functions-create-container-prereq.md
@@ -10,4 +10,4 @@ ms.author: glenga
 
 If you haven't already done so, complete the previous quickstart article [Create a function that runs in custom container](../articles/azure-functions/functions-create-function-linux-custom-image.md) to create and publish a custom container with your first function app. 
 
-This article creates a container image named `azurefunctionsimage` in either Azure Container Registry or Docker Hub. If you chose a diffent name for your image, you'll need to modify the examples in this article.
+This article creates a container image named `azurefunctionsimage` in either Azure Container Registry or Docker Hub. If you chose a different name for your image, you'll need to modify the examples in this article.
diff --git a/includes/functions-monitor-metrics-consumption.md b/includes/functions-monitor-metrics-consumption.md
@@ -32,7 +32,7 @@ This chart shows a total of 1.11 billion `Function Execution Units` consumed in
 
 The [Azure CLI](/cli/azure/) has commands for retrieving metrics. You can use the CLI from a local command environment or directly from the portal using [Azure Cloud Shell](../articles/cloud-shell/overview.md). For example, the following [az monitor metrics list](/cli/azure/monitor/metrics#az-monitor-metrics-list) command returns hourly data over same time period used before.
 
-Make sure to replace `<AZURE_SUBSCRIPTON_ID>` with your Azure subscription ID running the command.
+Make sure to replace `<AZURE_SUBSCRIPTION_ID>` with your Azure subscription ID running the command.
 
 ```azurecli-interactive
 az monitor metrics list --resource /subscriptions/<AZURE_SUBSCRIPTION_ID>/resourceGroups/metrics-testing-consumption/providers/Microsoft.Web/sites/metrics-testing-consumption --metric FunctionExecutionUnits,FunctionExecutionCount --aggregation Total --interval PT1H --start-time 2019-09-11T21:46:00Z --end-time 2019-09-11T23:18:00Z
@@ -123,7 +123,7 @@ This particular response shows that from `2019-09-11T21:46` to `2019-09-11T23:18
 
 The [Azure PowerShell](/powershell/azure/) has commands for retrieving metrics. You can use the Azure PowerShell from a local command environment or directly from the portal using [Azure Cloud Shell](../articles/cloud-shell/overview.md). For example, the following [Get-AzMetric](/powershell/module/az.monitor/get-azmetric) command returns hourly data over same time period used before.
 
-Make sure to replace `<AZURE_SUBSCRIPTON_ID>` with your Azure subscription ID running the command.
+Make sure to replace `<AZURE_SUBSCRIPTION_ID>` with your Azure subscription ID running the command.
 
 ```azurepowershell-interactive
 Get-AzMetric -ResourceId /subscriptions/<AZURE_SUBSCRIPTION_ID>/resourceGroups/metrics-testing-consumption/providers/Microsoft.Web/sites/metrics-testing-consumption -MetricName  FunctionExecutionUnits,FunctionExecutionCount -AggregationType Total -TimeGrain 01:00:00 -StartTime 2019-09-11T21:46:00Z -EndTime 2019-09-11T23:18:00Z
diff --git a/includes/iot-central-data-export-setup.md b/includes/iot-central-data-export-setup.md
@@ -49,7 +49,7 @@ Now that you have a destination to export your data to, set up data export in yo
     |Audit logs|N/A|
 
 1. Optionally, enrich exported messages with extra key-value pair metadata. The following enrichments are available for the telemetry, property changes, device connectivity, and device lifecycle data export types:
-<a name="DataExportEnrichmnents"></a>
+<a name="DataExportEnrichments"></a>
     - **Custom string**: Adds a custom static string to each message. Enter any key, and enter any string value.
     - **Property**, which adds to each message:
        - Device metadata such as device name, device template name, enabled, organizations, provisioned, and simulated.
diff --git a/includes/iot-hub-howto-cloud-to-device-messaging-dotnet.md b/includes/iot-hub-howto-cloud-to-device-messaging-dotnet.md
@@ -248,7 +248,7 @@ var feedbackReceiver = serviceClient.GetFeedbackReceiver();
 // Define the cancellation token.
 CancellationTokenSource source = new CancellationTokenSource();
 CancellationToken token = source.Token;
-// Call ReceiveAsync, passing the token. Wait for the timout period.
+// Call ReceiveAsync, passing the token. Wait for the timeout period.
 var feedbackBatch = await feedbackReceiver.ReceiveAsync(token);
 if (feedbackBatch == null) continue;
 ```
diff --git a/includes/iot-pnp-device-devguide-csharp.md b/includes/iot-pnp-device-devguide-csharp.md
@@ -271,7 +271,7 @@ A default component receives the command name as it was invoked by the service.
 A nested component receives the command name prefixed with the component name and the `*` separator.
 
 ```csharp
-await client.SetMethodHandlerAsync("themostat*reboot", (MethodRequest req, object ctx) =>
+await client.SetMethodHandlerAsync("thermostat*reboot", (MethodRequest req, object ctx) =>
 {
   Console.WriteLine("REBOOT");
   return Task.FromResult(new MethodResponse(200));
@@ -306,7 +306,7 @@ The following example shows how to implement a command with complex types define
     }
   },
   "response": {
-    "name": "startReponse",
+    "name": "startResponse",
     "schema": {
       "@type": "Object",
       "fields": [
diff --git a/includes/iot-pnp-multiple-components-csharp.md b/includes/iot-pnp-multiple-components-csharp.md
@@ -116,7 +116,7 @@ await SendTemperatureAsync(Thermostat1, cancellationToken);
 await SendTemperatureAsync(Thermostat2, cancellationToken);
 ```
 
-The `SendTemperatureTelemetryAsync` method uses the `PnpHhelper` class to create messages for each component:
+The `SendTemperatureTelemetryAsync` method uses the `PnpHelper` class to create messages for each component:
 
 ```csharp
 using Message msg = PnpHelper.CreateIothubMessageUtf8(telemetryName, JsonConvert.SerializeObject(currentTemperature), componentName);
diff --git a/includes/iot-pnp-multiple-components-java.md b/includes/iot-pnp-multiple-components-java.md
@@ -128,7 +128,7 @@ sendTemperatureReading(THERMOSTAT_1);
 sendTemperatureReading(THERMOSTAT_2);
 ```
 
-The `sendTemperatureReading` method uses the `PnpHhelper` class to create messages for each component:
+The `sendTemperatureReading` method uses the `PnpHelper` class to create messages for each component:
 
 ```java
 Message message = PnpHelper.createIotHubMessageUtf8(telemetryName, currentTemperature, componentName);
diff --git a/includes/load-balancer-cross-subscription-add-nic.md b/includes/load-balancer-cross-subscription-add-nic.md
@@ -34,7 +34,7 @@ $IP1 = @{
 $IP1Config = New-AzNetworkInterfaceIpConfig @IP1 -Primary
 $nic = @{
     Name = 'MyNic'
-    ResourceGroupName = '<Resoure Group Subscription A>'
+    ResourceGroupName = '<Resource Group Subscription A>'
     Location = 'eastus'
     IpConfiguration = $IP1Config
 }
diff --git a/includes/notification-hubs-enable-firebase-cloud-messaging-xamarin.md b/includes/notification-hubs-enable-firebase-cloud-messaging-xamarin.md
@@ -16,7 +16,7 @@
     ![Add Firebase to your Android app](./media/notification-hubs-enable-firebase-cloud-messaging/notification-hubs-add-firebase-to-android-app.png)
 
 3. On the **Add Firebase to your Android app** page, take the following steps: 
-    1. For the **Android package name**, enter a name for your package. For example: `tutorials.tutoria1.xamarinfcmapp`. 
+    1. For the **Android package name**, enter a name for your package. For example: `tutorials.tutorial1.xamarinfcmapp`. 
 
         ![Specify the package name](./media/notification-hubs-enable-firebase-cloud-messaging/specify-package-name-fcm-settings.png)
     2. Select **Register app**.  
diff --git a/includes/storage-files-migration-robocopy-optimize.md b/includes/storage-files-migration-robocopy-optimize.md
@@ -24,7 +24,7 @@ Speed and success rate of a given RoboCopy run will depend on several factors:
 In this category, you need to consider abilities of the **source storage**, the **target storage**, and the **network** connecting them. The maximum possible throughput is determined by the slowest of these three components. Make sure your network infrastructure is configured to support optimal transfer speeds to its best abilities.
 
 > [!CAUTION]
-> While copying as fast as possible is often most desireable, consider the utilization of your local network and NAS appliance for other, often business-critical tasks.
+> While copying as fast as possible is often most desirable, consider the utilization of your local network and NAS appliance for other, often business-critical tasks.
 
 Copying as fast as possible might not be desirable when there's a risk that the migration could monopolize available resources.
 
diff --git a/includes/storsimple-upgrade-sharepoint-adapter.md b/includes/storsimple-upgrade-sharepoint-adapter.md
@@ -6,7 +6,7 @@ ms.date: 10/26/2018
 ms.author: alkohli
 ---
 
-### Upgrade SharePoint 2010 to SharePoint 2013 and then install the StorSomple Adapter for SharePoint
+### Upgrade SharePoint 2010 to SharePoint 2013 and then install the StorSimple Adapter for SharePoint
 > [!IMPORTANT]
 > Any files that were previously moved to external storage via RBS will not be available until the upgrade is finished and the RBS feature is enabled again. To limit user impact, perform any upgrade or reinstallation during a planned maintenance window.
 > 
diff --git a/includes/vpn-gateway-custom-audience.md b/includes/vpn-gateway-custom-audience.md
@@ -23,7 +23,7 @@ There are a couple of different ways to get to the **App registrations** page. O
 1. Leave **Redirect URI (optional)** alone for now as you configure a redirect URI in the next section.
 1. Select **Register** to complete the initial app registration.
 
-When registration finishes, the Microsoft Entra admin center displays the app registration's **Overview** pane. You see the **Application (client) ID**. Also called the *client ID*, this value uniquely identifies your application in the Microsoft identity platform. This is the custom audience value that you use when you configure your P2S gateway. Even though this value is present, you still need to complete the next sections to associate the Micrsoft-registered application to your application ID.
+When registration finishes, the Microsoft Entra admin center displays the app registration's **Overview** pane. You see the **Application (client) ID**. Also called the *client ID*, this value uniquely identifies your application in the Microsoft identity platform. This is the custom audience value that you use when you configure your P2S gateway. Even though this value is present, you still need to complete the next sections to associate the Microsoft-registered application to your application ID.
 
 ## Expose an API and add a scope
 
diff --git a/includes/vpn-gateway-vwan-azure-ad-tenant.md b/includes/vpn-gateway-vwan-azure-ad-tenant.md
@@ -36,7 +36,7 @@
     ```
 
    > [!NOTE]
-   > If you're using a Cloud Applicaion Administrator account that is not native to the Microsoft Entra tenant to provide consent, replace "common" with the Microsoft Entra tenant ID in the URL. You may also have to replace "common" with your tenant ID in certain other cases as well. For help with finding your tenant ID, see [How to find your Microsoft Entra tenant ID](/azure/active-directory-b2c/tenant-management-read-tenant-name).
+   > If you're using a Cloud Application Administrator account that is not native to the Microsoft Entra tenant to provide consent, replace "common" with the Microsoft Entra tenant ID in the URL. You may also have to replace "common" with your tenant ID in certain other cases as well. For help with finding your tenant ID, see [How to find your Microsoft Entra tenant ID](/azure/active-directory-b2c/tenant-management-read-tenant-name).
    >
 
 1. Select the account that has the **Cloud Application Administrator** role if prompted.
diff --git a/includes/vpn-gateway-vwan-vpn-profile-download.md b/includes/vpn-gateway-vwan-vpn-profile-download.md
@@ -30,7 +30,7 @@ In the **AzureVPN** folder, navigate to the ***azurevpnconfig.xml*** file and op
 ```
 <audience>          </audience>
 <issuer>            </issuer>
-<tennant>           </tennant>
+<tenant>            </tenant>
 <fqdn>              </fqdn>
 <serversecret>      </serversecret>
 ```

Original file line number	Diff line number	Diff line change
`@@ -13,4 +13,4 @@`
`13`	`13`	`> [!IMPORTANT]`
`14`	`14`	> Azure CDN Standard from Microsoft (classic) will be retired on September 30, 2027. To avoid any service disruption, it is important that you [migrate your Azure CDN Standard from Microsoft (classic) profiles](../articles/cdn/migrate-tier.md) to Azure Front Door Standard or Premium tier by September 30, 2027. For more information, see [Azure CDN Standard from Microsoft (classic) retirement](https://azure.microsoft.com/updates/v2/Azure-CDN-Standard-from-Microsoft-classic-will-be-retired-on-30-September-2027).
`15`	`15`	`>`
`16`		`-> Azure CDN from Edgio will be retired on Januray 15, 2025. You must [migrate your workload](../articles/frontdoor/migrate-cdn-to-front-door.md) to Azure Front Door before this date to avoid service disruption. For more information, see [Azure CDN from Edgio retirement FAQ](../articles/cdn/edgio-retirement-faq.md).`
	`16`	`+> Azure CDN from Edgio will be retired on January 15, 2025. You must [migrate your workload](../articles/frontdoor/migrate-cdn-to-front-door.md) to Azure Front Door before this date to avoid service disruption. For more information, see [Azure CDN from Edgio retirement FAQ](../articles/cdn/edgio-retirement-faq.md).`
Original file line number	Diff line number	Diff line change
`@@ -10,4 +10,4 @@ ms.author: glenga`
`10`	`10`
`11`	`11`	`If you haven't already done so, complete the previous quickstart article [Create a function that runs in custom container](../articles/azure-functions/functions-create-function-linux-custom-image.md) to create and publish a custom container with your first function app.`
`12`	`12`
`13`		-This article creates a container image named `azurefunctionsimage` in either Azure Container Registry or Docker Hub. If you chose a diffent name for your image, you'll need to modify the examples in this article.
	`13`	+This article creates a container image named `azurefunctionsimage` in either Azure Container Registry or Docker Hub. If you chose a different name for your image, you'll need to modify the examples in this article.