Merge pull request #32640 from rwestMSFT/rw-1216-fix-pronouns

[SCOPED] Correct pronoun usage

Author: v-dirichards

docs/ado/guide/remote-data-service/running-the-address-book-sample-application.md

@@ -30,7 +30,7 @@ helpviewer_keywords:
 
      where *webserver* is the name of the Web server where the RDS server components are installed.  
 
-3.  You can then try various scenarios in the Address Book sample application, such as searching for a person based on his or her e-mail name, listing all people with the title "Program Manager," or editing existing records. Click **Find** to fill the data grid with all the available names.  
+3.  You can then try various scenarios in the Address Book sample application, such as searching for a person based on their e-mail name, listing all people with the title "Program Manager," or editing existing records. Click **Find** to fill the data grid with all the available names.  
 
 ## See Also  
  [Address Book Data-Binding Object](./address-book-data-binding-object.md)

docs/ado/reference/ado-api/updatebatch-and-cancelbatch-methods-example-vb.md

@@ -46,7 +46,7 @@ Public Sub Main()
     rstTitles.Open strSQLTitles, Cnxn, adOpenKeyset, adLockBatchOptimistic, adCmdTable  
   
     rstTitles.MoveFirst  
-    ' Loop through recordset and ask user if she wants  
+    ' Loop through recordset and ask user if they want  
     ' to change the type for a specified title.  
     Do Until rstTitles.EOF  
         If Trim(rstTitles!Type) = "psychology" Then  
@@ -62,7 +62,7 @@ Public Sub Main()
         rstTitles.MoveNext  
     Loop  
   
-    ' Ask the user if she wants to commit to all the  
+    ' Ask the user if they want to commit to all the  
     ' changes made above.  
     If MsgBox("Save all changes?", vbYesNo) = vbYes Then  
         rstTitles.UpdateBatch  

docs/ado/reference/ado-api/updatebatch-and-cancelbatch-methods-example-vc.md

@@ -86,7 +86,7 @@ void UpdateBatchX() {
       TESTHR(picRs->BindToRecordset(&titlers));  
       pRstTitles->MoveFirst();  
   
-      // Loop through recordset and ask user if she wants,  
+      // Loop through recordset and ask user if they want  
       // to change the type for a specified title.  
       while (!(pRstTitles->EndOfFile)) {  
          // Compare type with psychology  

docs/analytics-platform-system/workload-management.md

@@ -101,7 +101,7 @@ For each login, the resource class settings are applied to individual statements
 
 Before SQL Server PDW runs a statement, it tries to acquire the concurrency slots needed for the request. If it cannot acquire enough concurrency slots, SQL Server PDW moves the request into a waiting-to-be-executed state. All resources system that were already allocated to the request are returned back to the system.  
 
-Most of the SQL statements always need the default resource allocations, and therefore are not controlled by resource classes. For example, CREATE LOGIN only needs a small amount of resources, and is allocated the default resources even if the login calling CREATE LOGIN is a member of a resource class.  For example, if Anna is a member of the largerc resource class and she submits a CREATE LOGIN statement, the CREATE LOGIN statement will run with the default number of resources.  
+Most of the SQL statements always need the default resource allocations, and therefore are not controlled by resource classes. For example, CREATE LOGIN only needs a small amount of resources, and is allocated the default resources even if the login calling CREATE LOGIN is a member of a resource class.  For example, if Anna is a member of the largerc resource class and submits a CREATE LOGIN statement, the CREATE LOGIN statement will run with the default number of resources.  
 
 SQL statements and operations governed by resource classes:  
 

docs/data-quality-services/data-cleansing.md

@@ -70,7 +70,7 @@ ms.topic: conceptual
 > [!NOTE]  
 >  In the **Suggested**, **Corrected**, and **Correct** tabs, DQS displays the leading value for a domain, if applicable, in the **Correct To** column against the respective domain value.  
   
- The data steward uses [!INCLUDE[ssDQSClient](../includes/ssdqsclient-md.md)] to see the changes that DQS has proposed and to decide whether to implement them or not. He or she can verify that values DQS has designated as correct are in fact correct. He or she can verify that changes already made by DQS, with a high confidence level, should be made. He or she can decide whether to approve auto-suggested changes. And he or she can review values that have not been changed, just in case they want to make a change not found by the computer-assisted process.  
+ The data steward uses [!INCLUDE[ssDQSClient](../includes/ssdqsclient-md.md)] to see the changes that DQS has proposed and to decide whether to implement them or not. They can verify that the values DQS has designated as correct are in fact correct. They can verify that changes already made by DQS, with a high confidence level, should be made. The steward can decide whether to approve auto-suggested changes. And they can review values that have not been changed, just in case they want to make a change not found by the computer-assisted process.  
 
  DQS will merge any changes that the data steward has made with the results of the computer-assisted data cleansing. These changes will stay with the project; however, they will not be added to the knowledge base. During data cleansing, the associated knowledge base is read-only.  
 

docs/data-quality-services/manage-a-knowledge-base.md

@@ -58,7 +58,7 @@ ms.topic: conceptual
 
         6.  **Locked Date**: date when locked  
 
-        7.  **Created By**: the name of the user who created the knowledge base, with the network that he or she belongs to  
+        7.  **Created By**: the name of the user who created the knowledge base, with the network that they belong to  
 
         8.  **Created Date**: date when created  
 

docs/database-engine/availability-groups/windows/failover-clustering-and-always-on-availability-groups-sql-server.md

@@ -81,9 +81,9 @@ monikerRange: ">=sql-server-2016"
 
  The following example scenario illustrates how this configuration could lead to problems:  
 
- Marcel configures a WSFC with two nodes, `NODE01` and `NODE02`. He installs a [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] failover cluster instance, `fciInstance1`, on both `NODE01` and `NODE02` where `NODE01` is the current owner for `fciInstance1`.  
- On `NODE02`, Marcel installs another instance of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)], `Instance3`, which is a stand-alone instance.  
- On `NODE01`, Marcel enables fciInstance1 for [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)]. On `NODE02`, he enables `Instance3` for [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)]. Then he sets up an availability group for which `fciInstance1` hosts the primary replica, and `Instance3` hosts the secondary replica.  
+ You configure a WSFC with two nodes, `NODE01` and `NODE02`. You install a [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] failover cluster instance, `fciInstance1`, on both `NODE01` and `NODE02` where `NODE01` is the current owner for `fciInstance1`.  
+ On `NODE02`, you install another instance of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)], `Instance3`, which is a stand-alone instance.  
+ On `NODE01`, you enable fciInstance1 for [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)]. On `NODE02`, you enable `Instance3` for [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)]. Then you set up an availability group for which `fciInstance1` hosts the primary replica, and `Instance3` hosts the secondary replica.  
  At some point `fciInstance1` becomes unavailable on `NODE01`, and the WSFC causes a failover of `fciInstance1` to `NODE02`. After the failover, `fciInstance1` is a [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)]-enabled instance running under the primary role on `NODE02`. However, `Instance3` now resides on the same WSFC node as `fciInstance1`. This violates the [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)] constraint.  
  To correct the problem that this scenario presents, the stand-alone instance, `Instance3`, must reside on another node in the same WSFC as `NODE01` and `NODE02`.  
 

docs/integration-services/data-flow/use-a-recordset-destination.md

@@ -53,7 +53,7 @@ helpviewer_keywords:
 8.  Inside the Foreach Loop container, add and configure tasks to process one row of the recordset at a time by reading the values from the variables.  
 
 ## Example of Using the Recordset Destination  
- In the following example, the Data Flow task loads information about [!INCLUDE[ssSampleDBnormal](../../includes/sssampledbnormal-md.md)] employees from the Sales.SalesPerson table into a Recordset destination. Then, a Foreach Loop container reads one row of data at a time, and calls a Send Mail task. The Send Mail task uses expressions to send a customized e-mail message to each salesperson about the amount of his or her bonus.  
+ In the following example, the Data Flow task loads information about [!INCLUDE[ssSampleDBnormal](../../includes/sssampledbnormal-md.md)] employees from the Sales.SalesPerson table into a Recordset destination. Then, a Foreach Loop container reads one row of data at a time, and calls a Send Mail task. The Send Mail task uses expressions to send a customized e-mail message to each salesperson about the amount of their bonus.  
 
 #### To create the project and configure the variables  
 

docs/master-data-services/microsoft-excel-add-in/overview-importing-data-from-excel-mds-add-in-for-excel.md

@@ -21,7 +21,7 @@ ms.custom: microsoft-excel-add-in
 >  Publishing cannot be used to create a new entity. For more information about creating entities, see [Create an Entity (MDS Add-in for Excel)](../../master-data-services/microsoft-excel-add-in/create-an-entity-mds-add-in-for-excel.md).  
   
 ## When Multiple Users Publish at the Same Time  
- Multiple users can publish updates to the same data. As each user publishes, the update is saved to the database. This means that a user who was not working with the most recently-updated data can still change the value when he or she publishes.  
+ Multiple users can publish updates to the same data. As each user publishes, the update is saved to the database. This means that a user who was not working with the most recently-updated data can still change the value when they publish.  
 
  Only the updates you make are published to the database. Any out-of-date data in the worksheet is not published.  
 

docs/master-data-services/what-s-new-in-master-data-services-mds.md

@@ -68,7 +68,7 @@ monikerRange: ">=sql-server-ver16"
   
  The new Super User function permission gives a user or group the same permissions as the Server Admin in the previous release of [!INCLUDE[ssMDSshort](../includes/ssmdsshort-md.md)]. The Super User permission can be assigned to multiple users and groups. In the previous release, the user who originally installed [!INCLUDE[ssMDSshort](../includes/ssmdsshort-md.md)] was the server admin, and it was difficult to transfer this permission to another user or a group. For more information, see [Functional Area Permissions (Master Data Services)](../master-data-services/functional-area-permissions-master-data-services.md).  
   
- A user can now explicitly be assigned the Admin permission at the model level. This means that if the user is assigned permissions in the model subtree, such as the entity level, he still has this Admin permission.
+ A user can now explicitly be assigned the Admin permission at the model level. This means that if the user is assigned permissions in the model subtree, such as the entity level, they still have this Admin permission.
   
  In this release of [!INCLUDE[ssMDSshort](../includes/ssmdsshort-md.md)], we're providing more levels of permissions by introducing the following new permissions: Read, Create, Update, and Delete. For example, a user that has only the Update permission can now update the master data without creating or deleting the data. When you give a user the Create, Update or Delete permission, the user is automatically assigned the Read permission. You can also combine the Read, Create, Update, and Delete permissions.