Merge pull request #23360 from rwestMSFT/rw-0722-select-bulk-fix

BCS2022 · web-flow · commit 8db7e136849b · 2022-07-22T13:14:29.000-07:00
[Bulk] Fix incorrect usage of "Select"
diff --git a/azure-sql/database/hyperscale-database-create-quickstart.md b/azure-sql/database/hyperscale-database-create-quickstart.md
@@ -175,9 +175,9 @@ You can create a resource group, server, and single database using Azure PowerSh
 
 The Azure Cloud Shell is a free interactive shell that you can use to run the steps in this article. It has common Azure tools preinstalled and configured to use with your account.
 
-To open the Cloud Shell, just select **Try it** from the upper right corner of a code block. You can also launch Cloud Shell in a separate browser tab by going to [https://shell.azure.com](https://shell.azure.com).
+To open the Cloud Shell, select **Try it** from the upper right corner of a code block. You can also launch Cloud Shell in a separate browser tab by going to [https://shell.azure.com](https://shell.azure.com).
 
-When Cloud Shell opens, verify that **PowerShell** is selected for your environment. Subsequent sessions will use Azure CLI in a Bash environment, Select **Copy** to copy the blocks of code, paste it into the Cloud Shell, and press **Enter** to run it.
+When Cloud Shell opens, verify that **PowerShell** is selected for your environment. Subsequent sessions will use Azure CLI in a PowerShell environment. Select **Copy** to copy the blocks of code, paste it into the Cloud Shell, and press **Enter** to run it.
 
 ### Set parameter values
 
diff --git a/azure-sql/database/ledger-create-a-single-database-with-ledger-enabled.md b/azure-sql/database/ledger-create-a-single-database-with-ledger-enabled.md
@@ -91,7 +91,7 @@ You'll create a resource group, a logical database server, a single ledger datab
 
 The Azure Cloud Shell is a free interactive shell that you can use to run the steps in this article. It has common Azure tools preinstalled and configured to use with your account. 
 
-To open the Cloud Shell, just select **Try it** from the upper right corner of a code block. You can also launch Cloud Shell in a separate browser tab by going to [https://shell.azure.com](https://shell.azure.com). Select **Copy** to copy the blocks of code, paste it into the Cloud Shell, and press **Enter** to run it.
+To open the Cloud Shell, select **Try it** from the upper right corner of a code block. You can also launch Cloud Shell in a separate browser tab by going to [https://shell.azure.com](https://shell.azure.com). Select **Copy** to copy the blocks of code, paste it into the Cloud Shell, and press **Enter** to run it.
 
 ### Set parameter values
 
@@ -278,7 +278,7 @@ You'll create a resource group, a logical database server, a single ledger datab
 
 The Azure Cloud Shell is a free interactive shell that you can use to run the steps in this article. It has common Azure tools preinstalled and configured to use with your account.
 
-To open the Cloud Shell, just select **Try it** from the upper right corner of a code block. You can also launch Cloud Shell in a separate browser tab by going to [https://shell.azure.com](https://shell.azure.com). Select **Copy** to copy the blocks of code, paste it into the Cloud Shell, and press **Enter** to run it.
+To open the Cloud Shell, select **Try it** from the upper right corner of a code block. You can also launch Cloud Shell in a separate browser tab by going to [https://shell.azure.com](https://shell.azure.com). Select **Copy** to copy the blocks of code, paste it into the Cloud Shell, and press **Enter** to run it.
 
 ### Set parameter values
 
diff --git a/azure-sql/database/maintenance-window-configure.md b/azure-sql/database/maintenance-window-configure.md
@@ -51,9 +51,9 @@ The following examples show how to configure the maintenance window using Azure
 
 The Azure Cloud Shell is a free interactive shell that you can use to run the steps in this article. It has common Azure tools preinstalled and configured to use with your account.
 
-To open the Cloud Shell, just select **Try it** from the upper right corner of a code block. You can also launch Cloud Shell in a separate browser tab by going to [https://shell.azure.com](https://shell.azure.com).
+To open the Cloud Shell, select **Try it** from the upper right corner of a code block. You can also launch Cloud Shell in a separate browser tab by going to [https://shell.azure.com](https://shell.azure.com).
 
-When Cloud Shell opens, verify that **PowerShell** is selected for your environment. Subsequent sessions will use Azure CLI in a Bash environment, Select **Copy** to copy the blocks of code, paste it into the Cloud Shell, and press **Enter** to run it.
+When Cloud Shell opens, verify that **PowerShell** is selected for your environment. Subsequent sessions will use Azure CLI in a PowerShell environment. Select **Copy** to copy the blocks of code, paste it into the Cloud Shell, and press **Enter** to run it.
 
 ### Discover available maintenance windows
 
@@ -157,9 +157,9 @@ Configuring the maintenance window with Azure CLI is only available for SQL Mana
 
 The Azure Cloud Shell is a free interactive shell that you can use to run the steps in this article. It has common Azure tools preinstalled and configured to use with your account.
 
-To open the Cloud Shell, just select **Try it** from the upper right corner of a code block. You can also launch Cloud Shell in a separate browser tab by going to [https://shell.azure.com](https://shell.azure.com).
+To open the Cloud Shell, select **Try it** from the upper right corner of a code block. You can also launch Cloud Shell in a separate browser tab by going to [https://shell.azure.com](https://shell.azure.com).
 
-When Cloud Shell opens, verify that **Bash** is selected for your environment. Subsequent sessions will use Azure CLI in a Bash environment, Select **Copy** to copy the blocks of code, paste it into the Cloud Shell, and press **Enter** to run it.
+When Cloud Shell opens, verify that **Bash** is selected for your environment. Subsequent sessions will use Azure CLI in a Bash environment. Select **Copy** to copy the blocks of code, paste it into the Cloud Shell, and press **Enter** to run it.
 
 ### Sign in to Azure
 
diff --git a/azure-sql/database/single-database-create-quickstart.md b/azure-sql/database/single-database-create-quickstart.md
@@ -199,9 +199,9 @@ You can create a resource group, server, and single database using Azure PowerSh
 
 The Azure Cloud Shell is a free interactive shell that you can use to run the steps in this article. It has common Azure tools preinstalled and configured to use with your account.
 
-To open the Cloud Shell, just select **Try it** from the upper right corner of a code block. You can also launch Cloud Shell in a separate browser tab by going to [https://shell.azure.com](https://shell.azure.com).
+To open the Cloud Shell, select **Try it** from the upper right corner of a code block. You can also launch Cloud Shell in a separate browser tab by going to [https://shell.azure.com](https://shell.azure.com).
 
-When Cloud Shell opens, verify that **PowerShell** is selected for your environment. Subsequent sessions will use Azure CLI in a Bash environment, Select **Copy** to copy the blocks of code, paste it into the Cloud Shell, and press **Enter** to run it.
+When Cloud Shell opens, verify that **PowerShell** is selected for your environment. Subsequent sessions will use Azure CLI in a PowerShell environment. Select **Copy** to copy the blocks of code, paste it into the Cloud Shell, and press **Enter** to run it.
 
 ### Set parameter values
 
diff --git a/azure-sql/includes/cli-launch-cloud-shell-sign-in.md b/azure-sql/includes/cli-launch-cloud-shell-sign-in.md
@@ -11,9 +11,9 @@ ms.custom: devx-track-azurecli
 
 The Azure Cloud Shell is a free interactive shell that you can use to run the steps in this article. It has common Azure tools preinstalled and configured to use with your account.
 
-To open the Cloud Shell, just select **Try it** from the upper right corner of a code block. You can also launch Cloud Shell in a separate browser tab by going to [https://shell.azure.com](https://shell.azure.com).
+To open the Cloud Shell, select **Try it** from the upper right corner of a code block. You can also launch Cloud Shell in a separate browser tab by going to [https://shell.azure.com](https://shell.azure.com).
 
-When Cloud Shell opens, verify that **Bash** is selected for your environment. Subsequent sessions will use Azure CLI in a Bash environment, Select **Copy** to copy the blocks of code, paste it into the Cloud Shell, and press **Enter** to run it.
+When Cloud Shell opens, verify that **Bash** is selected for your environment. Subsequent sessions will use Azure CLI in a Bash environment. Select **Copy** to copy the blocks of code, paste it into the Cloud Shell, and press **Enter** to run it.
 
 ### Sign in to Azure
 
diff --git a/docs/azure-data-studio/extensions/azure-sql-migration-extension.md b/docs/azure-data-studio/extensions/azure-sql-migration-extension.md
@@ -47,7 +47,7 @@ To install the Azure SQL migration extension in Azure Data Studio, follow the st
 
     :::image type="content" source="media/azure-sql-migration-extension/azure-sql-migration-icon.png" alt-text="Azure SQL migration extension":::
 
-6. You can connect to the SQL Server instance in Azure Data Studio. Right-select the instance name and select **Manage** to see the instance dashboard and the **Azure SQL Migration** extension landing page.
+6. You can connect to the SQL Server instance in Azure Data Studio. Right-click the instance name and select **Manage** to see the instance dashboard and the **Azure SQL Migration** extension landing page.
 
     :::image type="content" source="media/azure-sql-migration-extension/azure-sql-migration-extension-landing-page.png" alt-text="Landing page":::
 
diff --git a/docs/azure-data-studio/extensions/machine-learning-extension.md b/docs/azure-data-studio/extensions/machine-learning-extension.md
@@ -98,7 +98,7 @@ To use the Machine Learning extension in Azure Data Studio, follow the steps bel
 
 1. Open the **Connections** viewlet in Azure Data Studio.
 
-1. Right Select on your server and select **Manage**.
+1. Right-click on your server and select **Manage**.
 
 1. Select **Machine Learning** in the left side menu under **General**.
 
diff --git a/docs/azure-data-studio/extensions/schema-compare-extension.md b/docs/azure-data-studio/extensions/schema-compare-extension.md
@@ -38,7 +38,7 @@ The Schema Compare extension provides the following features:
 
 To install the Schema Compare extension, follow these steps: 
 
-1. In Azure Data Studio, Select the Extensions Icon to view available extensions.
+1. In Azure Data Studio, select the Extensions Icon to view available extensions.
 
     :::image type="content" source="media/schema-compare-extension/schema-compare-marketplace-search.png" alt-text="Screenshot of the Azure Data Studio GUI, marketplace search.":::
 
diff --git a/docs/connect/jdbc/using-bulk-copy-with-the-jdbc-driver.md b/docs/connect/jdbc/using-bulk-copy-with-the-jdbc-driver.md
@@ -599,7 +599,7 @@ public class BulkCopyExistingTransactions {
   
 3. For the Data Source, select the **Data source** that allows you to connect to your SQL Server (for example, SQL Server Native Client 11.0), check the configuration and then **Next**  
   
-4. For the Destination, Select the **Flat File Destination** and enter a **File Name** with a destination such as `C:\Test\TestBulkCSVExample.csv`. Check that the **Format** is Delimited, the **Text qualifier** is none, and enable **Column names in the first data row**, and then select **Next**  
+4. For the Destination, select the **Flat File Destination** and enter a **File Name** with a destination such as `C:\Test\TestBulkCSVExample.csv`. Check that the **Format** is Delimited, the **Text qualifier** is none, and enable **Column names in the first data row**, and then select **Next**  
   
 5. Select **Write a query to specify the data to transfer** and **Next**.  Enter your **SQL Statement** `SELECT ProductID, Name, ProductNumber FROM Production.Product`, and **Next**  
   
diff --git a/docs/integration-services/data-flow/odata-source-properties.md b/docs/integration-services/data-flow/odata-source-properties.md
@@ -26,7 +26,7 @@ When you right-click **OData Source** in the data flow and click **Properties**,
 |CollectionName|Name of the collection to retrieve from the OData service. The **CollectionName** property is used when **UseResourcePath** is False.<br /><br /> This property is expressionable, which lets you set the value at runtime. However, if the metadata of the collection does not match the metadata that existed at design time, a validation error occurs, causing the data flow execution to fail.|  
 |DefaultStringLength|This value specifies default length for string columns that have no max length.<br /><br /> **Default:** 4000|  
 |Query|The OData query parameters. This property is expressionable and can be set at runtime.|  
-|ResourcePath|Use this property when you need to specify a full resource path, rather than just selecting a collection name. This property is used when **UseResourcePath** is True.|  
+|ResourcePath|Use this property when you need to specify a full resource path, rather than selecting a collection name. This property is used when **UseResourcePath** is True.|  
 |UseResourcePath|When set to True, the **ResourcePath** value is appended to the base URL to determine the OData feed location. When set to False, the **CollectionName** value is used.<br /><br /> **Default:** False|  
   
 ## See Also
diff --git a/docs/relational-databases/performance/upgrade-dbcompat-using-qta.md b/docs/relational-databases/performance/upgrade-dbcompat-using-qta.md
@@ -85,7 +85,7 @@ QTA is a session-based feature that stores session state in the `msqta` schema o
 
 1. In [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] open the Object Explorer and connect to [!INCLUDE[ssDE](../../includes/ssde-md.md)].
 
-2. For the database that is intended to upgrade the database compatibility level, right-select the database name, select **Tasks**, select **Database Upgrade**, and select on **New Database Upgrade Session**.
+2. For the database that is intended to upgrade the database compatibility level, right-click the database name, select **Tasks**, select **Database Upgrade**, and select on **New Database Upgrade Session**.
 
 3. In the QTA Wizard window, two steps are required to configure a session:
 
@@ -117,7 +117,7 @@ QTA is a session-based feature that stores session state in the `msqta` schema o
 
 ### Executing the database upgrade workflow
 
-1. For the database that is intended to upgrade the database compatibility level, right-select the database name, select **Tasks**, select **Database Upgrade**, and select on **Monitor Sessions**.
+1. For the database that is intended to upgrade the database compatibility level, right-click the database name, select **Tasks**, select **Database Upgrade**, and select on **Monitor Sessions**.
 
 2. The **session management** page lists current and past sessions for the database in scope. Select the desired session, and select on **Details**.
 
diff --git a/docs/reporting-services/install-windows/install-reporting-services-native-mode-report-server.md b/docs/reporting-services/install-windows/install-reporting-services-native-mode-report-server.md
@@ -119,7 +119,7 @@ The following list describes the [!INCLUDE[ssRSnoversion](../../includes/ssrsnov
 
     - Install Rules
 
-2. On the **Setup Role** page, Select **SQL Server Feature Installation**.
+2. On the **Setup Role** page, select **SQL Server Feature Installation**.
 
     ![SQL Server Feature Installation for setup role](../../reporting-services/install-windows/media/rs-setuprole.png "SQL Server Feature Installation for setup role")
 
diff --git a/docs/reporting-services/lesson-3-defining-a-data-driven-subscription.md b/docs/reporting-services/lesson-3-defining-a-data-driven-subscription.md
@@ -41,7 +41,7 @@ This lesson assumes you completed Lesson 1 and Lesson 2 and that the report data
 6. Select **Apply**.
 
 ## Destination  
-1.  In the Destination section, Select **Windows File Share** for the method of delivery.  
+1.  In the Destination section, select **Windows File Share** for the method of delivery.  
 
 ## Dataset
 1. click **Edit Dataset**.
diff --git a/docs/reporting-services/report-server/configure-a-native-mode-report-server-for-local-administration-ssrs.md b/docs/reporting-services/report-server/configure-a-native-mode-report-server-for-local-administration-ssrs.md
@@ -114,7 +114,7 @@ ms.author: maggies
     >[!TIP]  
     >**Note:** If you do not see the **Site Settings** option, close and reopen your browser and browse to web portal with administrative privileges.  
   
-3.  On the Site settings page, Select **Security** and then select **Add group or user**.  
+3.  On the Site settings page, select **Security** and then select **Add group or user**.  
   
 4.  In the **Group or user name** field, type your Windows user account in this format: `<domain>\<user>`.  
 
diff --git a/docs/ssms/agent/configure-sql-server-agent.md b/docs/ssms/agent/configure-sql-server-agent.md
@@ -53,9 +53,9 @@ For more information about the Windows permissions required for the [!INCLUDE[ss
   
 ## To configure SQL Server Agent
 
-1. Select the **Start** button, and then, on the **Start**  menu, Select **Control Panel**.  
-2. In Control Panel, Select **System and Security**, Select **Administrative Tools**, and then select **Local Security Policy**.
-3. In Local Security Policy, Select the chevron to expand the **Local Policies** folder, and then Select the **User Rights Assignment** folder.
+1. Select the **Start** button, and then, on the **Start**  menu, select **Control Panel**.  
+2. In Control Panel, select **System and Security**, select **Administrative Tools**, and then select **Local Security Policy**.
+3. In Local Security Policy, select the chevron to expand the **Local Policies** folder, and then Select the **User Rights Assignment** folder.
 4. Right-click a permission that you want to configure for use with [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] and select **Properties**.
-5. In the permission's properties dialog box, verify that the account under which [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent runs is listed. If not, Select **Add User or Group**, enter the account under which [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent runs in the **Select Users, Computers, Service Accounts, or Groups** dialog box, and then Select **OK**.
-6. Repeat for each permission that you want to add to run with [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent. When finished, Select **OK**.
+5. In the permission's properties dialog box, verify that the account under which [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent runs is listed. If not, select **Add User or Group**, enter the account under which [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent runs in the **Select Users, Computers, Service Accounts, or Groups** dialog box, and then Select **OK**.
+6. Repeat for each permission that you want to add to run with [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent. When finished, select **OK**.
diff --git a/docs/ssms/f1-help/connect-to-any-sql-server-component-from-sql-server-management-studio.md b/docs/ssms/f1-help/connect-to-any-sql-server-component-from-sql-server-management-studio.md
@@ -46,7 +46,7 @@ When you register a server, Management Studio saves the connection information i
 
 ### Save connections in Solution Explorer
 
-Solution Explorer allows you to store related queries, scripts, connections, and other associated information in a project. Each script project contains a node called **Connections**, where you can save one or more connections. To add a connection, right-select **Connections**, and then select **New Connection**. To access a saved connection, expand **Connections** and double-select the connection Management Studio opens a query window associated with that connection. When saved, scripts retain their association to a specific connection.  
+Solution Explorer allows you to store related queries, scripts, connections, and other associated information in a project. Each script project contains a node called **Connections**, where you can save one or more connections. To add a connection, right-click **Connections**, and then select **New Connection**. To access a saved connection, expand **Connections** and double-select the connection Management Studio opens a query window associated with that connection. When saved, scripts retain their association to a specific connection.  
   
 ## See also
 
diff --git a/docs/ssms/scripting/generate-and-publish-scripts-wizard.md b/docs/ssms/scripting/generate-and-publish-scripts-wizard.md
@@ -228,7 +228,7 @@ This page summarizes the options that you have selected in this wizard. To chang
 
 Use this page to monitor the progress of the wizard as it occurs.
 
-**Details** - View the **Action** column to see the progress of the wizard. After generating the scripts, the wizard saves the scripts to a file or uses them to publish to a Web service, depending on your selections. When each of these steps is complete, Select the value in the **Result** column to see the outcome of the corresponding step.
+**Details** - View the **Action** column to see the progress of the wizard. After generating the scripts, the wizard saves the scripts to a file or uses them to publish to a Web service, depending on your selections. When each of these steps is complete, select the value in the **Result** column to see the outcome of the corresponding step.
 
 **Save Report** - Select to save the results of the wizard's progress to a file.
 
