Live publish

Author: buck1ey

powerapps-docs/developer/component-framework/reference/control/getoutputs.md

@@ -23,8 +23,8 @@ Model-driven apps and canvas apps (public preview)
 
 ## Remarks
 
-The output will contain a value for each property marked as `input-output` or `bound` in the manifest.
-For example, if the manifest has a property `value` that is an `input-output`, and you want to set that to the local variable `myvalue` you should return:
+The output will contain a value for each property with a usage as `bound` in the manifest.
+For example, if the manifest has a property named `value` that has usage as `bound`, and you want to set that to the local variable `myvalue` then you should return:
 
 ```TypeScript
 {

powerapps-docs/developer/component-framework/reference/control/includes/getoutputs-description.md

@@ -15,4 +15,4 @@ applies_to:
 ms.assetid: 06007e6e-7c82-4842-9584-75c5c5782c4d
 ---
 
-It is called by the framework prior to a component receiving the new data. Returns an object based on nomenclature defined in manifest, expecting objects[s] for the property marked as `bound` or `output`.
+It is called by the framework prior to a component receiving the new data. Returns an object based on nomenclature defined in manifest, expecting objects[s] for the property marked as `bound`.

powerapps-docs/teams/import-solution-in-teams.md

@@ -1,6 +1,6 @@
 ---
 title: Import a solution into Dataverse for Teams | Microsoft Docs
-description: Explains how to import a Dataverse solution into Dataverse for Teams.
+description: Explains how to import a Microsoft Dataverse solution into Microsoft Dataverse for Teams.
 author: wimcoor
 ms.service: powerapps
 ms.topic: conceptual
@@ -17,44 +17,46 @@ Microsoft Dataverse for Teams provides a way to transport the customizations you
 
 1. Create a solution in a Dataverse environment. 
 1. Export the solution from the Dataverse environment.
-1. Import the solution in Dataverse for Teams.
+1. Import the solution into Dataverse for Teams.
 
 ## Create a solution in Dataverse
 
-The first step to move your customizations is to create a solution in Dataverse. Include only components that are fully supported for Dataverse for Teams. Solutions that included components that are not supported by Dataverse for Teams won’t import. Only the following custom components can be imported into Dataverse for Teams:
+The first step to move your customizations is to create a solution in Dataverse. Include only components that are fully supported for Dataverse for Teams. Solutions that include components that are not supported by Dataverse for Teams won’t import. Only the following custom components can be imported into Dataverse for Teams:
 
-* Canvas apps 
-* Tables 
-* Flows 
-* Bots 
-* Connection references 
-* Environment variables 
+* Canvas apps
+* Tables
+* Flows
+* Bots
+* Connection references
+* Environment variables
 
 > [!NOTE]
 > Only include items that you or your team have created. Solutions that contain any of the standard Dataverse or Dynamics 365 tables, such as account or contact, won’t import.
 
-For information about the differences between Dataverse for Teams and Dataverse, see [How are Dataverse for Teams and Dataverse different?](data-platform-compare.md)
+For information about the differences between Dataverse for Teams and Dataverse, go to [How are Dataverse for Teams and Dataverse different?](data-platform-compare.md)<!-- Edit note: This is per Style, but you might want to hold this kind of update for a broader future pass. -->
 
-For information about how to create a solution with Dataverse, see [Create a solution](../maker/common-data-service/create-solution.md). 
+For information about how to create a solution with Dataverse, go to [Create a solution](../maker/common-data-service/create-solution.md).
 
-## Export the solution form Dataverse
+## Export the solution from Dataverse
 
-Typically, you want to export your solution as managed. However, if your goal is to transport your customizations to Dataverse for Teams and continue your development from there, export your solution as an unmanaged solution. More information: [Export solutions](../maker/common-data-service/export-solutions.md) 
+Typically, you want to export your solution from Dataverse as managed. However, if your goal is to transport your customizations to Dataverse for Teams and continue your development from there, export your solution as an unmanaged solution. More information: [Export solutions](../maker/common-data-service/export-solutions.md) 
 
 ## Import the solution into Dataverse for Teams
 
+Take the following steps to import a solution into Dataverse for Teams:
+
 1. From the Power Apps personal app in Teams, select the **Build** tab of the team where you want to import the solution. More information: [Install the Power Apps personal app in Microsoft Teams](install-personal-app.md)
 1. Select **See all**, and then on the command bar, select **Import**.
-1. On the **Import a solution** pane, select **Browse**.
+1. On the **Import a solution** page, select **Browse**.
 
     :::image type="content" source="media/teams-import-solution.png" alt-text="Select Browse":::
 1. Locate the compressed (.zip or .cab) file that contains the solution you want to import, select **Open**, and then select **Next**. 
-1. Information about the solution is displayed. Depending on the components in the solution, you may be prompted for additional information before you select **Next**.
+1. Information about the solution is displayed. Depending on the components in the solution, you might be prompted for additional information before you select **Next**.
    - If your solution contains connection references, you’ll be prompted to select the connections you want. If a connection does not already exist, create a new one. 
-   - If your solution contains environment variables, you will be prompted to enter values. You will not see this screen if values are already present in your solution or the target environment.
+   - If your solution contains environment variables, you'll be prompted to enter values. You will not see this page if values are already present in your solution or the target environment.
 1. Select **Import**.
 
-Your solution imports in the background and may take multiple minutes. A notification appears on the **Build** tab as the solution is imported.
+Your solution imports in the background and might take multiple minutes. A notification appears on the **Build** tab as the solution is imported.
 
 :::image type="content" source="media/teams-import-staus.png" alt-text="Currently importing solution message ":::
 After the import completes, a success or failure notification is displayed.
@@ -65,13 +67,13 @@ The ___location of your solution components is different depending on whether you i
 
 ## Troubleshooting import failures
 
-If the import isn’t successful, you’ll see a notification on the solutions page that displays error or warnings messages that were captured. Select **Download Log File** to capture details about what caused the import to fail. The most common cause for an import to fail is that the solution did not contain some required components.
+If the import isn’t successful, you’ll see a notification on the solutions page that displays error or warning messages that were captured. Select **Download Log File** to capture details about what caused the import to fail. The most common cause for an import to fail is that the solution did not contain some required components.
 
-When you download the log file, you will find an XML file in your browser's default download folder that you can open using Office Excel to view the contents.
+When you download the log file, you will find an XML file in your browser's default download folder that you can open using an XML reader, such as Microsoft Excel, to view the contents.
 
-## Known issue
+## Known issues
 
-When you are working with a new Dataverse for Teams environment, the **Import** command is missing because the **See all** link **Build** tab is not displayed for that environment.  
+When you are working with a new Dataverse for Teams environment, the **Import** command is missing because the **See all** link located on the **Build** tab is not displayed for that environment.  
 
 To work around this issue, create and save an app in the environment. When an item exists in the environment, the **See all** link is available and you will be able to browse to the **Build** tab.
 

powerapps-docs/user/collaborate-using-sharepoint.md

@@ -10,8 +10,8 @@ ms.service: powerapps
 ms.devlang: na
 ms.topic: conceptual
 ms.component: model
-ms.date: 03/02/2020
-ms.author: matp
+ms.date: 12/14/2020
+ms.author: mkaur
 search.audienceType: 
   - maker
 search.app: 
@@ -29,6 +29,9 @@ Before you can use SharePoint to store documents, it must be enabled by your sys
 
 -   [Manage your documents using SharePoint](https://docs.microsoft.com/power-platform/admin/manage-documents-using-sharepoint)  
 
+> [!IMPORTANT]
+> SharePoint managed documents that are deleted using a Power Apps or Dynamics 365 customer engagement app are permanently deleted from both the app and the SharePoint site. 
+
 ## Where do you access the documents from?
 
 1. For row types that support document management, open the row, select the **Related** tab, and then select **Documents**.