Fixes to fmts and typos from visual test pass

windows/manage/appv-allow-administrators-to-enable-connection-groups.md

@@ -23,8 +23,8 @@ Use one of the following methods to allow only administrators to enable or disab
 
 <table>
 <colgroup>
-<col width="50%" />
+<col width="30%" />
-<col width="50%" />
+<col width="70%" />
 </colgroup>
 <thead>
 <tr class="header">

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

@@ -69,8 +69,8 @@ Use the following information to publish a package that has been added to a spec
 
 <table>
 <colgroup>
-<col width="50%" />
+<col width="30%" />
-<col width="50%" />
+<col width="70%" />
 </colgroup>
 <thead>
 <tr class="header">
@@ -176,18 +176,12 @@ App-V cmdlets have been assigned to variables for the previous examples for clar
 
 ## <a href="" id="bkmk-admins-pub-pkgs"></a>To enable only administrators to publish or unpublish packages
 
-
+Starting in App-V 5.0 SP3, you can use the following cmdlet and parameter to enable only administrators (not end users) to publish or unpublish packages:
-**Note**  
-**This feature is supported starting in App-V 5.0 SP3.**
-
- 
-
-Use the following cmdlet and parameter to enable only administrators (not end users) to publish or unpublish packages:
 
 <table>
 <colgroup>
-<col width="50%" />
+<col width="30%" />
-<col width="50%" />
+<col width="70%" />
 </colgroup>
 <tbody>
 <tr class="odd">
@@ -218,8 +212,8 @@ To use the App-V Management console to set this configuration, see [How to Publi
 
 <table>
 <colgroup>
-<col width="50%" />
+<col width="30%" />
-<col width="50%" />
+<col width="70%" />
 </colgroup>
 <thead>
 <tr class="header">

windows/manage/appv-migrating-to-appv-from-a-previous-version.md

@@ -30,8 +30,8 @@ You can also use the `–OSDsToIncludeInPackage` parameter with the `ConvertFrom
 </colgroup>
 <thead>
 <tr class="header">
-<th align="left">New in App-V</th>
+<th align="left">New in App-V for Windows 10</th>
-<th align="left">Prior to App-V</th>
+<th align="left">Prior to App-V for Windows 10</th>
 </tr>
 </thead>
 <tbody>

windows/manage/appv-running-locally-installed-applications-inside-a-virtual-environment.md

@@ -113,7 +113,7 @@ Use the following example syntax, and substitute the name of your package for **
 
 `Start-AppvVirtualProcess -AppvClientObject $AppVName cmd.exe`
 
-If you don’t know the exact name of your package, you can use the command line **Get-AppvClientPackage \*executable\***, where **executable** is the name of the application, for example: Get-AppvClientPackage \*Word\*.
+If you don’t know the exact name of your package, you can use the command line <strong>Get-AppvClientPackage \*executable\*</strong>, where **executable** is the name of the application, for example:<br>Get-AppvClientPackage \*Word\*
 
 ## <a href="" id="bkmk-cl-switch-appvpid"></a>Command line switch /appvpid:&lt;PID&gt;
 
@@ -143,7 +143,7 @@ To get the package GUID and version GUID of your application, run the **Get-Appv
 
 -   Version ID of the desired package
 
-If you don’t know the exact name of your package, use the command line **Get-AppvClientPackage \*executable\***, where **executable** is the name of the application, for example: Get-AppvClientPackage \*Word\*.
+If you don’t know the exact name of your package, use the command line <strong>Get-AppvClientPackage \*executable\*</strong>, where **executable** is the name of the application, for example:<br>Get-AppvClientPackage \*Word\*
 
 This method lets you launch any command within the context of an App-V package, regardless of whether the package is currently running.
 

windows/manage/appv-using-the-client-management-console.md

@@ -41,8 +41,8 @@ The client management console contains the following described main tabs.
 
 <table>
 <colgroup>
-<col width="50%" />
+<col width="20%" />
-<col width="50%" />
+<col width="80%" />
 </colgroup>
 <thead>
 <tr class="header">