Merge branch 'master' into master-jdaly-2019-4-26

Author: JimDaly

powerapps-docs/developer/common-data-service/TOC.yml

@@ -79,7 +79,7 @@
       href: write-plug-in.md
     - name: Handle exceptions
       href: handle-exceptions.md
-    - name: Inpersonate a user
+    - name: Impersonate a user
       href: impersonate-a-user.md
     - name: Register a plug-in
       href: register-plug-in.md

powerapps-docs/developer/common-data-service/webapi/web-api-types-operations.md

@@ -2,7 +2,7 @@
 title: "Web API types and operations (Common Data Service)| Microsoft Docs"
 description: "This topic describes what is available for you to use vis-a-vis the Web API and will introduce important topics and how you can find information you need from the documentation generated from the service and metadata documents as well as the documentation of the system entity types, functions, and actions"
 ms.custom: ""
-ms.date: 04/22/2019
+ms.date: 04/30/2019
 ms.service: powerapps
 ms.suite: ""
 ms.tgt_pltfrm: ""
@@ -267,7 +267,7 @@ OData supports a wide range of data types but Common Data Service doesn’t use
 
 ### Lookup properties
 
-For most single-valued navigation properties you will find a computed, read-only property that uses the following naming convention: `_<name>_value` where the `<name>` matches the name of the single-valued navigation property. The exception to this pattern is when a lookup attribute of the entity can accept multiple types of entity references. A common example is how the `incident` entity `customerid` attribute may be set to a reference that is either a `contact` or `account` entity. In the <xref href="Microsoft.Dynamics.CRM.incident?text=incident EntityType" /> [Single-valued navigation properties](/dynamics365/customer-engagement/web-api/incident?view=dynamics-ce-odata-9#Single-valued_navigation_properties) you will find `customerid_account` and `customerid_contact` as separate single-valued navigation properties to reflect the customer associated with an opportunity. If you set one of these single-valued navigation properties, the other will be set to null because they are both bound to the `customerid` attribute. In the [<xref href="Microsoft.Dynamics.CRM.incident?text=incident EntityType" /> [Properties](/dynamics365/customer-engagement/web-api/incident?view=dynamics-ce-odata-9#Properties) you’ll find a `_customerid_value` lookup property that contains the same value that is set for whichever of the single-valued navigation properties contain a value.  
+For most single-valued navigation properties you will find a computed, read-only property that uses the following naming convention: `_<name>_value` where the `<name>` matches the name of the single-valued navigation property. The exception to this pattern is when a lookup attribute of the entity can accept multiple types of entity references. A common example is how the `incident` entity `customerid` attribute may be set to a reference that is either a `contact` or `account` entity. In the <xref href="Microsoft.Dynamics.CRM.incident?text=incident EntityType" /> [Single-valued navigation properties](/dynamics365/customer-engagement/web-api/incident?view=dynamics-ce-odata-9#Single-valued_navigation_properties) you will find `customerid_account` and `customerid_contact` as separate single-valued navigation properties to reflect the customer associated with an opportunity. If you set one of these single-valued navigation properties, the other will be set to null because they are both bound to the `customerid` attribute. In the <xref href="Microsoft.Dynamics.CRM.incident?text=incident EntityType" /> [Properties](/dynamics365/customer-engagement/web-api/incident?view=dynamics-ce-odata-9#Properties) you’ll find a `_customerid_value` lookup property that contains the same value that is set for whichever of the single-valued navigation properties contain a value.  
 
 Generally, you should avoid using lookup properties and use the corresponding single-valued navigation properties instead. These properties have been included because they may be useful for certain integration scenarios. These properties are read-only and computed because they will simply reflect the changes applied using the corresponding single-valued navigation property.  
 

powerapps-docs/developer/component-framework/updating-existing-controls.md

@@ -11,7 +11,7 @@ ms.tgt_pltfrm: ""
 ms.topic: "article"
 ms.assetid: d2cbf58a-9112-45c2-b823-2c07a310714c
 ---
-# Updating existing custom controls 
+# Updating existing custom components 
 
 [!INCLUDE[cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)]
 

powerapps-docs/maker/canvas-apps/limits-and-config.md

@@ -89,10 +89,10 @@ This list identifies all services to which PowerApps Studio talks and their usag
 | login.microsoft.com<br>login.windows.net<br>login.microsoftonline.com<br>secure.aadcdn.microsoftonline-p.com |https |ADAL |
 | graph.microsoft.com<br>graph.windows.net |https |Azure Graph - For getting user info (e.g. profile photo) |
 | gallery.azure.com |https |Sample and Template apps |
-| *.azure-apim.net |https |Api Hubs - Different sub-domains for each locale |
-| *.powerapps.com |https |WebAuth + Portal |
-| *.azureedge.net |https |WebAuth |
-| *.blob.core.windows.net |https |Blob storage |
+| \*.azure-apim.net |https |Api Hubs - Different sub-domains for each locale |
+| \*.powerapps.com |https |WebAuth + Portal |
+| \*.azureedge.net |https |WebAuth |
+| \*.blob.core.windows.net |https |Blob storage |
 | vortex.data.microsoft.com |https |Telemetry |
 
 > [!NOTE]