Merge pull request #14091 from nschonni/double-the

v-shils · web-flow · commit a4dc28a70692 · 2018-08-28T10:33:20.000-07:00
typo: Double word "the"
diff --git a/articles/active-directory/active-directory-tou.md b/articles/active-directory/active-directory-tou.md
@@ -160,7 +160,7 @@ The following procedure describes how to add a Terms of use language.
 
 1. Select the Terms of use you want to edit.
 
-1. In the the details pane, click the **Languages** tab.
+1. In the details pane, click the **Languages** tab.
 
     ![Add TOU](media/active-directory-tou/languages-tou.png)
 
diff --git a/articles/active-directory/managed-service-identity/qs-configure-template-windows-vm.md b/articles/active-directory/managed-service-identity/qs-configure-template-windows-vm.md
@@ -353,7 +353,7 @@ If you have a VM that no longer needs a managed service identity:
 
 1. Whether you sign in to Azure locally or via the Azure portal, use an account that is associated with the Azure subscription that contains the VM.
 
-2. Load the template into an [editor](#azure-resource-manager-templates) and locate the `Microsoft.Compute/virtualMachines` resource of interest within the `resources` section. If you have a VM that only has user assigned identity, you can disable it by changing the the identity type to `None`.
+2. Load the template into an [editor](#azure-resource-manager-templates) and locate the `Microsoft.Compute/virtualMachines` resource of interest within the `resources` section. If you have a VM that only has user assigned identity, you can disable it by changing the identity type to `None`.
  
    The following example shows you how remove all user assigned identities from a VM with no system assigned identities:
    
diff --git a/articles/active-directory/managed-service-identity/qs-configure-template-windows-vmss.md b/articles/active-directory/managed-service-identity/qs-configure-template-windows-vmss.md
@@ -318,7 +318,7 @@ If you have a virtual machine scale set that no longer needs a managed service i
 
 1. Whether you sign in to Azure locally or via the Azure portal, use an account that is associated with the Azure subscription that contains the virtual machine scale set.
 
-2. Load the template into an [editor](#azure-resource-manager-templates) and locate the `Microsoft.Compute/virtualMachineScaleSets` resource of interest within the `resources` section. If you have a virtual machine scale set that only has user assigned identity, you can disable it by changing the the identity type to `None`.
+2. Load the template into an [editor](#azure-resource-manager-templates) and locate the `Microsoft.Compute/virtualMachineScaleSets` resource of interest within the `resources` section. If you have a virtual machine scale set that only has user assigned identity, you can disable it by changing the identity type to `None`.
 
    The following example shows you how remove all user assigned identities from a VM with no system assigned identities:
 
diff --git a/articles/cognitive-services/Speech-Service/third-party-notices.md b/articles/cognitive-services/Speech-Service/third-party-notices.md
@@ -29,7 +29,7 @@ The Cognitive Services Client Speech SDK is using Parson, obtained from https://
 
 **b. azure-c-shared-utility - Azure C SDKs common code**
 
-The Cognitive Services Client Speech SDK is using Azure C SDK Common Code, obtained from https://github.com/Azure/azure-c-shared-utility. It is licensed under the The MIT License (MIT):
+The Cognitive Services Client Speech SDK is using Azure C SDK Common Code, obtained from https://github.com/Azure/azure-c-shared-utility. It is licensed under the MIT License (MIT):
 
     Microsoft Azure IoT SDKs
     Copyright (c) Microsoft Corporation
diff --git a/articles/data-factory/monitor-integration-runtime.md b/articles/data-factory/monitor-integration-runtime.md
@@ -82,7 +82,7 @@ Some settings of the properties make more sense when there are two or more nodes
 
 The default value of the concurrent jobs limit is set based on the machine size. The factors used to calculate this value depend on the amount of RAM and the number of CPU cores of the machine. So the more cores and the more memory, the higher the default limit of concurrent jobs.
 
-You scale out by increasing the number of nodes. When you increase the number of nodes, the concurrent jobs limit is the the sum of the concurrent job limit values of all the available nodes.  For example, if one node lets you run a maximum of twelve concurrent jobs, then adding three more similar nodes lets you run a maximum of  48 concurrent jobs (that is, 4 x 12). We recommend that you increase the concurrent jobs limit only when you see low resource usage with the default values on each node.
+You scale out by increasing the number of nodes. When you increase the number of nodes, the concurrent jobs limit is the sum of the concurrent job limit values of all the available nodes.  For example, if one node lets you run a maximum of twelve concurrent jobs, then adding three more similar nodes lets you run a maximum of  48 concurrent jobs (that is, 4 x 12). We recommend that you increase the concurrent jobs limit only when you see low resource usage with the default values on each node.
 
 You can override the calculated default value in the Azure portal. Select Author > Connections > Integration Runtimes > Edit > Nodes > Modify concurrent job value per node. You can also use the PowerShell [update-azurermdatafactoryv2integrationruntimenode](https://docs.microsoft.com/en-us/powershell/module/azurerm.datafactoryv2/update-azurermdatafactoryv2integrationruntimenode?view=azurermps-6.4.0#examples) command.
   
diff --git a/articles/key-vault/about-keys-secrets-and-certificates.md b/articles/key-vault/about-keys-secrets-and-certificates.md
@@ -171,7 +171,7 @@ Azure Key Vault supports the following operations on key objects:
 -   **Backup**: Exports a key in a protected form.  
 -   **Restore**: Imports a previously backed up key.  
 
-For more information, see [Key operations in the the Key Vault REST API reference](/rest/api/keyvault).  
+For more information, see [Key operations in the Key Vault REST API reference](/rest/api/keyvault).  
 
 Once a key has been created in Azure Key Vault, the following cryptographic operations may be performed using the key:  
 
@@ -281,7 +281,7 @@ The following permissions can be used, on a per-principal basis, in the secrets
 -   *delete*: Delete the secret  
 -   *all*: All permissions  
 
-For more information on working with secrets, see [Secret operations in the the Key Vault REST API reference](/rest/api/keyvault).  
+For more information on working with secrets, see [Secret operations in the Key Vault REST API reference](/rest/api/keyvault).  
 
 ###  <a name="BKMK_SecretTags"></a> Secret tags  
 You can specify additional application-specific metadata in the form of tags. Azure Key Vault supports up to 15 tags, each of which can have a 256 character name and a 256 character value.  
@@ -441,7 +441,7 @@ If a certificate's policy is set to auto-renewal, then a notification is sent on
 -   *deleteissuers*: allows delete of Key Vault certificate issuers  
 -   *all*: grants all permissions  
 
-For more information, see the [Certificate operations in the the Key Vault REST API reference](/rest/api/keyvault). 
+For more information, see the [Certificate operations in the Key Vault REST API reference](/rest/api/keyvault). 
 
 ## See Also
 
