diff --git a/windows/application-management/app-v/revision-heidi/appv-capacity-planning.md b/windows/application-management/app-v/revision-heidi/appv-capacity-planning.md
index 373cd9aa7b..06dde90c41 100644
--- a/windows/application-management/app-v/revision-heidi/appv-capacity-planning.md
+++ b/windows/application-management/app-v/revision-heidi/appv-capacity-planning.md
@@ -29,22 +29,22 @@ Before you design the App-V infrastructure, determining which applications will
Task
-More Information
+More information
Determine Application Scope
Depending on the applications to be virtualized, the App-V infrastructure can be set up in different ways. The first task is to define what applications you want to virtualize.
Determine application scope
The App-V infrastructure can be set up in different ways depending on which applications you want to virtualize. This means your first task is to define which applications you want to virtualize.
Determine Location Scope
Location scope refers to the physical locations (for example, enterprise-wide or a specific geographic location) where you plan to run the virtualized applications. It can also refer to the user population (for example, a single department) who will run the virtual applications. You should obtain a network map that includes the connection paths as well as available bandwidth to each location and the number of users using virtualized applications and the WAN link speed.
Determine location scope
"Location scope" refers to the physical locations where you plan to run the virtualized applications (for example, enterprise-wide or a specific geographic location). It can also refer to the user population that will run the virtual applications (for example, a single department). You should obtain a network map that includes the connection paths, the available bandwidth for each location, the number of users using virtualized applications, and the WAN link speed.