Incorp tech review feedback

Author: phecke

powerapps-docs/developer/common-data-service/security-access-coding.md

@@ -15,6 +15,7 @@ search.app:
   - PowerApps
   - D365CE
 ---
+
 # Verifying access in code
 
 [!INCLUDE[cc-data-platform-banner](../../includes/cc-data-platform-banner.md)]
@@ -54,7 +55,7 @@ new record. Testing whether the user can create a new record requires using the
 other strategy (mentioned above) to check the user’s security privileges.
 
 However, if the user was successful in retrieving entity records using a query, you
-can then test an entity instance using <xref:Microsoft.Crm.Sdk.Messages.RetrievePrincipalAccessRequest>.
+can then test an entity instance using the `RetrievePrincipalAccess` message (<xref:Microsoft.Dynamics.CRM.RetrievePrincipalAccess>, <xref:Microsoft.Crm.Sdk.Messages.RetrievePrincipalAccessRequest>).
 
 The following sample method uses the .NET SDK assemblies to allow retrieving a
 set of access rights defined within the [AccessRights Enum](/dotnet/api/microsoft.crm.sdk.messages.accessrights).
@@ -71,8 +72,6 @@ set of access rights defined within the [AccessRights Enum](/dotnet/api/microsof
 static AccessRights GetAccessRights(IOrganizationService svc, EntityReference
 user, EntityReference entity) {
 
-// TODO Consider adding a test for the user being a system user or part of a team.
-
   try
   {
     var accessRightsRequest = new RetrievePrincipalAccessRequest() 
@@ -124,7 +123,7 @@ those access rights on a record using the <xref:Microsoft.Crm.Sdk.Messages.Retri
 
 When you don’t have a specific entity record to test, such as whether they can
 create a new entity record, you must rely on checking the user’s security
-privileges. These privileges are stored in the [Privilege entity](reference/entities/privilege).
+privileges. These privileges are stored in the [Privilege entity](reference/entities/privilege.md).
 
 There are nearly one thousand individual privileges in the Dataverse database and the
 number will grow with every entity or custom action that is added to the system.

powerapps-docs/developer/common-data-service/security-concepts.md

@@ -1,5 +1,5 @@
 ---
-title: "Security concepts (Microsoft Dataverse) | Microsoft Docs" 
+title: "Security concepts for developers (Microsoft Dataverse) | Microsoft Docs" 
 description: "A brief summary of security concepts." 
 ms.custom: ""
 ms.date: 12/10/2020
@@ -15,7 +15,7 @@ search.app:
   - PowerApps
   - D365CE
 ---
-# Security concepts
+# Security concepts for developers
 
 [!INCLUDE[cc-data-platform-banner](../../includes/cc-data-platform-banner.md)]
 

powerapps-docs/developer/common-data-service/security-model.md

@@ -34,6 +34,3 @@ As a developer, you should know that the data operations in your code run in the
 The first step is to understand the security concepts that apply to data access. You should understand how to configure and manage security roles because you will need to apply them when you test your code. But this is beyond the scope of this topic.  You can find more information about security concepts in general and security configuration tasks in [Security concepts in Microsoft Dataverse](/power-platform/admin/wp-security-cds).
 
 In the security related topics that follow, we will assume that you have have a basic understanding of Microsoft Dataverse security concepts and administration so that we can proceed with addressing the security and data access APIs that you will need to use in your plug-in or application.
-
-### See Also
-

powerapps-docs/developer/common-data-service/security-sharing-assigning.md

@@ -79,4 +79,4 @@ operation. If **Share reassigned records with original owner** is selected (se
 shares the record with all access rights after the assign operation. Otherwise,
 the previous owner does not share the record and may not have access to the
 record, depending on his or her privileges. The Organization entity's
-[ShareToPreviousOwnerOnAssign](reference/entities/organization#sharetopreviousowneronassign-options) attribute controls this setting.
+[ShareToPreviousOwnerOnAssign](reference/entities/organization.md#sharetopreviousowneronassign-options) attribute controls this setting.