Merge pull request #35774 from rwestMSFT/rw-1106-repeating-words

[SCOPED] Fix errant repeating words

Author: rwestMSFT

azure-sql/database/scripts/vnet-service-endpoint-rule-powershell-create.md

@@ -366,7 +366,7 @@ Or, you might be unsure whether your subnet has the `Microsoft.Sql` type name. Y
 
 Here are the phases of the PowerShell script:
 
-1. Sign in to to your Azure account, needed only once per PowerShell session. Assign variables.
+1. Sign in to your Azure account, needed only once per PowerShell session. Assign variables.
 2. Search for your virtual network, and then for your subnet.
 3. Is your subnet tagged as `Microsoft.Sql` endpoint server type?
 4. Add a Virtual Service endpoint of type name `Microsoft.Sql`, on your subnet.

azure-sql/includes/passwordless/associate-managed-identity-cli.md

@@ -31,7 +31,7 @@ If you are working with Git Bash, be careful of path conversions when using full
 
 # [Azure Spring Apps](#tab/spring-apps-identity)
 
-You can assign a managed identity to your Azure Spring Apps instance using the [az spring app identity assign](/azure/spring-apps/basic-standard/how-to-manage-user-assigned-managed-identities?tabs=azure-cli&pivots=sc-standard) command command in the Azure CLI.
+You can assign a managed identity to your Azure Spring Apps instance using the [az spring app identity assign](/azure/spring-apps/basic-standard/how-to-manage-user-assigned-managed-identities?tabs=azure-cli&pivots=sc-standard) command in the Azure CLI.
 
 ```azurecli
 az spring app identity assign \

azure-sql/managed-instance/aad-security-configure-tutorial.md

@@ -206,7 +206,7 @@ Authorization to individual databases works much the same way in SQL Managed Ins
 
 Now that we've created a database called **MyMITestDB** and a login that only has default permissions, the next step is to create a user from that login. At the moment, the login can connect to the SQL managed instance and see all the databases, but it can't interact with the databases. If you sign in with the Microsoft Entra account that has the default permissions and try to expand the newly created database, you'll see the following error:
 
-![Screenshot of an error message from the the SSMS Object Explorer that reads "The database MyMITestDB is not accessible. (ObjectExplorer)".](./media/aad-security-configure-tutorial/ssms-db-not-accessible.png)
+![Screenshot of an error message from the SSMS Object Explorer that reads "The database MyMITestDB is not accessible. (ObjectExplorer)".](./media/aad-security-configure-tutorial/ssms-db-not-accessible.png)
 
 For more information on granting database permissions, see [Getting Started with Database Engine Permissions](/sql/relational-databases/security/authentication-access/getting-started-with-database-engine-permissions).
 

azure-sql/managed-instance/data-virtualization-overview.md

@@ -134,7 +134,7 @@ SECRET = 'sv=2018-03-28&ss=bfqt&srt=sco&sp=rwdlacup&se=2019-04-18T20:42:12Z&st=2
 
 ## External data source
 
-An external data source is an abstraction that that provides an easy reference to a file location across multiple queries. To query public locations, specify the file location when you create an external data source:
+An external data source is an abstraction that provides an easy reference to a file location across multiple queries. To query public locations, specify the file location when you create an external data source:
 
 ```sql
 CREATE EXTERNAL DATA SOURCE MyExternalDataSource

azure-sql/managed-instance/management-operations-cancel.md

@@ -119,7 +119,7 @@ Instances that have failed to create are still present as a resource and:
 
 
 > [!NOTE]
-> To minimize noise in the the list of resources or managed instances, delete instances that have failed to deploy or instances with cancelled deployments. 
+> To minimize noise in the list of resources or managed instances, delete instances that have failed to deploy or instances with cancelled deployments. 
 
 
 ## Next steps

azure-sql/virtual-machines/windows/availability-group-overview.md

@@ -111,7 +111,7 @@ On an Azure VM failover cluster, we recommend a single NIC per server (cluster n
 
 As basic availability group doesn't allow more than one secondary replica and there's no read access to the secondary replica, you can use the database mirroring connection strings for basic availability groups. Using the connection string eliminates the need to have listeners. Removing the listener dependency is helpful for availability groups on Azure VMs as it eliminates the need for a load balancer or having to add additional IPs to the load balancer when you have multiple listeners for additional databases.
 
-For example, to explicitly connect using TCP/IP to the AG database AdventureWorks on either Replica_A or Replica_B of a Basic AG (or any AG that that has only one secondary replica and the read access isn't allowed in the secondary replica), a client application could supply the following database mirroring connection string to successfully connect to the AG:
+For example, to explicitly connect using TCP/IP to the AG database AdventureWorks on either Replica_A or Replica_B of a Basic AG (or any AG that has only one secondary replica and the read access isn't allowed in the secondary replica), a client application could supply the following database mirroring connection string to successfully connect to the AG:
 
 `Server=Replica_A; Failover_Partner=Replica_B; Database=AdventureWorks; Network=dbmssocn`
 

azure-sql/virtual-machines/windows/configure-azure-ad-authentication-for-sql-vm.md

@@ -297,7 +297,7 @@ You can enable Microsoft Entra authentication for specific unregistered instance
 When using the `Set-AzVMExtension -ExtensionName "SqlIaasExtension"` command to enable Microsoft Entra authentication for a SQL Server instance, consider the following:
 - Permissions of the managed identity are only checked when the `CheckPermissions` parameter is set to `true`.
 - Specify the client ID of the identity `ClientID` parameter to use a **user-assigned managed identity**. When the `ClientID` parameter is empty, a **system-assigned managed identity** is used.
-- Provide a list of instances in the the `EnableForGivenInstances` parameter to enable Microsoft Entra authentication for specific unregistered instances. Othewrise, use the `EnableForAllInstances` parameter to enable Microsoft Entra authentication for all unregistered instances on the virtual machine. 
+- Provide a list of instances in the `EnableForGivenInstances` parameter to enable Microsoft Entra authentication for specific unregistered instances. Othewrise, use the `EnableForAllInstances` parameter to enable Microsoft Entra authentication for all unregistered instances on the virtual machine. 
 
 
 The following example enables Microsoft Entra authentication for all instances on the VM using a **system-assigned identity**:

docs/azdata/reference/reference-azdata-app.md

@@ -48,15 +48,15 @@ Scaffold a new application `spec.yaml` only.
 ```bash
 azdata app init --spec
 ```
-Scaffold a new R application application skeleton based on the `r` template.
+Scaffold a new R application skeleton based on the `r` template.
 ```bash
 azdata app init --name reduce --template r
 ```
-Scaffold a new Python application application skeleton based on the `python` template.
+Scaffold a new Python application skeleton based on the `python` template.
 ```bash
 azdata app init --name reduce --template python
 ```
-Scaffold a new SSIS application application skeleton based on the `ssis` template.
+Scaffold a new SSIS application skeleton based on the `ssis` template.
 ```bash
 azdata app init --name reduce --template ssis            
 ```

docs/connect/odbc/use-xa-with-dtc.md

@@ -714,7 +714,7 @@ void XaTestRunner::GetUniqueName(std::string& name)
     auto id = counter++;
 
     auto duration = std::chrono::system_clock::now().time_since_epoch();
-    long long millis = std::chrono::duration_cast<std::chrono::milliseconds>(duration).count();
+    long millis = std::chrono::duration_cast<std::chrono::milliseconds>(duration).count();
     char szName[64];
     sprintf_s(szName, sizeof(szName), "test_%d_%lld", id, millis);
     name = szName;

docs/integration-services/data-flow/data-streaming-destination.md

@@ -17,7 +17,7 @@ f1_keywords:
 
   The **Data Streaming Destination** is a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] (SSIS) destination component that lets the **OLE DB Provider for SSIS** consume output of an SSIS package as a tabular result set. You can create a linked server that uses the OLE DB Provider for SSIS and then run a SQL query on the linked server to display data returned by the SSIS package.  
 
- In the following example example, the following query returns output from the Package.dtsx package in the SSISPackagePublishing project in the Power BI folder of the SSIS Catalog. This query uses the linked server named  [Default Linked Server for Integration Services] that in turn uses the new OLE DB Provider for SSIS. The query includes folder name, project name, and package name in the SSIS catalog. The OLE DB Provider for SSIS runs the package you specified in the query and returns the tabular result set.  
+ In the following example, the following query returns output from the Package.dtsx package in the SSISPackagePublishing project in the Power BI folder of the SSIS Catalog. This query uses the linked server named  [Default Linked Server for Integration Services] that in turn uses the new OLE DB Provider for SSIS. The query includes folder name, project name, and package name in the SSIS catalog. The OLE DB Provider for SSIS runs the package you specified in the query and returns the tabular result set.  
 
 ```sql
 SELECT * FROM OPENQUERY([Default Linked Server for Integration Services], N'Folder=Power BI;Project=SSISPackagePublishing;Package=Package.dtsx')