Removing comments and a few tweaks.

Author: Mattp123

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

@@ -35,23 +35,23 @@ The first step to move your customizations is to create a solution in Dataverse.
 
 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, go to [Create a solution](../maker/common-data-service/create-solution.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, go to [Create a solution](../maker/common-data-service/create-solution.md).
 
 ## Export the solution from Dataverse
 
 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:<!-- Edit note: Adding an example intro here since should not just depend on the heading. -->
+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** page, select **Browse**.<!-- Edit note: Per Style, use page for wizards. -->
+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 migt<!-- Edit note: Per "Can, may" in Style. --> 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'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**.
@@ -69,11 +69,11 @@ The ___location of your solution components is different depending on whether you i
 
 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 Microsoft Excel to view the contents.<!-- Edit note: Not sure if Excel is really the most common way to open such an XML file. You might say "an app such as Microsoft Excel". -->
+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 issues
 
-When you are working with a new Dataverse for Teams environment, the **Import** command is missing because the **See all** link **Build** tab<!-- Edit note: This was confusing to read, but not sure how to rewrite. Maybe the link is on the 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.