Merge branch 'master' into 2129156

Author: tapanm-MSFT

powerapps-docs/developer/component-framework/limitations.md

@@ -3,7 +3,7 @@ title: "Limitations of Power Apps component framework | MicrosoftDocs"
 description: "Limitations using Power Apps component framework"
 author: nkrb
 manager: kvivek
-ms.date: 10/01/2019
+ms.date: 12/16/2020
 ms.service: "powerapps"
 ms.topic: "index-page"
 ms.assetid: 18e88d702-3349-4022-a7d8-a9adf52cd34f
@@ -14,12 +14,15 @@ ms.author: "nabuthuk"
 
 With the release of Power Apps component framework, you can now create your own code components to improve the user experience in model-driven apps and canvas apps. Even though you can create your own components, there are some limitations that restrict developers implementing some features in the code components. Below are some of the limitations:
 
-1. Microsoft Dataverse dependent APIs, including WebAPI along with few other APIs, are not available for this experimental preview. For individual API availability for this experimental preview release, see [Power Apps component framework API reference](reference/index.md).
+1. Microsoft Dataverse dependent APIs, including WebAPI, are not available for canvas applications yet. For individual API availability in current public preview release,  see [Power Apps component framework API reference](reference/index.md).
+
 2. Code components should bundle all the code including external library content into the primary code bundle. To see an example of how the Power Apps command line interface can help with bundling your external library content into a component-specific bundle, see [Angular flip component](sample-controls/angular-flip-control.md) example.
 
    > [!NOTE]
    > Support for shared libraries across components using library nodes in the component manifest is not yet supported. We are reviewing this and will be adding this capability in future release.
 
+3. Code components should not use the HTML web storage objects, like `window.localStorage` and `window.sessionStorage`, to store data. Data stored locally on the user's browser or mobile client is not secure and not guaranteed to be available reliably.
+
 ## Related topics
 
 [Power Apps component framework API reference](reference/index.md)<br/>

powerapps-docs/guidance/planning/gaining-support.md

@@ -5,7 +5,7 @@ author: TGrounds
 ms.service: powerapps
 ms.topic: conceptual
 ms.custom: guidance
-ms.date: 06/16/2020
+ms.date: 12/18/2020
 ms.author: thground
 ms.reviewer: kathyos
 
@@ -34,5 +34,9 @@ the project. Nick's sponsorship will ensure that employees adopt the new
 process. Charlotte's sponsorship will provide some funds in addition to permission
 to access key data.
 
-> [!div class="nextstepaction"]
-> [Next step: Design the app](designing-phase.md)
+### Next steps
+
+- If you're designing an app using Power Apps, see [Design the app](designing-phase.md).
+
+- If you're designing an automation using Power Automate, see [Design the automation](/power-automate/guidance/planning/process-design) in Power Automate guidance docs.
+

powerapps-docs/guidance/planning/planning-phase.md

@@ -5,7 +5,7 @@ author: TGrounds
 ms.service: powerapps
 ms.topic: conceptual
 ms.custom: guidance
-ms.date: 06/16/2020
+ms.date: 12/05/2020
 ms.author: thground
 ms.reviewer: kathyos
 
@@ -37,5 +37,8 @@ In this section, you'll learn about:
 
 - [Creating a project plan](defining-app-project-objective.md)
 
+> [!NOTE]
+> The planning information covered here is also applicable for Power Automate users who are planning to automate their processes or tasks. You can find detailed information about planning a Power Automate project in the Power Automate guidance documentation: [Planning a Power Automate Project](/power-automate/guidance/planning/introduction)
+
 > [!div class="nextstepaction"]
 > [Next step: Identifying the business problem to solve](identifying-business-problem-to-solve.md)