Merge pull request #125174 from ArieHein/Spelling-Wave-44

Jak-MS · web-flow · commit 927a3649a237 · 2024-12-16T15:49:46.000-06:00
Spelling Fixes
diff --git a/articles/time-series-insights/how-to-tsi-gen2-migration.md b/articles/time-series-insights/how-to-tsi-gen2-migration.md
@@ -182,7 +182,7 @@ events
 | where timestamp >= datetime(2021-11-01T00:00:0.0000000Z) and timestamp < datetime(2021-11-05T00:00:00.000000Z)
 | where deviceId_string== "deviceId1" and siteId_string == "siteId1" and dataId_string == "dataId1"
 | take 10000
-| project timestamp, sensorStringValue= ['sensors.value_string'], sensorBoolValue= ['sensors.value_bool'], sensorDoublelValue= ['sensors.value_double']
+| project timestamp, sensorStringValue= ['sensors.value_string'], sensorBoolValue= ['sensors.value_bool'], sensorDoubleValue= ['sensors.value_double']
 ```
 
 ###	AggregateSeries  
diff --git a/articles/trusted-signing/concept-trusted-signing-resources-roles.md b/articles/trusted-signing/concept-trusted-signing-resources-roles.md
@@ -44,7 +44,7 @@ Identity validations are all about establishing the identity on the certificates
 
 - **Public Trust** means that all identity values must be validated in accordance to the [Microsoft PKI Services Third-Party Certification Practice Statement (CPS)](https://www.microsoft.com/pkiops/docs/repository.htm). This requirement aligns with the expectations for publicly trusted code signing certificates.
 
-- **Private Trust** is intended for situations in which there's an established trust in a private identity across one or many relying parties (consumers of signatures) or internally in app control or line-of-business (LOB) scenarios. With Private Trust identity validations, there's minimal verification of the identity attributes (for example, the `Organization Unit` value). Verification is tightly associated with the Azure Tenant of the subscriber (for example, `Costoso.onmicrosoft.com`). The values in Private Trust certificate profiles aren't validated beyond the Azure Tenant information.
+- **Private Trust** is intended for situations in which there's an established trust in a private identity across one or many relying parties (consumers of signatures) or internally in app control or line-of-business (LOB) scenarios. With Private Trust identity validations, there's minimal verification of the identity attributes (for example, the `Organization Unit` value). Verification is tightly associated with the Azure Tenant of the subscriber (for example, `Contoso.onmicrosoft.com`). The values in Private Trust certificate profiles aren't validated beyond the Azure Tenant information.
 
 For more information about Public Trust and Private Trust, see [Trusted Signing trust models](./concept-trusted-signing-trust-models.md).
 
diff --git a/articles/trusted-signing/how-to-renew-identity-validation.md b/articles/trusted-signing/how-to-renew-identity-validation.md
@@ -41,7 +41,7 @@ You can check the expiration date of your Identity Validation on the Identity Va
 You can delete an Identity Validation that is not in "In Progress" state from the Identity Validation page.
 
 >[!Note]
->Deleting an Identity Validation before stops the renewal of linked certificate profiles across all the accounts within a subscription where Identtiy Validation was done. This impacts signing. 
+>Deleting an Identity Validation before stops the renewal of linked certificate profiles across all the accounts within a subscription where Identity Validation was done. This impacts signing. 
 >Deleted identity validation requests cannot be recovered.
 
 1. Navigate to your Trusted Signing account in the [Azure portal](https://portal.azure.com/).
diff --git a/articles/trusted-signing/how-to-signing-integrations.md b/articles/trusted-signing/how-to-signing-integrations.md
@@ -40,7 +40,7 @@ To complete the steps in this article, you need:
 
 Trusted Signing Client Tools for SignTool.exe is a library plugin that requires the following components:
 
-1. Windows SDK SignTool.exe (minimum verision: 10.0.2261.755)
+1. Windows SDK SignTool.exe (minimum version: 10.0.2261.755)
 1. .NET 8 Runtime
 1. Microsoft Visual C++ Redistributable
 1. Trusted Signing Client Dlib
diff --git a/articles/trusted-signing/quickstart.md b/articles/trusted-signing/quickstart.md
@@ -208,7 +208,7 @@ The following table lists *helpful commands* to use when you create a Trusted Si
 You can complete your own identity validation by filling in the request form with the information that must be included in the certificate. Identity validation can be completed only in the Azure portal. You can't complete identity validation by using the Azure CLI.
 
 > [!NOTE]
-> You can't create an identity validation request if you aren't assigned the appropriate role. If the **New identity** button on the menu bar appears dimmed in the Azure portal, ensure that you are assigned the Trusted Signing Identity Verifier roler to proceed with identity validation.
+> You can't create an identity validation request if you aren't assigned the appropriate role. If the **New identity** button on the menu bar appears dimmed in the Azure portal, ensure that you are assigned the Trusted Signing Identity Verifier role to proceed with identity validation.
 
 # [Identity Validation - Organization](#tab/orgvalidation)
 
diff --git a/articles/update-manager/manage-pre-post-events.md b/articles/update-manager/manage-pre-post-events.md
@@ -83,7 +83,7 @@ To use application insights to monitor executions in Azure functions, refer [her
 
 ### Cancel a schedule run before it begins to run
 
-To cancel the schedule run, the cancelation API in your pre-event must get triggered at least 10 minutes before the schedule maintenance configuration start time. You must call the cancelation API in your pre-event, that is, Runbook script or Azure function code. 
+To cancel the schedule run, the cancellation API in your pre-event must get triggered at least 10 minutes before the schedule maintenance configuration start time. You must call the cancellation API in your pre-event, that is, Runbook script or Azure function code. 
 
 **To cancel the schedule maintenance run**
 
@@ -156,16 +156,16 @@ To view the history of an event created through Azure Function, follow these ste
 3. Select the **By Maintenance run ID** tab, and then select the maintenance run ID for which you want to view the status.
 4. Refer to the **Status** to view the status. If the maintenance run has been canceled, the status will be displayed as **cancelled**. Select the status to view the details.
 
-There are two types of cancelations:
+There are two types of cancellations:
 
-- **Cancelation by user**: When you invoke the cancelation API from your script or code.
-- **Cancelation by system**: When the system invokes the cancelation API due to an internal error. This is done only if the system is unable to send the pre-event to the customer's end point that is 30 minutes before the scheduled patching job. In this case, the upcoming scheduled maintenance configuration will be canceled due to the failure of running the pre-events by the system.
+- **Cancellation by user**: When you invoke the cancellation API from your script or code.
+- **Cancellation by system**: When the system invokes the cancellation API due to an internal error. This is done only if the system is unable to send the pre-event to the customer's end point that is 30 minutes before the scheduled patching job. In this case, the upcoming scheduled maintenance configuration will be canceled due to the failure of running the pre-events by the system.
 
-To confirm if the cancelation is by user or system, you can view the status of the maintenance run ID from the ARG query mentioned above in **See details**. The **error message** displays whether the schedule run has been canceled by the user or system and the **status** field confirms the status of the maintenance run.
+To confirm if the cancellation is by user or system, you can view the status of the maintenance run ID from the ARG query mentioned above in **See details**. The **error message** displays whether the schedule run has been canceled by the user or system and the **status** field confirms the status of the maintenance run.
 
- :::image type="content" source="./media/manage-pre-post-events/cancelation-api-user-inline.png" alt-text="Screenshot that shows how to view the cancelation status." lightbox="./media/manage-pre-post-events/cancelation-api-user-expanded.png":::
+ :::image type="content" source="./media/manage-pre-post-events/cancelation-api-user-inline.png" alt-text="Screenshot that shows how to view the cancellation status." lightbox="./media/manage-pre-post-events/cancelation-api-user-expanded.png":::
 
-The above image shows an example of cancelation by the user, where the error message would be **Maintenance cancelled using cancellation API at YYYY-MM-DD**. If the maintenance run is canceled by the system due to any reason, the error message in the JSON would be **Maintenance cancelled due to internal platform failure at YYYY-MM-DD**.
+The above image shows an example of cancellation by the user, where the error message would be **Maintenance cancelled using cancellation API at YYYY-MM-DD**. If the maintenance run is canceled by the system due to any reason, the error message in the JSON would be **Maintenance cancelled due to internal platform failure at YYYY-MM-DD**.
 
 
 ## Delete pre and post event
diff --git a/articles/update-manager/troubleshoot.md b/articles/update-manager/troubleshoot.md
@@ -129,7 +129,7 @@ If any of the steps are missed, please move the resource to the previous resourc
 
 #### Issue
 
-You want to ensure that the Windows Update client won't install pacthes on your Windows Server so you want to set the patch setting to Manual. The Azure machine has the patch orchestration option as `AutomaticByOS/Windows` automatic updates and you're unable to change the patch orchestration to Manual Updates by using **Change update settings**.
+You want to ensure that the Windows Update client won't install patches on your Windows Server so you want to set the patch setting to Manual. The Azure machine has the patch orchestration option as `AutomaticByOS/Windows` automatic updates and you're unable to change the patch orchestration to Manual Updates by using **Change update settings**.
 
 #### Resolution
 
diff --git a/articles/update-manager/whats-new.md b/articles/update-manager/whats-new.md
@@ -141,7 +141,7 @@ The limit on the number of subscriptions that you can manage to use the Update M
 
 ### New prerequisite for scheduled patching
 
-A new patch orchestration - **Customer Managed Schedules (Preview)** is introduced as a prerequisite to enable scheduled patching on Azure VMs. The new patch enables the *Azure-orchestrated* and *BypassPlatformSafteyChecksOnUserSchedule* VM properties on your behalf after receiving the consent. [Learn more](prerequsite-for-schedule-patching.md).
+A new patch orchestration - **Customer Managed Schedules (Preview)** is introduced as a prerequisite to enable scheduled patching on Azure VMs. The new patch enables the *Azure-orchestrated* and *BypassPlatformSafetyChecksOnUserSchedule* VM properties on your behalf after receiving the consent. [Learn more](prerequsite-for-schedule-patching.md).
 
 > [!IMPORTANT]
 > For a seamless scheduled patching experience, we recommend that for all Azure VMs, you update the patch orchestration to **Customer Managed Schedules (Preview)** by **30th June 2023**. If you fail to update the patch orchestration by **30th June 2023**, you can experience a disruption in business continuity because the schedules will fail to patch the VMs.
diff --git a/articles/virtual-desktop/redirection-configure-location.md b/articles/virtual-desktop/redirection-configure-location.md
@@ -175,7 +175,7 @@ To enable location services without Intune, you can use Group Policy to configur
 
    1. Enable individual Microsoft Store, MSIX, or Appx apps (this value needs to be set per user). Replace `<Package Family Name>` with the package family name of the app, for example `Microsoft.BingWeather_8wekyb3d8bbwe`. You can get a list of apps and their package family name using the [Get-AppxPackage](/powershell/module/appx/get-appxpackage) PowerShell cmdlet.
 
-      - **Key**: `HKEY_CURRENT_USER\oftware\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\location\<Package Family Name>`
+      - **Key**: `HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\location\<Package Family Name>`
       - **Type**: `REG_SZ` (String value)
       - **Value name**: `Value`
       - **Value data**: `Allow`
@@ -221,7 +221,7 @@ To view redirection support in Windows App and the Remote Desktop app, see [Comp
 
 On Windows, you can enable location services in the Windows Settings app. For more information, see [Windows location service and privacy](https://support.microsoft.com/windows/windows-location-service-and-privacy-3a8eee0a-5b0b-dc07-eede-2a5ca1c49088). The steps in this article to enable location services in a remote session using Intune and Group Policy can also be applied to local Windows devices.
 
-To enable location services on other platforms, refer to the relevent manufacturer's documentation.
+To enable location services on other platforms, refer to the relevant manufacturer's documentation.
 
 ## Test location redirection
 
diff --git a/articles/virtual-desktop/session-host-update-configure.md b/articles/virtual-desktop/session-host-update-configure.md
@@ -49,11 +49,11 @@ Before you update session hosts using session host update, you need:
 
       | Name | Type | Applies to |
       |--|--|--|
-      | Reset password | Allow | Decendent Computer objects |
-      | Validated write to DNS host name | Allow | Decendent Computer objects |
-      | Validated write to service principal name | Allow | Decendent Computer objects |
-      | Read account restrictions | Allow | Decendent Computer objects |
-      | Write account restrictions | Allow | Decendent Computer objects |
+      | Reset password | Allow | Descendant Computer objects |
+      | Validated write to DNS host name | Allow | Descendant Computer objects |
+      | Validated write to service principal name | Allow | Descendant Computer objects |
+      | Read account restrictions | Allow | Descendant Computer objects |
+      | Write account restrictions | Allow | Descendant Computer objects |
 
       Beginning with [KB5020276](https://support.microsoft.com/help/5020276), further protections were introduced for the reuse of computer accounts in an Active Directory domain. To successfully reuse the existing computer object for the session host, either:
 
diff --git a/articles/virtual-desktop/windows-11-language-packs.md b/articles/virtual-desktop/windows-11-language-packs.md
@@ -87,7 +87,7 @@ You can create a custom image by following these steps:
    $CSVFile = "Windows-10-1809-FOD-to-LP-Mapping-Table.csv"
    $filePath = (Get-Location).Path + "\$CSVFile"
 
-   ##Import Necesarry CSV File##
+   ##Import Necessary CSV File##
    $FODList = Import-Csv -Path $filePath -Delimiter ";"
 
    ##Set Language (Target)##
diff --git a/articles/virtual-network-manager/create-virtual-network-manager-bicep.md b/articles/virtual-network-manager/create-virtual-network-manager-bicep.md
@@ -151,7 +151,7 @@ resource deploymentScript 'Microsoft.Resources/deploymentScripts@2020-10-01' = {
       # string with comma-separated list of deployment target regions
       [parameter(mandatory=$true)][string[]]$targetLocations,
 
-      # configuration type to deploy. must be either connecticity or securityadmin
+      # configuration type to deploy. must be either connectivity or securityadmin
       [parameter(mandatory=$true)][ValidateSet('Connectivity','SecurityAdmin')][string]$configType,
 
       # AVNM resource group name
diff --git a/articles/virtual-network/create-peering-different-subscriptions-service-principal.md b/articles/virtual-network/create-peering-different-subscriptions-service-principal.md
@@ -245,7 +245,7 @@ An administrator in the **subscription-1** Microsoft Entra ID tenant must approv
     echo $appid2
     ```
 
-1. Use the appid for **spn-2-peer-vnet** and the Microsoft Entra ID tenant ID for **subcription-1** to build the sign-in URL for the approval. The URL is built from the following example:
+1. Use the appid for **spn-2-peer-vnet** and the Microsoft Entra ID tenant ID for **subscription-1** to build the sign-in URL for the approval. The URL is built from the following example:
 
     ```
     https://login.microsoftonline.com/entra-tenant-id-subscription-1/oauth2/authorize?client_id={$appid2}&response_type=code&redirect_uri=https://www.microsoft.com
diff --git a/articles/virtual-network/ip-services/manage-custom-ip-address-prefix.md b/articles/virtual-network/ip-services/manage-custom-ip-address-prefix.md
@@ -151,7 +151,7 @@ The operation is asynchronous. You can check the status by reviewing the **Commi
 To fully remove a custom IP prefix, it must be deprovisioned and then deleted. 
 
 > [!IMPORTANT]
-> It is strongly reccomended to decommission the range **prior** to modifying/deleting the Route Origin Authorization (ROA) you created with your Routing Internet Registry. Failure to do this will mean Microsoft will still be advertising your range when not authrorized to do so. Please see the [creation documentation](create-custom-ip-address-prefix-powershell.md) for more information about ROAs.
+> It is strongly recommended to decommission the range **prior** to modifying/deleting the Route Origin Authorization (ROA) you created with your Routing Internet Registry. Failure to do this will mean Microsoft will still be advertising your range when not authorized to do so. Please see the [creation documentation](create-custom-ip-address-prefix-powershell.md) for more information about ROAs.
 
 > [!NOTE]
 > If there is a requirement to migrate an provisioned range from one region to the other, the original custom IP prefix must be fully removed from the first region before a new custom IP prefix with the same address range can be created in another region.
diff --git a/articles/virtual-network/virtual-network-tap-overview.md b/articles/virtual-network/virtual-network-tap-overview.md
@@ -43,7 +43,7 @@ The accounts you use to apply TAP configuration on network interfaces must be as
 
 - [Ixia CloudLens](https://www.ixiacom.com/cloudlens/cloudlens-azure)
 
-- [cPacket Cloud Visbility](https://www.cpacket.com/cloud)
+- [cPacket Cloud Visibility](https://www.cpacket.com/cloud)
 
 - [Big Switch Big Monitoring Fabric](https://www.arista.com/en/bigswitch)
 
diff --git a/articles/virtual-wan/disaster-recovery-design.md b/articles/virtual-wan/disaster-recovery-design.md
@@ -56,7 +56,7 @@ If network connectivity over different transport type isn't possible, then choos
 
 ## Remote user connectivity considerations
 
-Remote user connectivity is established using point-to-site VPN between an end-device to a network. Following a network failure, the end-device would drop and attempt to re-estabilish the VPN tunnel. Therefore, for point-to-site VPN, your disaster recovery design should aim to minimize the recovery time following a failure. The following network redundancy would help minimize the recovery time. Depending on how critical the connections are you can choose some or all of these options.
+Remote user connectivity is established using point-to-site VPN between an end-device to a network. Following a network failure, the end-device would drop and attempt to re-establish the VPN tunnel. Therefore, for point-to-site VPN, your disaster recovery design should aim to minimize the recovery time following a failure. The following network redundancy would help minimize the recovery time. Depending on how critical the connections are you can choose some or all of these options.
 
 - Access network redundancy (discussed above).
 - Managing redundant virtual hub for point-to-site VPN termination. When you have multiple virtual hubs with point-to-site gateways, VWAN provides global profile listing all the point-to-site endpoints. With the global profile, your end-devices could connect to the closest available virtual hub that offers the best network performance. If all your Azure deployments are in a single region and the end devices that connect are in close proximity to the region, you can have redundant virtual hubs within the region. If your deployment and end-devices are spread across multiple regions, you can deploy virtual hub with point-to-site gateway in each of your selected region.  Virtual WAN has a built-in traffic manager that selects the best hub for remote user connectivity automatically.
@@ -111,7 +111,7 @@ If your on-premises branch locations are spread around two or more Azure regions
 
 Disaster recovery considerations for ExpressRoute private peering are discussed in [Designing for disaster recovery with ExpressRoute private peering](../expressroute/designing-for-disaster-recovery-with-expressroute-privatepeering.md#small-to-medium-on-premises-network-considerations). As noted in the article, the concepts described in that article equally apply to ExpressRoute gateways created within a virtual hub. Using a redundant virtual hub within the region, as shown in the following diagram, is the only topology enhancement recommended for [Small to medium on-premises network considerations](../expressroute/index.yml).
 
-:::image type="content" source="./media/disaster-recovery-design/expressroute-multi-hub.png" alt-text="Diagram of multi-hub Expresss Route connectivity.":::
+:::image type="content" source="./media/disaster-recovery-design/expressroute-multi-hub.png" alt-text="Diagram of multi-hub Express Route connectivity.":::
 
 In the above diagram, the ExpressRoute 2 is terminated on a separate ExpressRoute gateway within a second virtual hub within the region.
 
diff --git a/articles/virtual-wan/how-to-forced-tunnel.md b/articles/virtual-wan/how-to-forced-tunnel.md
@@ -259,7 +259,7 @@ Below is a sample EAP XML file. Change the *TrustedRootCA* field to the thumbpri
                 <TLSExtensions xmlns="http://www.microsoft.com/provisioning/EapTlsConnectionPropertiesV2">
                     <FilteringInfo xmlns="http://www.microsoft.com/provisioning/EapTlsConnectionPropertiesV3">
                         <CAHashList Enabled="true">
-                            <IssuerHash> ROOT CERTIFCATE THUMBPRINT  </IssuerHash>
+                            <IssuerHash> ROOT CERTIFICATE THUMBPRINT  </IssuerHash>
                         </CAHashList>
                     </FilteringInfo>
                 </TLSExtensions>
diff --git a/articles/virtual-wan/how-to-palo-alto-cloud-ngfw.md b/articles/virtual-wan/how-to-palo-alto-cloud-ngfw.md
diff --git a/articles/virtual-wan/how-to-routing-policies.md b/articles/virtual-wan/how-to-routing-policies.md
diff --git a/articles/virtual-wan/how-to-virtual-hub-routing-powershell.md b/articles/virtual-wan/how-to-virtual-hub-routing-powershell.md
diff --git a/articles/virtual-wan/third-party-integrations.md b/articles/virtual-wan/third-party-integrations.md
diff --git a/articles/virtual-wan/virtual-wan-locations-partners.md b/articles/virtual-wan/virtual-wan-locations-partners.md
diff --git a/articles/virtual-wan/whats-new.md b/articles/virtual-wan/whats-new.md
