Addressing some feedback from BugBash (#8)

* Addressing some feedback from bugbash

* added line breaks and a link to the download

* fix Win32 app isolation capitalization

* Update docs/packaging/msix-packaging-tool.md

Co-authored-by: Dylan DSilva <83655835+ddsilva-msft@users.noreply.github.com>

* changing link

* Update docs/packaging/msix-packaging-tool.md

Co-authored-by: macruzco <93291474+macruzco@users.noreply.github.com>

* Update docs/packaging/msix-packaging-tool.md

Co-authored-by: macruzco <93291474+macruzco@users.noreply.github.com>

---------

Co-authored-by: macruzco <93291474+macruzco@users.noreply.github.com>
Co-authored-by: Dylan DSilva <83655835+ddsilva-msft@users.noreply.github.com>

Author: 3 people

docs/packaging/msix-packaging-tool.md

@@ -1,16 +1,23 @@
 # Table of Contents
-1. [Convert an existing win32 installer into an .msix app](#Win32)
-2. [Convert an existing .msix app to run isolated](#MSIX)
+1. [Convert an existing win32 installer into an .msix app](#Win32-->-msix)
+2. [Convert an existing .msix app to run isolated](#MSIX-->-Isolated-Win32)
 
 ## Overview
 
 This page will cover everything needed to package an existing MSIX or win32 application into
-Isolated Win32 App. This will be done through the MSIX Packaging Tool (MPT). **Note** that the version of MPT that supports Win32 App Isolation is v1.2023.517.0, available in the release assets of this project. The [store version of MPT](https://learn.microsoft.com/en-us/windows/msix/packaging-tool/tool-overview) is **outdated** for the purposes of the Win32 App Isolation feature.
+an isolated Win32 app. This will be done through the MSIX Packaging Tool (MPT). **Note** that the
+version of MPT that supports Win32 app isolation is v1.2023.517.0, available in the release assets
+of this project. The [store version of MPT](https://learn.microsoft.com/en-us/windows/msix/packaging-tool/tool-overview) 
+is **outdated** for the purposes of the Win32 app isolation feature. You can find additional 
+documentation for MPT [here](https://learn.microsoft.com/en-us/windows/msix/packaging-tool/tool-overview).
 
-## Win32 -> MSIX <a name="Win32"></a>
+You can find the download for MPT, as well as the profiler, in the [releases](../../../../releases) section of the github.
 
-1. Select "Application Pacakge" on the far left and choose where the package will be created.
-This flow will follow the "Create package on this computer" option.
+## Win32 -> MSIX
+
+1. Select "Application Package" on the far left and choose where the package will be created.
+This flow will follow the "Create package on this computer" option. **Note** This will result 
+in the app installed as a normal win32 after finishing step 5.
 
     ![image](https://github.com/microsoft/win32-app-isolation/blob/main/docs/packaging/images/01-packaging-main-menu.png)
 
@@ -23,7 +30,7 @@ blank as we will need to edit the manifest and sign it again.
 
     ![image](https://github.com/microsoft/win32-app-isolation/blob/main/docs/packaging/images/03-packaging-installer.png)
 
-4. Enter the package information. The publisher name must match the name on the certificate used to sign in later steps.
+4. Enter the package information.
 
     ![image](https://github.com/microsoft/win32-app-isolation/blob/main/docs/packaging/images/04-packaging-package-info.png)
 
@@ -36,11 +43,13 @@ MSIX will pick up on them
 7. Repeat the same process if there are services in the package
 
 8. Clicking Create will save the package as a full trust package. Click the "Package Editor" button
-to go to the "Package Editor" flow from the main menu
+to go to the "Package Editor" flow from the main menu. This can take up to several minutes depending
+on the size of the package.
 
     ![image](https://github.com/microsoft/win32-app-isolation/blob/main/docs/packaging/images/05-packaging-create-package.png)
 
-## MSIX -> Isolated Win32 <a name="MSIX"></a>
+## MSIX -> Isolated Win32
+
 1. Select the far right option "Application Pacakge" and browse to the .msix file and click the
 "Open package" button.
 
@@ -84,7 +93,8 @@ to go to the "Package Editor" flow from the main menu
     * `isolatedWin32-volumeRootMinimal`
 
 4. Save and close the manifest window. If there are any errors in the manifest, MPT will display
-them. Select Create/Save to generate the .msix file.
+them. Select Create/Save to generate the .msix file. This can take serveral minutes depending on 
+the size of the package
 
 5. See [application capability profiler](../profiler/application-capability-profiler.md) for
 information on identifying capabilities that may need to be declared in the application package