deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-22 22:03:46 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Fix typos in application-management

Browse Source 
Fixes all typos I could find in /windows/application-management
This commit is contained in:
Lachlan Picking
2019-01-25 00:42:53 +10:00
parent 2ea418d13b
commit 5c75a26495
20 changed files with 31 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
windows/application-management/deploy-app-upgrades-windows-10-mobile.md
View File

@ -20,7 +20,7 @@ There are two steps to deploy an app upgrade:
1. [Define the supersedence](#define-app-supersedence) - this lets Configuration Manager know that the old version should be replaced by the new version.
2. [Deploy the upgrade](#deploy-the-app-upgrade) to your users.
The following steps walk you through the upgrade deployment process - we have an upgraded version of the Walking Scorer app (moving from version 12.23.2.0 to 12.23.3.0). Becasuse we previously used Configuration Manager to deploy the existing version, we'll use it now to upgrade the app.
The following steps walk you through the upgrade deployment process - we have an upgraded version of the Walking Scorer app (moving from version 12.23.2.0 to 12.23.3.0). Because we previously used Configuration Manager to deploy the existing version, we'll use it now to upgrade the app.
Before you can deploy the upgrade, make sure you import the new version of the app and distribute it to your manage.microsoft.com distribution point.
@ -42,7 +42,7 @@ Before you can deploy the upgrade, make sure you import the new version of the a
> Do **NOT** select **Uninstall**. This tells Configuration Manager to uninstall the old version, but it does **NOT** then install the new version.
6. Click **OK**.
7. If you have other versions of the same app, repeate steps 4-6 for each version. Click **OK** when you're done.
7. If you have other versions of the same app, repeat steps 4-6 for each version. Click **OK** when you're done.
> [!NOTE]
> Need to remove a supersedence? (Maybe the new version turned out to be flaky and you don't want users to get it yet.) On the **Supersedence** tab for the *new* version of the app, double-click the older version in the list of supersedence rules, and then change the **New Deployment Type** to **Do not replace**.