Terminology updates

cds/Xrm Tooling/TPLCrmServiceClient/README.md

@@ -10,7 +10,7 @@ The [CrmServiceClient.Clone Method](https://docs.microsoft.com/dotnet/api/micros
 
 ## Demonstrates
 
-This simple sample will generate a number of account entity records using the [System.Threading.Tasks.Parallel.ForEach Method](https://docs.microsoft.com/dotnet/api/system.threading.tasks.parallel.foreach).
+This simple sample will generate a number of account table records using the [System.Threading.Tasks.Parallel.ForEach Method](https://docs.microsoft.com/dotnet/api/system.threading.tasks.parallel.foreach).
 
 Then it will use that technique again to delete the entities created.
 

cds/orgsvc/C#/ActivityPartyRecords/README.md

@@ -23,7 +23,7 @@ Creates three contact records which are required for this sample.
 
 1. Retrieves the contact records that are created in the [Setup](#Setup). 
 2. Creates the activity party records for each contact.
-3. Also creates Letter activity and set **From** and **To** fields to the respective Activity Party entities.
+3. Also creates Letter activity and set **From** and **To** columns to the respective Activity Party entities.
 
 ### Clean up
 

cds/orgsvc/C#/AssignChartToAnotherUser/README.md

@@ -15,7 +15,7 @@ See [How to run samples](https://github.com/microsoft/PowerApps-Samples/blob/mas
 
 ## What this sample does
 
-The [AssignRequest](https://docs.microsoft.com/dotnet/api/microsoft.crm.sdk.messages.assignrequest?view=dynamics-general-ce-9) message is intended to be used in a scenario where it contains the data that is needed to assign the specified record to a new owner (user or team) by changing the OwnerId attribute of the record.
+The [AssignRequest](https://docs.microsoft.com/dotnet/api/microsoft.crm.sdk.messages.assignrequest?view=dynamics-general-ce-9) message is intended to be used in a scenario where it contains the data that is needed to assign the specified record to a new owner (user or team) by changing the OwnerId column of the record.
 
 ## How this sample works
 
@@ -25,7 +25,7 @@ In order to simulate the scenario described in [What this sample does](#what-thi
 
 1. Checks for the current version of the org.
 2. The `CreateRequiredRecords` method creates a sample account and some opportunity records for the visualization.
-3. The `newUserOwnedVisualization` method creates the visualization entity instance.
+3. The `newUserOwnedVisualization` method creates the visualization table.
 
 ### Demonstrate
 

cds/orgsvc/C#/AssignUserOwnedDashboardToAnother/README.md

@@ -15,7 +15,7 @@ See [How to run samples](https://github.com/microsoft/PowerApps-Samples/blob/mas
 
 ## What this sample does
 
-The [AssignRequest](https://docs.microsoft.com/dotnet/api/microsoft.crm.sdk.messages.assignrequest?view=dynamics-general-ce-9) message is intended to be used in a scenario where it contains the data that is needed to assign the specified record to a new owner (user or team) by changing the OwnerId attribute of the record.
+The [AssignRequest](https://docs.microsoft.com/dotnet/api/microsoft.crm.sdk.messages.assignrequest?view=dynamics-general-ce-9) message is intended to be used in a scenario where it contains the data that is needed to assign the specified record to a new owner (user or team) by changing the OwnerId column of the record.
 
 ## How this sample works
 
@@ -24,7 +24,7 @@ In order to simulate the scenario described in [What this sample does](#what-thi
 ### Setup
 
 1. Checks for the current version of the org.
-2. The `CreateRequiredRecords` method creates entity records that this sample requires.
+2. The `CreateRequiredRecords` method creates table records that this sample requires.
 3. The `mySavedQuery` method grabs the default public view for the opportunities.
 4. The `visualizationQuery` method retrieves the visualizations out of the system. This sample assumes that you have the **Top opportunities**. 
 5. The `_otherUSerId` method creates the user to whom the dashboard will be assigned.

cds/orgsvc/C#/AssociateRecords/README.md

@@ -1,18 +1,18 @@
-# Associate and disassociate entities
+# Associate and disassociate tables
 
-This sample shows how to associate and disassociate entities using the [IOrganizationService.Associate](https://docs.microsoft.com/dotnet/api/microsoft.xrm.sdk.iorganizationservice.associate?view=dynamics-general-ce-9) and [IOrganization.Disassociate](https://docs.microsoft.com/dotnet/api/microsoft.xrm.sdk.iorganizationservice.disassociate?view=dynamics-general-ce-9) messages. 
+This sample shows how to associate and disassociate tables using the [IOrganizationService.Associate](https://docs.microsoft.com/dotnet/api/microsoft.xrm.sdk.iorganizationservice.associate?view=dynamics-general-ce-9) and [IOrganization.Disassociate](https://docs.microsoft.com/dotnet/api/microsoft.xrm.sdk.iorganizationservice.disassociate?view=dynamics-general-ce-9) messages. 
 
 ## How to run this sample
 
 See [How to run this sample](https://github.com/microsoft/PowerApps-Samples/blob/master/cds/README.md) for information about how to run this sample.
 
 ## What this sample does
 
-Entity records are associated to each other using lookup attributes on the related entity. The simplest way to associate two entity records in a one-to-many relationship is to use an EntityReference to set the value of a lookup attribute on the related entity.
+Table records are associated to each other using lookup columns on the related table. The simplest way to associate two table records in a one-to-many relationship is to use an `EntityReference` to set the value of a lookup columns on the related table.
 
-The simplest way to disassociate two entity records in a one-to-many relationship is to set the value of the lookup attribute to null.
+The simplest way to disassociate two table records in a one-to-many relationship is to set the value of the lookup columns to null.
 
-Relationships using an many-to-many relationship also depend on lookup attributes on the intersect entity that supports the many-to-many relationship. These relationship are defined by the existence of entity records in that intersect entity. While you can interact with the intersect entity directly, it is much easier to use the API to do this for you.
+Relationships using an many-to-many relationship also depend on lookup columns on the intersect table that supports the many-to-many relationship. These relationship are defined by the existence of table records in that intersect table. While you can interact with the intersect table directly, it is much easier to use the API to do this for you.
 
 ## How this sample works
 

cds/orgsvc/C#/AuditEntityData/README.md

@@ -5,20 +5,20 @@ products:
 - power-platform
 - power-apps
 page_type: sample
-description: "Sample that shows how to enable and disable auditing on an entity and its attributes in Microsoft Dataverse. [SOAP]"
+description: "Sample that shows how to enable and disable auditing on a table and its columns in Microsoft Dataverse. [SOAP]"
 ---
 
-# Audit entity data changes
+# Audit table data changes
 
-This sample shows how to enable and disable auditing on an entity and its attributes, retrieve the data change history of the audited entity, and delete the audit records.
+This sample shows how to enable and disable auditing on a table and its columns, retrieve the data change history of the audited table, and delete the audit records.
 
 ## How to run this sample
 
 See [How to run samples](https://github.com/microsoft/PowerApps-Samples/blob/master/cds/README.md) for information about how to run this sample.
 
 ## What this sample does
 
-The `RetrieveRecordChangeHistoryRequest` message is intended to be used in a scenario where it contains data that is needed to retrieve the audit history for an entity.
+The `RetrieveRecordChangeHistoryRequest` message is intended to be used in a scenario where it contains data that is needed to retrieve the audit history for a table.
 
 ## How this sample works
 
@@ -27,13 +27,13 @@ In order to simulate the scenario described in [What this sample does](#what-thi
 ### Setup
 
 1. Checks for the current version of the org.
-2. Creates an sample account entity.
+2. Creates an sample account table.
 
 ### Demonstrate
 
 1. Gets the organization's ID from the system user record.
-2. Enabling auditing on organization and also on the sample account entity.
-3. The `RetrieveRecordChangeHistoryRequest` retrieves the audit history for the account entity and displays the result.
+2. Enabling auditing on organization and also on the sample account table.
+3. The `RetrieveRecordChangeHistoryRequest` retrieves the audit history for the account table and displays the result.
 
 ### Clean up
 

cds/orgsvc/C#/AuditUserAccess/README.md

@@ -1,4 +1,4 @@
-# Audit User Access with PowerApps
+# Audit user access with Power Apps
 
 This sample code shows how to audit user access. 
 
@@ -8,7 +8,7 @@ See [How to run samples](https://github.com/microsoft/PowerApps-Samples/blob/mas
 
 ## What this sample does
 
-This sample first enables user access auditing with the logged on user's organization. Next, it creates and modifies an account entity so that audit records are generated.
+This sample first enables user access auditing with the logged on user's organization. Next, it creates and modifies an account table so that audit records are generated.
 
 ## How this sample works
 
@@ -17,13 +17,13 @@ In order to simulate the scenario described in [What this sample does](#what-thi
 ### Setup
 
 1. Checks for the current version of the org.
-1. Creates a new account entity and enables auditing on the new account entity.
+1. Creates a new account table and enables auditing on the new account table.
 
 ### Demonstrate
 
 1. Gets the organization's ID from the system user record and retrieves organization record.
 2. Enables auditing on the organization, including auditing for user access.
-3. Makes an update request ti the account entity to be tracked by auditing.
+3. Makes an update request ti the account table to be tracked by auditing.
 4. set the organization and account auditing flags back to old values and retrieve them if they were actually changed.
 
 ### Clean up

cds/orgsvc/C#/BulkEmail/README.md

@@ -1,7 +1,7 @@
 
 # Sample: Send bulk email and monitor results
 
-This sample shows how to send bulk email using the <xref:Microsoft.Crm.Sdk.Messages.SendBulkMailRequest> and monitor the results by retrieving records from the `AsyncOperation` entity.
+This sample shows how to send bulk email using the <xref:Microsoft.Crm.Sdk.Messages.SendBulkMailRequest> and monitor the results by retrieving records from the `AsyncOperation` table.
 
 ## How to run this sample
 

cds/orgsvc/C#/CRUDOperationsChart/README.md

@@ -22,13 +22,13 @@ In order to simulate the scenario described in [What this sample does](#what-thi
 ### Setup
 
 1. Checks for the current version of the org.
-1. The `CreateRequiredRecords` method creates entity records that is required for the sample.
+1. The `CreateRequiredRecords` method creates table records that is required for the sample.
 
 ### Demonstrate
 
 1. The `presentationXml` method sets the presentation XML string. 
 2. The `dataXml` method sets the data XML string.
-3. The `newUserOwnedVisualization` method creates the visualization entity instance.
+3. The `newUserOwnedVisualization` method creates the visualization table.
 4. The `retrievedOrgOwnedVisualization` method retrieves the visualization.
 5. The `newDataXml` method updates the name and the data description string.
 

cds/orgsvc/C#/Changetracking/README.md

@@ -1,6 +1,6 @@
 # Synchronize data with external systems using change tracking
 
-This sample code shows how to retrieve changes from an entity and synchronize data with external systems by using the `RetrieveEntityChanges` message with the [RetrieveEntityChangesRequest](https://docs.microsoft.com/dotnet/api/microsoft.xrm.sdk.messages.retrieveentitychangesrequest) and [RetrieveEntityChangesResponse](https://docs.microsoft.com/dotnet/api/microsoft.xrm.sdk.messages.retrieveentitychangesresponse) classes.
+This sample code shows how to retrieve changes from a table and synchronize data with external systems by using the `RetrieveEntityChanges` message with the [RetrieveEntityChangesRequest](https://docs.microsoft.com/dotnet/api/microsoft.xrm.sdk.messages.retrieveentitychangesrequest) and [RetrieveEntityChangesResponse](https://docs.microsoft.com/dotnet/api/microsoft.xrm.sdk.messages.retrieveentitychangesresponse) classes.
 
 For more information about the feature that this sample demonstrates, see [Use change tracking to synchronize data with external systems](https://docs.microsoft.com/powerapps/developer/common-data-service/use-change-tracking-synchronize-data-external-systems).
 <!-- The link above won't work until the topic is published -->
@@ -21,16 +21,16 @@ In order to simulate the scenario described in [What this sample does](#what-thi
 
 ### Setup
 
-1. Import a managed solution (ChangeTrackingSample_1_0_0_0_managed.zip) that creates a `sample_book` entity that has an alternate key named `sample_bookcode`. Verify that the indexes to support the alternate key are active
-1. 10 initial sample_book entity records are created so that changes to those entities can be tracked.
+1. Import a managed solution (ChangeTrackingSample_1_0_0_0_managed.zip) that creates a `sample_book` table that has an alternate key named `sample_bookcode`. Verify that the indexes to support the alternate key are active
+1. 10 initial sample_book table records are created so that changes to those entities can be tracked.
 
 ### Demonstrate
 
 1. Perform initial request and cache the results, including the `DataToken`
 1. Update the records created in [Setup](#setup)
 1. Perform a second request, this time passing the `DataVersion` with the `DataToken` value retrieved from the initial request.
-1. Show the entity changes returned by the second request
+1. Show the table changes returned by the second request
 
 ### Clean up
 
-Display an option to delete the managed solution imported in [Setup](#setup), which removes the `sample_book` entity and all the data created in the sample. The deletion is optional in case you want to examine the entities and data created by the sample. You can manually delete the `ChangeTrackingSample` to achieve the same result.
+Display an option to delete the managed solution imported in [Setup](#setup), which removes the `sample_book` table and all the data created in the sample. The deletion is optional in case you want to examine the entities and data created by the sample. You can manually delete the `ChangeTrackingSample` to achieve the same result.

cds/orgsvc/C#/ConnectionEarlyBound/README.md

@@ -1,6 +1,6 @@
 # Create a connection (early bound)
 
-This sample shows how to create a connection between an account and a contact entity that have matching connection roles.  
+This sample shows how to create a connection between an account and a contact table that have matching connection roles.  
 
 ## How to run this sample
 
@@ -16,13 +16,13 @@ In order to simulate the scenario described in [What this sample does](#what-thi
 
 ### Setup
 
-1. Creates a connection role for account and contact entity.
-2. Creates a related connection role object type code for account and contact entity.
+1. Creates a connection role for account and contact table.
+2. Creates a related connection role object type code for account and contact table.
 3. Associates the connection role with itself.
 
 ### Demonstrate
 
-1. Creates a connection between account and contact entity.
+1. Creates a connection between account and contact table.
 2. Assigns a connection role to a record.
 
 ### Clean up

cds/orgsvc/C#/ConnectionRole/README.md

@@ -21,8 +21,8 @@ Checks for the current version of the org.
 ### Demonstrate
 
 1. Defines some anonymous types to define the range of possible connection property values.
-2. Creates a connection role for account and contact entity.
-3. Creates a connection role object type code record for account and contact entity.
+2. Creates a connection role for account and contact table.
+3. Creates a connection role object type code record for account and contact table.
 
 ### Clean up
 

cds/orgsvc/C#/CreateEmailUsingTemplate/README.md

@@ -17,7 +17,7 @@ In order to simulate the scenario described in [What this sample does](#what-thi
 ### Setup
 
 1. Checks for the current version of the org.
-2. The `CreateRequiredRecords` method creates any entity records that this sample requires.
+2. The `CreateRequiredRecords` method creates any table records that this sample requires.
 
 ### Demonstrate
 

cds/orgsvc/C#/CreateRetrieveEntityRelationships/README.md

@@ -1,7 +1,7 @@
 
-# Create and retrieve entity relationships
+# Create and retrieve table relationships
 
-This sample shows how to create and retrieve entity relationships. The following methods are used to create and retrieve the relationships:
+This sample shows how to create and retrieve table relationships. The following methods are used to create and retrieve the relationships:
 
 - [CreateOneToManyRequest](https://docs.microsoft.com/dotnet/api/microsoft.xrm.sdk.messages.createonetomanyrequest?view=dynamics-general-ce-9)
 - [CreateManyToManyRequest](https://docs.microsoft.com/dotnet/api/microsoft.xrm.sdk.messages.createmanytomanyrequest?view=dynamics-general-ce-9)
@@ -16,7 +16,7 @@ See [How to run this sample](https://github.com/microsoft/PowerApps-Samples/blob
 
 ## What this sample does
 
-The `CreateOneToManyRequest`, `CreateManyToManyRequest`, `CanManyToManyRequest`, `CreateOneToManyRequest`, `CanBeReferencedRequest`, `CanBeReferencingRequest`, and `RetrieveRelationshipRequest` messages are intended to be used in a scenario where it contains the data that is needed to create and retrieve entity relationships.
+The `CreateOneToManyRequest`, `CreateManyToManyRequest`, `CanManyToManyRequest`, `CreateOneToManyRequest`, `CanBeReferencedRequest`, `CanBeReferencingRequest`, and `RetrieveRelationshipRequest` messages are intended to be used in a scenario where it contains the data that is needed to create and retrieve table relationships.
 
 ## How this sample works
 
@@ -31,7 +31,7 @@ Checks for the current version of the org.
 1. The `CreateOneToManyRequest` method creates a new One-to-Many (1:N) relationship. 
 2. The `CreateManyToManyRequest` method creates a new Many-To-Many (N:N) relationship.
 3. The `EligibleCreateManyToManyRelationship` method verifies whether entities can participate in N:N relationship.
-4. The `RetrieveRelationshipRequest` method retrieves the two entity relationships previously created.
+4. The `RetrieveRelationshipRequest` method retrieves the two table relationships previously created.
 
 
 ### Clean up

cds/orgsvc/C#/CreateUpdateEmailableEntity/README.md

@@ -1,14 +1,14 @@
-# Create an Email entity
+# Create an Email table
 
-This sample shows how to create and update an entity using the [CreateEntityRequest](https://docs.microsoft.com/dotnet/api/microsoft.xrm.sdk.messages.createentityrequest?view=dynamics-general-ce-9) message.
+This sample shows how to create and update a table using the [CreateEntityRequest](https://docs.microsoft.com/dotnet/api/microsoft.xrm.sdk.messages.createentityrequest?view=dynamics-general-ce-9) message.
 
 ## How to run this sample
 
 See [How to run samples](https://github.com/microsoft/PowerApps-Samples/blob/master/cds/README.md) for information about how to run this sample.
 
 ## What this sample does
 
-The `CreateEntityRequest` message is intended to be used in a scenario where it contains  the data that is needed to create a custom entity, and optionally, to add it to a specified unmanaged solution.
+The `CreateEntityRequest` message is intended to be used in a scenario where it contains  the data that is needed to create a custom table, and optionally, to add it to a specified unmanaged solution.
 
 ## How this sample works
 
@@ -20,10 +20,10 @@ Checks for the current version of the org.
 
 ### Demonstrate
 
-1. The `Entity` method creates the custom entity. Define the entity to enable for emailing. In order to do so, `IsActivityParty` must be set to true.
-2. The `StringAttributeMetadata` method is used to define the primary attribute of the entity which is used in the ActivityParty screens. Be sure to select descriptive attributes.
+1. The `CreateEntityRequest` method creates the custom table. Define the table to enable for emailing. In order to do so, `IsActivityParty` must be set to true.
+2. The `StringAttributeMetadata` method is used to define the primary column of the table which is used in the ActivityParty screens. Be sure to select descriptive columns.
 3. The `PublishRequest` method publishes all the customizations.
-4. The `CreateFirstEmailAttributeRequest` method creates an email attribute in order to create emails from the entity.
+4. The `CreateFirstEmailAttributeRequest` method creates an email column in order to create emails from the table.
 
 ### Clean up