new attempt on Edge docfx, fixing note references, bookmark links

windows/application-management/app-v/appv-configure-access-to-packages-with-the-management-console.md

@@ -35,7 +35,7 @@ Use the following procedure to configure access to virtualized packages.
     1. Using the format **mydomain** \\ **groupname**, enter the name or part of the name of an Active Directory group object, then select **Check**.
 
        > [!NOTE]  
-        >Ensure that you provide an associated domain name for the group that you are searching for.
+       > Ensure that you provide an associated domain name for the group that you are searching for.
 
 3. Grant access to the package by first selecting the desired group, then selecting **Grant Access**. The newly added group is displayed in the **AD entities with access** pane.
 

windows/application-management/app-v/appv-create-a-custom-configuration-file-with-the-management-console.md

@@ -31,7 +31,7 @@ You can create a dynamic user configuration file with the App-V Management Conso
 4. Select **Advanced**, and then select **Export Configuration**. Enter a file name and select **Save**. Now you can edit the file to configure a package for a user.
 
    > [!NOTE]  
-    >If you want to export a configuration while running on Windows Server, make sure to disable the IE Enhanced Security Configuration setting. If this setting is enabled and set to block downloads, you won't be able to download anything from the App-V Server.
+   > If you want to export a configuration while running on Windows Server, make sure to disable the IE Enhanced Security Configuration setting. If this setting is enabled and set to block downloads, you won't be able to download anything from the App-V Server.
 
 
 

windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md

@@ -32,8 +32,8 @@ Get-AppvClientPackage –Name "ContosoApplication" -Version 2
 
 Use the **Add-AppvClientPackage** cmdlet to add a package to a computer.
 
->[!IMPORTANT]
->This example only adds a package. It does not publish the package to the user or the computer.
+> [!IMPORTANT]
+> This example only adds a package. It does not publish the package to the user or the computer.
 
 For example:
 
@@ -59,8 +59,8 @@ Publish-AppvClientPackage "ContosoApplication" -Global
 
 ## Publish a package to a specific user
 
->[!NOTE]  
->You must use App-V 5.0 SP2 Hotfix Package 5 or later to use this parameter.
+> [!NOTE]  
+> You must use App-V 5.0 SP2 Hotfix Package 5 or later to use this parameter.
 
 An administrator can publish a package to a specific user by specifying the optional *–UserSID* parameter with the **Publish-AppvClientPackage** cmdlet, where *-UserSID* represents the end user’s security identifier (SID).
 
@@ -99,8 +99,8 @@ Unpublish-AppvClientPackage "ContosoApplication"
 
 ## Unpublish a package for a specific user
 
->[!NOTE]
->You must use App-V 5.0 SP2 Hotfix Package 5 or later to use this parameter.
+> [!NOTE]
+> You must use App-V 5.0 SP2 Hotfix Package 5 or later to use this parameter.
 
 An administrator can unpublish a package for a specific user by using the optional *-UserSID* parameter with the **Unpublish-AppvClientPackage** cmdlet, where *-UserSID* represents the end user’s security identifier (SID).
 
@@ -127,8 +127,8 @@ For example:
 Remove-AppvClientPackage "ContosoApplication"
 ```
 
->[!NOTE]
->App-V cmdlets have been assigned to variables for the previous examples for clarity only; assignment is not a requirement. Most cmdlets can be combined as displayed in [Add and publish a package](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#add-and-publish-a-package). For a detailed tutorial, see [App-V 5.0 Client PowerShell Deep Dive](https://blogs.technet.microsoft.com/appv/2012/12/03/app-v-5-0-client-powershell-deep-dive/).
+> [!NOTE]
+> App-V cmdlets have been assigned to variables for the previous examples for clarity only; assignment is not a requirement. Most cmdlets can be combined as displayed in [Add and publish a package](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#add-and-publish-a-package). For a detailed tutorial, see [App-V 5.0 Client PowerShell Deep Dive](https://blogs.technet.microsoft.com/appv/2012/12/03/app-v-5-0-client-powershell-deep-dive/).
 
 ## Enable only administrators to publish or unpublish packages
 

windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md

@@ -18,8 +18,8 @@ ms.topic: article
 
 Use the following procedure to publish an App-V package. Once you publish a package, computers running the App-V client can access and run the applications in that package.
 
->[!NOTE]  
->The ability to enable only administrators to publish or unpublish packages (described below) is supported starting in App-V 5.0 SP3.
+> [!NOTE]  
+> The ability to enable only administrators to publish or unpublish packages (described below) is supported starting in App-V 5.0 SP3.
 
 ## Publish an App-V package
 

windows/application-management/app-v/appv-release-notes-for-appv-for-windows.md

@@ -137,8 +137,8 @@ The InsertVersionInfo.sql script is not required for versions of the App-V manag
 
 The Permissions.sql script should be updated according to **Step 2** in [KB article 3031340](https://support.microsoft.com/kb/3031340).
 
->[!IMPORTANT] 
->**Step 1** of the KB article listed above isn't required for versions of App-V later than App-V 5.0 SP3.
+> [!IMPORTANT] 
+> **Step 1** of the KB article listed above isn't required for versions of App-V later than App-V 5.0 SP3.
 
 ## Microsoft Visual Studio 2012 not supported
 App-V doesn't support Visual Studio 2012.

windows/application-management/app-v/appv-sequence-a-package-with-powershell.md

@@ -65,8 +65,8 @@ The following list displays additional optional parameters that can be used with
 
 In Windows 10, version 1703, running the new-appvsequencerpackage or the update-appvsequencepackage cmdlets automatically captures and stores all of your customizations as an App-V project template. If you want to make changes to this package later, your customizations are automatically loaded from this template file. 
 
->[!IMPORTANT]
->If you have an auto-saved template and you attempt to load another template through the _TemplateFilePath_ parameter, the customization value from the parameter will override the auto-saved template. 
+> [!IMPORTANT]
+> If you have an auto-saved template and you attempt to load another template through the _TemplateFilePath_ parameter, the customization value from the parameter will override the auto-saved template. 
 
 ## Related topics