Merge branch 'master' into pehecke-migrate-orgservice

Author: phecke

powerapps-docs/developer/common-data-service/use-source-control-solution-files.md

@@ -24,7 +24,7 @@ The SolutionPackager tool can be used with any source control system. After a so
  As further customizations and changes are necessary for the solution, developers should edit or customize components through existing means, export again to create a .zip file, and extract the compressed solution file into the same folder.  
 
 > [!IMPORTANT]
->  Except for the sections described in [When to edit the customizations file](/model-driven-apps/when-edit-customization-file.md), manual editing of extracted component files and .zip files is not supported.  
+>  Except for the sections described in [When to edit the customizations file](../model-driven-apps/when-edit-customization-file.md), manual editing of extracted component files and .zip files is not supported.  
   
  When the SolutionPackager tool extracts the component files it will not overwrite existing component files of the same name if the file contents are identical. In addition, the tool honors the read-only attribute on component files producing a warning in the console window that particular files were not written. This enables the user to check out, from source control, the minimal set of files that are changing. The `/clobber` parameter can be used to override and cause read-only files to be written or deleted. The `/allowWrite` parameter can be used to assess what impact an extract operation has without actually causing any files to be written or deleted. Use of the `/allowWrite` parameter with verbose logging is effective.  
 

powerapps-docs/developer/component-framework/create-custom-controls-using-pcf.md

@@ -114,11 +114,11 @@ You can also interact with the component locally in real time and observe elemen
 
 ## Deploying your PowerApps component framework components
 
-Once the debugging and development is finished, you just have one step remaining - to deploy your new component.  
+Once the debugging and development is finished, you just have one step remaining to deploy your new component.  
 
 Follow the steps below to create and import a [solution](https://docs.microsoft.com/en-us/dynamics365/customer-engagement/customize/solutions-overview) file:
 
-1. Create a new directory and go to it 'cd <new directory name>'
+1. Create a new directory and go to it `cd <new directory name>`
 2. Create a new solution project in the directory of your choice by using the command 
  `pac solution init --publisherName <enter your publisher name> --customizationPrefix <enter your publisher name>` after `cd <your new folder>`.
 

powerapps-docs/developer/component-framework/manifest-schema-reference/property.md

@@ -25,7 +25,7 @@ ms.assetid: 45f4872d-c1d2-4c5a-8721-251b96ede370
 |`name`|Name of the property|`string`|Yes|
 |`display-name-key`|Used in the customization screens as localized strings that describes the name of the property.|`string`|Yes|
 |`of-type`|Defines the data type of the property|See [Remarks](#remarks)|Optional|
-|`usage`|The usage attribute identifies if the property is meant to represent an entity attribute that the component can change (bound) or read-only values (input)|`bound`,`input` or `output`|Optional|
+|`usage`|The usage attribute identifies if the property is meant to represent an entity attribute that the component can change (bound) or read-only values (input)|`bound` or `input`|Optional|
 |`required`|Whether the property is required or not|`boolean`|Optional|
 |`of-type-group`|Name of the type-group as defined in manifest|`string`|Optional|
 |`description-key`|Used in the customization screens as localized strings that describes the description of the property.|`string`|Optional|

powerapps-docs/maker/common-data-service/solution-layers.md

@@ -2,7 +2,7 @@
 title: "View solution layers | MicrosoftDocs"
 description: "Learn how you can use solution layers"
 keywords: 
-ms.date: 04/10/2019
+ms.date: 04/18/2019
 ms.service: powerapps
 ms.custom: 
 ms.topic: article
@@ -26,36 +26,40 @@ search.app:
   - D365CE
 ---
 
+<!--note from editor: Best practice is that H1 title and title in metadata are different.    -->
+
 # View solution layers
-Solution layers allows you to view all component changes that occur due to solution changes over time. Within a solution layer, you can drill-down to view the specific changed and unchanged property details for a component. 
+Solution layers allow you to view all component changes that occur due to solution changes over time. Within a solution layer, you can drill down to view specific changed and unchanged property details for a component. 
 
-Solution layers provide the following benefits: 
--	Let’s you see the order in which a solution changed a component. 
--	Let’s you view all properties of a component within a specific solution including the changes to the component. 
--	Can be used to troubleshoot dependency or solution layering issues by displaying change details for a component that was introduced by a solution change.
+Solution layers: 
+-	Let you see the order in which a solution changed a component. 
+-	Let you view all properties of a component within a specific solution, including the changes to the component. 
+-	Can be used to troubleshoot dependency or solution-layering issues by displaying change details for a component that was introduced by a solution change.
 
 ## View the solution layers for a component
 You can access solution layers from the **Components** list or from the **Dependency Details** dialog box in solution explorer. 
 
-1. To view solution layers from the **Components** list, [open solution explorer](../model-driven-apps/advanced-navigation.md#solution-explorer), in the **Components** list select a component, such as **Account**, and then select **Solution Layers** on the toolbar. 
+<!--note from editor: In step 2 below, does the page display a name at top? If so, use the same capitalization in text. -->
+
+1. To view solution layers from the **Components** list, open [solution explorer](../model-driven-apps/advanced-navigation.md#solution-explorer). In the **Components** list, select a component, such as **Account**, and then select **Solution Layers** on the toolbar. 
 
    > [!div class="mx-imgBorder"] 
-   > ![](media/solution-layers-toolbar.png "Solution layers button")
+   > ![Solution layers button](media/solution-layers-toolbar.png "Solution layers button")
 
-2. The solution layer page appears that displays each layer for the component, such as the account entity displayed here, with the most recent layer at the top. To view the details for a solution layer, select it. 
+2. The solution layer page appears. It displays each layer for the component, such as the **Account** entity displayed here, with the most recent layer at the top. To view the details for a solution layer, select it. 
 
    > [!div class="mx-imgBorder"] 
-   > ![](media/solution-layers-list.png "Solution layers list")
+   > ![Solution layers list](media/solution-layers-list.png "Solution layers list")
 
-3. On the **Solution Layer** dialog box, the **Changed Properties** tab displays only those properties that were modified as part of the specific solution layer. 
+3. In the **Solution Layer** dialog box, the **Changed Properties** tab displays only those properties that were modified as part of the specific solution layer. 
 
    > [!div class="mx-imgBorder"] 
-   > ![](media/solution-layers-change-prop.png "Solution layer changed properties")
+   > ![Solution layer changed properties](media/solution-layers-change-prop.png "Solution layer changed properties")
 
 4. Select the **All Properties** tab to view all properties, including changed and unchanged properties, for the solution layer. 
 
    > [!div class="mx-imgBorder"] 
-   > ![](media/solution-layers-all-prop.png "Solution layer all properties")
+   > ![Solution layer all properties](media/solution-layers-all-prop.png "Solution layer all properties")
 
-## See also
-[Solutions overview](solutions-overview.md)
+### See also
+[Solutions overview](solutions-overview.md)