Merge pull request #125308 from ArieHein/Spelling-52

Jak-MS · web-flow · commit af62e802e633 · 2024-12-23T16:50:59.000-06:00
Spelling Fixes
diff --git a/articles/databox-online/azure-stack-edge-gpu-deploy-configure-network-compute-web-proxy.md b/articles/databox-online/azure-stack-edge-gpu-deploy-configure-network-compute-web-proxy.md
@@ -121,7 +121,7 @@ Follow these steps to configure the network for your device.
 
 
      > [!NOTE]
-     > We recommend that you do not switch the local IP address of the network interface from static to DCHP, unless you have another IP address to connect to the device. If using one network interface and you switch to DHCP, there would be no way to determine the DHCP address. If you want to change to a DHCP address, wait until after the device has activated with the service, and then change. You can then view the IPs of all the adapters in the **Device properties** in the Azure portal for your service.
+     > We recommend that you do not switch the local IP address of the network interface from static to DHCP, unless you have another IP address to connect to the device. If using one network interface and you switch to DHCP, there would be no way to determine the DHCP address. If you want to change to a DHCP address, wait until after the device has activated with the service, and then change. You can then view the IPs of all the adapters in the **Device properties** in the Azure portal for your service.
 
 
     After you configure and apply the network settings, select **Next: Advanced networking** to configure compute network.
diff --git a/articles/databox-online/azure-stack-edge-gpu-deploy-virtual-machine-install-gpu-extension.md b/articles/databox-online/azure-stack-edge-gpu-deploy-virtual-machine-install-gpu-extension.md
@@ -279,9 +279,9 @@ Try the new cross-platform PowerShell https://aka.ms/pscore6
 PS C:\WINDOWS\system32> $templateFile = "C:\12-09-2020\ExtensionTemplates\addGPUextensiontoVM.json"
 PS C:\WINDOWS\system32> $templateParameterFile = "C:\12-09-2020\ExtensionTemplates\addGPUExtLinuxVM.parameters.json"
 PS C:\WINDOWS\system32> $RGName = "rg2"
-PS C:\WINDOWS\system32> New-AzureRmResourceGroupDeployment -ResourceGroupName $RGName -TemplateFile $templateFile -TemplateParameterFile $templateParameterFile -Name "delpoyment7"
+PS C:\WINDOWS\system32> New-AzureRmResourceGroupDeployment -ResourceGroupName $RGName -TemplateFile $templateFile -TemplateParameterFile $templateParameterFile -Name "deployment7"
 
-DeploymentName          : delpoyment7
+DeploymentName          : deployment7
 ResourceGroupName       : rg2
 ProvisioningState       : Succeeded
 Timestamp               : 12/10/2020 10:43:23 PM
diff --git a/articles/databox-online/azure-stack-edge-gpu-deploy-virtual-machine-powershell-script.md b/articles/databox-online/azure-stack-edge-gpu-deploy-virtual-machine-powershell-script.md
@@ -205,7 +205,7 @@ Before you begin creating and managing a VM on your Azure Stack Edge Pro device
     
      Using Vnet /subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourceGroups/ASERG/providers/Microsoft.Network/virtualNetworks/ASEVNET
     
-     Creating a new Newtork Interface
+     Creating a new Network Interface
     WARNING: The output object type of this cmdlet will be modified in a future release.
     
     VirtualMachine              :
diff --git a/articles/databox-online/azure-stack-edge-gpu-deploy-virtual-machine-templates.md b/articles/databox-online/azure-stack-edge-gpu-deploy-virtual-machine-templates.md
@@ -582,7 +582,7 @@ Assign appropriate parameters in `CreateVM.parameters.json` for your Azure Stack
 
     Use ASEVNET for Vnet name, ASEVNETsubNet for Subnet name, and ASERG for Vnet resource group name.
     
-1. Now you’ll need a static IP address to assign to the VM that is in the subnet network defined above. Replace **PrivateIPAddress** with this address in the parameter file. To have the VM get an IP address from your local DCHP server, leave the `privateIPAddress` value blank.  
+1. Now you’ll need a static IP address to assign to the VM that is in the subnet network defined above. Replace **PrivateIPAddress** with this address in the parameter file. To have the VM get an IP address from your local DHCP server, leave the `privateIPAddress` value blank.  
     
     ```json
     "privateIPAddress": {
@@ -730,7 +730,7 @@ Assign appropriate parameters in `CreateVM.parameters.json` for your Azure Stack
 
     Use ASEVNET for Vnet name, ASEVNETsubNet for Subnet name, and ASERG for Vnet resource group name.
     
-1. Now you’ll need a static IP address to assign to the VM that is in the subnet network defined above. Replace **PrivateIPAddress** with this address in the parameter file. To have the VM get an IP address from your local DCHP server, leave the `privateIPAddress` value blank.  
+1. Now you’ll need a static IP address to assign to the VM that is in the subnet network defined above. Replace **PrivateIPAddress** with this address in the parameter file. To have the VM get an IP address from your local DHCP server, leave the `privateIPAddress` value blank.  
     
     ```json
     "privateIPAddress": {
diff --git a/articles/databox/data-box-deploy-copy-data.md b/articles/databox/data-box-deploy-copy-data.md
@@ -29,7 +29,7 @@ ms.author: shaas
 > [!IMPORTANT]
 > Azure Data Box now supports access tier assignment at the blob level. The steps contained within this tutorial reflect the updated data copy process and are specific to block blobs. 
 >
->For help with determining the appropriate access tier for your block blob data, refer to the [Determine appropriate access tiers for block blobs](#determine-appropriate-access-tiers-for-block-blobs) section. Follow the steps containined within the [Copy data to Azure Data Box](#copy-data-to-azure-data-box) section to copy your data to the appropriate access tier.
+>For help with determining the appropriate access tier for your block blob data, refer to the [Determine appropriate access tiers for block blobs](#determine-appropriate-access-tiers-for-block-blobs) section. Follow the steps contained within the [Copy data to Azure Data Box](#copy-data-to-azure-data-box) section to copy your data to the appropriate access tier.
 >
 > The information contained within this section applies to orders placed after April 1, 2024.
 
diff --git a/articles/databox/data-box-next-gen-quickstart-portal.md b/articles/databox/data-box-next-gen-quickstart-portal.md
@@ -108,7 +108,7 @@ When you receive the Data Box, perform the following steps to cable, connect, an
 
     1. Connect the power cable to the device.
     2. Use the RJ-45 CAT 6 network cable to connect your host computer to the management port (MGMT) on the device. 
-    3. Use the QFSP28 copper cable to connect at least one 100 Gbps (preferred over 10 Gbps or 1 Gbps) network interface, DATA 1 or DATA 2 for data. 
+    3. Use the QSFP28 copper cable to connect at least one 100 Gbps (preferred over 10 Gbps or 1 Gbps) network interface, DATA 1 or DATA 2 for data. 
     4. Turn on the device. The power button is on the front panel of the device.
 
 
diff --git a/articles/dev-box/how-to-connect-dev-box-virtual-switch.md b/articles/dev-box/how-to-connect-dev-box-virtual-switch.md
@@ -17,7 +17,7 @@ This article provides guidance on how to set up and use dev box with virtual swi
 Dev box supports nested virtualization. You can create virtual machines inside a dev box and connect them to the default virtual switch *Default Switch*. If you want to create another virtual switch with internet access, set up a NAT network with an internal virtual switch. Use an IP address range that suits your required configuration.
 
 > [!WARNING]
-> Incorrect configuration of virtual switch will cause you to lose the connection to dev box immediately and this is NOT reversable. Please setup with extreme care.
+> Incorrect configuration of virtual switch will cause you to lose the connection to dev box immediately and this is NOT reversible. Please setup with extreme care.
 
 ## Prerequisites
 - A dev box with Hyper-V and Virtual Machine Platform installed.
diff --git a/articles/dns/dns-private-resolver-get-started-portal.md b/articles/dns/dns-private-resolver-get-started-portal.md
@@ -156,7 +156,7 @@ Add or remove specific rules your DNS forwarding ruleset as desired, such as:
 - A wildcard rule to forward unmatched DNS queries to a protective DNS service.
 
 > [!IMPORTANT]
-> The rules shown in this quickstart are examples of rules that can be used for specific scenarios. None of the fowarding rules described in this article are required. Be careful to test your forwarding rules and ensure that the rules don't cause DNS resolution issues.<br><br>
+> The rules shown in this quickstart are examples of rules that can be used for specific scenarios. None of the forwarding rules described in this article are required. Be careful to test your forwarding rules and ensure that the rules don't cause DNS resolution issues.<br><br>
 > **If you include a wildcard rule in your ruleset, ensure that the target DNS service can resolve public DNS names. Some Azure services have dependencies on public name resolution.**
 
 ### Delete a rule from the forwarding ruleset
diff --git a/articles/dns/dns-private-resolver-get-started-powershell.md b/articles/dns/dns-private-resolver-get-started-powershell.md
@@ -250,7 +250,7 @@ In this example:
 - 10.5.5.5 is a protective DNS service.
 
 > [!IMPORTANT]
-> The rules shown in this quickstart are examples of rules that can be used for specific scenarios. None of the fowarding rules described in this article are required. Be careful to test your forwarding rules and ensure that the rules don't cause DNS resolution issues.<br><br>
+> The rules shown in this quickstart are examples of rules that can be used for specific scenarios. None of the forwarding rules described in this article are required. Be careful to test your forwarding rules and ensure that the rules don't cause DNS resolution issues.<br><br>
 > **If you include a wildcard rule in your ruleset, ensure that the target DNS service can resolve public DNS names. Some Azure services have dependencies on public name resolution.**
 
 ## Test the private resolver
diff --git a/articles/dns/dns-reverse-dns-for-azure-services.md b/articles/dns/dns-reverse-dns-for-azure-services.md
@@ -92,7 +92,7 @@ azure network public-ip set -n PublicIp -g MyResourceGroup -d contosoapp1 -f con
 
 To update reverse DNS on a public IP address with an existing PTR:
 
-```azurecli-interacgive
+```azurecli-interactive
 az network public-ip update --resource-group MyResourceGroup --name PublicIp --reverse-fqdn contosoapp1.westus.cloudapp.azure.com.
 ```
 
diff --git a/articles/dns/dnssec.md b/articles/dns/dnssec.md
@@ -266,7 +266,7 @@ This list is provided to help understand some of the common terms used when disc
 | Trust anchor | A preconfigured public key that is associated with a particular zone. A trust anchor enables a DNS resolver to validate signed DNSSEC resource records for that zone and to build authentication chains to child zones. |
 | Unsigned zone | Any DNS zone that has not been signed as defined by RFC 4035 [7] Section 2. |
 | Zone signing | Zone signing is the process of creating and adding DNSSEC-related resource records to a zone, making it compatible with DNSSEC validation. |
-| Zone unsigning | Zone unsigning is the process of removing DNSSSEC-related resource records from a zone, restoring it to an unsigned status. |
+| Zone unsigning | Zone unsigning is the process of removing DNSSEC-related resource records from a zone, restoring it to an unsigned status. |
 | Zone signing key (ZSK) | An authentication key that corresponds to a private key that is used to sign a zone. Typically, a zone signing key is part of the same DNSKEY RRSet as the key signing key whose corresponding private key signs this DNSKEY RRSet, but the zone signing key is used for a slightly different purpose and can differ from the key signing key in other ways, such as in validity lifetime. Designating an authentication key as a zone signing key is purely an operational issue; DNSSEC validation doesn't distinguish between zone signing keys and other DNSSEC authentication keys. It's possible to use a single key as both a key signing key and a zone signing key. |
 
 ## Next steps
diff --git a/articles/dns/private-dns-arg.md b/articles/dns/private-dns-arg.md
@@ -12,7 +12,7 @@ ms.topic: how-to
 
 # Private DNS information in Azure Resource Graph
 
-This article describes some of the ways you can use Azure Resource Graph Exporer to view information about your Azure Private DNS zones and records. Some example queries are provided.
+This article describes some of the ways you can use Azure Resource Graph Explorer to view information about your Azure Private DNS zones and records. Some example queries are provided.
 
 [Azure Resource Graph (ARG)](../governance/resource-graph/overview.md) is an Azure service that allows you to query your Azure resources with complex filtering, grouping, and sorting. ARG queries provide detailed information about your resources and you can display the results in several ways. 
 
diff --git a/articles/dns/private-dns-getstarted-portal.md b/articles/dns/private-dns-getstarted-portal.md
@@ -114,7 +114,7 @@ Now, create a virtual machine to test autoregistgration in your private DNS zone
 13. Review the settings and then click **Create**. It will take a few minutes for the virtual machine allocation to complete.
 14. Search for and select **Virtual machines** and then verify that the VM status is **Running**. If it isn't running, start the virtual machine.
 
-## Review autoregistion
+## Review autoregistration
 
 1. Search for or select **Private DNS zones** and then select the **private.contoso.com** zone.
 2. Under DNS Management, select Recordsets.
diff --git a/articles/dns/private-reverse-dns.md b/articles/dns/private-reverse-dns.md
@@ -39,7 +39,7 @@ To create an IPv4 reverse DNS record in your zone, add the remaining IP address
 * 10.1.2.5 in the 2.1.10.in-addr.arpa zone appears as:`5   IN  PTR  myvm.contoso.com.` 
 
 > [!IMPORTANT]
-> A reverse DNS zone for address space with a longer prefix takes precendence. For example, if all three zones contain entries for the IPv4 address 10.1.2.5 as shown here, only the entry in the 2.1.10.in-addr.arpa zone will be used. If the longer prefix zone (2.1.10.in-addr.arpa) exists, then all reverse DNS entries for the corresponding /24 address space must be entered in this zone.
+> A reverse DNS zone for address space with a longer prefix takes precedence. For example, if all three zones contain entries for the IPv4 address 10.1.2.5 as shown here, only the entry in the 2.1.10.in-addr.arpa zone will be used. If the longer prefix zone (2.1.10.in-addr.arpa) exists, then all reverse DNS entries for the corresponding /24 address space must be entered in this zone.
 
 ## Requirements and restrictions
 
diff --git a/articles/dns/tutorial-dns-private-resolver-failover.md b/articles/dns/tutorial-dns-private-resolver-failover.md
@@ -17,7 +17,7 @@ This article details how to eliminate a single point of failure in your on-premi
 In this tutorial, you learn how to:
 
 > [!div class="checklist"]
-> * Resolve Azure Private DNS zones using on-premises conditional fowarders and Azure DNS private resolvers.
+> * Resolve Azure Private DNS zones using on-premises conditional forwarders and Azure DNS private resolvers.
 > * Enable on-premises DNS failover for your Azure Private DNS zones.
 
 The following diagram shows the failover scenario discussed in this article.

Original file line number	Diff line number	Diff line change
`@@ -29,7 +29,7 @@ ms.author: shaas`
`29`	`29`	`> [!IMPORTANT]`
`30`	`30`	`> Azure Data Box now supports access tier assignment at the blob level. The steps contained within this tutorial reflect the updated data copy process and are specific to block blobs.`
`31`	`31`	`>`
`32`		`->For help with determining the appropriate access tier for your block blob data, refer to the [Determine appropriate access tiers for block blobs](#determine-appropriate-access-tiers-for-block-blobs) section. Follow the steps containined within the [Copy data to Azure Data Box](#copy-data-to-azure-data-box) section to copy your data to the appropriate access tier.`
	`32`	`+>For help with determining the appropriate access tier for your block blob data, refer to the [Determine appropriate access tiers for block blobs](#determine-appropriate-access-tiers-for-block-blobs) section. Follow the steps contained within the [Copy data to Azure Data Box](#copy-data-to-azure-data-box) section to copy your data to the appropriate access tier.`
`33`	`33`	`>`
`34`	`34`	`> The information contained within this section applies to orders placed after April 1, 2024.`
`35`	`35`