Live publish for 22 January 2020.

Author: buck1ey

powerapps-docs/developer/common-data-service/media/system-jobs-more-actions-commands.png

@@ -72,7 +72,7 @@ You can view information about registered assemblies in the application solution
 
 ![All Solutions internal](media/all-solutions-internal-view.png)
 
-There you can find all the assemblies that are registered for this environment.
+After selecting the name of the Default Solution in the internal solution list, you can find all the assemblies that are registered for this environment.
 
 ![View all registered assemblies](media/view-plug-in-assemblies-default-solution.png)
 
@@ -129,7 +129,7 @@ More information: [Use FetchXML with FetchExpression](org-service/entity-operati
 
 As described in [View registered assemblies](#view-registered-assemblies), the assembly registration you created was added to the system **Default Solution**. You should add your assembly to an unmanaged solution so you can distribute it to other organizations.
 
-Within the unmanaged solution you are using, use solution explorer to navigate to **Plug-in Assemblies**. In the list menu, select **Add Existing**.
+Within the unmanaged solution you are using, use solution explorer to navigate to **Plug-in Assemblies**. In the list menu, select **Add Existing**. Note that in the following figures, a custom solution named Common Data Service Default Solution is used.
 
 ![Add Existing plug-in assembly](media/add-existing-plug-in-assembly.png)
 
@@ -289,7 +289,7 @@ The PRT provides commands to unregister assemblies, types, steps, and images. Se
 
 These are delete operations on the [PluginAssembly](reference/entities/pluginassembly.md), [PluginType](reference/entities/plugintype.md), [SdkMessageProcessingStep](reference/entities/sdkmessageprocessingstep.md), and [SdkMessageProcessingStepImage](reference/entities/sdkmessageprocessingstepimage.md) entities.
 
-You can also delete **Plug-in Assemblies** and **Sdk Message Processing Steps** in the solution explorer to achieve the same result.
+You can also delete **Plug-in Assemblies** and **Sdk Message Processing Steps** in the solution explorer to achieve the same result. In the figure below, a custom solution named Common Data Service Default Solution is shown.
 
 ![Deleting step in solution explorer](media/delete-sdk-message-processing-step.png)
 

powerapps-docs/developer/common-data-service/register-plug-in.md

@@ -23,7 +23,7 @@ The Discovery Service APIs can be used by your application to discover business
 A detailed description of using the Discovery Service with the RESTful API can be found on the [Discover the URL for your organization](/powerapps/developer/common-data-service/webapi/discover-url-organization-web-api) page.
 
 > [!IMPORTANT]
-> When accessing the Discovery Service, it is strongly recommended that your application use the *global* Discovery Service endpoint (https://globaldisco.crm.dynamics.com) and not the *regional* Discovery Service endpoint, which is [deprecated](/power-platform/important-changes-coming#regional-discovery-service-is-deprecated). The global Discovery Service is only available when using the RESTful API.
+> When accessing the Discovery Service, it is strongly recommended that your application use the *global* Discovery Service endpoint (https://globaldisco.crm.dynamics.com) and not the *regional* Discovery Service endpoint, which will be [deprecated](/power-platform/important-changes-coming#regional-discovery-service-is-deprecated) on March 2, 2020. The global Discovery Service is only available when using the RESTful API.
 
 The rest of this document describes the changes that may be needed to call the Discovery Service using the RESTful API.
 

powerapps-docs/developer/common-data-service/webapi/discovery-orgsdk-to-webapi.md

@@ -41,6 +41,7 @@ The following is the list of blogs created by Power Apps community.
 - [Create code components](https://debajmecrm.com/2019/04/26/in-depth-end-end-walkthrough-develop-your-custom-controls-using-power-apps-component-framework-and-use-it-on-your-crm-interface/)
 - [Editing the DOM with supported code components](https://www.magnetismsolutions.com/blog/adammurchison/2019/05/29/editing-the-dom-with-supported-dynamics-365-custom-controls)
 - [How to configure Node.js and Typescript into your environment](https://capuanodanilo.com/2019/06/11/how-to-configure-node-js-and-typescript-into-your-environment-to-develop-powerapps-component-frameworks-pcf)
+- [Localization of code components](https://dynamicsninja.blog/2020/01/21/pcf-localization)
 - [Power Apps component framework – Frosting on the Cake](https://stevemordue.com/powerapps-component-framework-frosting-on-the-cake/)
 - [Public availability of Power Apps component framework – An important milestone](https://crmindian.com/2019/04/24/public-availability-of-powerapps-component-framework-an-important-milestone-for-powerapps-and-d365/)
 - [Work with code components using Power Apps component framework](https://powermaverick.dev/2019/05/18/create-custom-controls-using-powerapp-component-framework)
@@ -54,6 +55,7 @@ The following is the list of videos created by Power Apps community.
 - [Easier debugging with sourcemaps and Fiddler](https://www.youtube.com/watch?v=Ov-m5FBUj9g&feature=youtu.be)
 - [Getting started with code components](https://www.youtube.com/watch?v=ylhVZUlGgQw)
 - [Power Apps component framework Academy: Getting started](https://www.youtube.com/watch?v=YJ9hrKxAhTU)  
+- [Power Apps component framework: Deep dive manifest file for dataset template](https://www.youtube.com/watch?v=TsTrYaOGaGo&feature=youtu.be)
 - [Power Apps component framework Academy: Deep dive manifest file for field template](https://www.youtube.com/watch?time_continue=522&v=w40zqSsYEy0)
 - [Power Apps component framework Academy: Dataset components](https://www.youtube.com/watch?v=OEiM97nTD0w)
 - [Power Apps component framework Academy: Importing into your organization](https://www.youtube.com/watch?v=2uO2L2xTPkc)

powerapps-docs/developer/component-framework/community-resources.md

@@ -55,14 +55,14 @@ This table lists some common commands used in the CLI
 |**pcf**|Commands for working with Power Apps component framework. It has the following parameters: <br/> - **init**: Initializes the code component project. It has the following parameters <br/> - *namespace*: Namespace of the code component. <br/> - *name*: Name of the code component. <br/> - *template*: Field or dataset <br/> - **push**: Pushes the code component to the Common Data Service instance with all the latest changes. It has the following parameter: <br/> - *publisher-prefix*: Publisher prefix of the organization.| `pac pcf init --namespace <specify your namespace here> --name <Name of the code component> --template <component type>` <br/> <br/> `pac pcf push --publisher-prefix <your publisher prefix>`|
 |**solution**|Commands for working with Common Data Service projects. It has the following parameters: <br/> - **init**: Initializes the solution project. It has the following parameters:<br/> - *publisher-name*: Publisher name of the organization. <br/> - *publisher-prefix*: Publisher prefix of the organization. <br/> - **add-reference**: Sets the reference path to the component project folder by passing the `path` parameter.<br/> - **clone**: Creates a solution project based up on the existing solution project by passing the following parameters `name`, `version`, and `include`|`pac solution init --publisher-name <enter your publisher name> --publisher-prefix <enter your publisher prefix>` <br/><br/> `pac solution add-reference --path <path to your Power Apps component framework project>`<br/><br/> `pac solution clone –name<name of the solution to be exported> --version <version of your solution> --include <settings that should be included>`|
 |**auth**|Commands to authenticate to Common Data Service. It has the following parameters: <br/> - **create**: Creates the authentication profile for your organization by passing the `url` parameter. You need to pass the organization url for the `url` parameter. <br/> - **list**: Provides the list of authentication profiles. <br/> - **select**: Provides a way to switch between previously created authentication profiles by passing the `index` parameter.<br/>**delete**: Deletes the authentication profile created by passing  the `index` parameter.|`pac auth create --url <your Common Data Service org’s url>` <br/> <br/> `pac auth list` <br/><br/> `Pac auth select --index <index of the active profile>`|
-|**telemetry**|Manages the telemetry settings. It has the following parameters: <br/>- *enable*: Enables the telemetry option.<br/> - *disable*: Disables the tlemetry option.<br/> - *status*: Returns whether the telemetry is enabled or disabled.|`pac telemetry enable` <br/><br/> `pac telemetry disable`|
+|**telemetry**|Manages the telemetry settings. It has the following parameters: <br/>- *enable*: Enables the telemetry option.<br/> - *disable*: Disables the telemetry option.<br/> - *status*: Returns whether the telemetry is enabled or disabled.|`pac telemetry enable` <br/><br/> `pac telemetry disable`|
 |**org**|Command to work with Common Data Service.|`pac org who`|
 |**plugin**|Manages to create a plug-in project|`pac plugin init`|
 
 
 ## Uninstall Microsoft Power Apps CLI
 
-To uninstall the Power Apps CLI tooling, run the MSI from [here](https://aka.ms/PowerAppsCLI). 
+To uninstall the Power Apps CLI tooling, run the MSI from [here](https://aka.ms/PowerAppsCLI).
 
 If you are a **Private Preview** participant and have an older version of CLI, follow these steps: