From a63aeeecb27b2ba8e0abee2f03470591bd88933b Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Fri, 21 Apr 2017 11:14:48 -0700 Subject: [PATCH] tiny change --- windows/deployment/upgrade/upgrade-readiness-resolve-issues.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-resolve-issues.md b/windows/deployment/upgrade/upgrade-readiness-resolve-issues.md index f086bf5c7a..4bec01b0f0 100644 --- a/windows/deployment/upgrade/upgrade-readiness-resolve-issues.md +++ b/windows/deployment/upgrade/upgrade-readiness-resolve-issues.md @@ -162,7 +162,7 @@ The Upgrade Readiness proposed action plan is an optimally ordered list of apps The proposed action plan represents the order thath Microsoft recommends you rationalize the upgrade-readiness of your apps and drivers. By validating apps and drivers in the order proposed, you can ensure that you are testing efficiently. -Each item in the proposed action plan represents either an application or a driver that you have not yet marked “Ready to upgrade”. +Each item in the proposed action plan represents either an application or a driver that you have not yet marked “Ready to upgrade.” >Since “Low install count” apps are automatically marked “Ready to upgrade”, you will not see any of these apps in the proposed action plan.