Merge pull request #2150 from TerryGLee/tglee-vsinstall

[install] fix headings in Admin Guide ...

Author: PRMerger15

docs/install/visual-studio-administrator-guide.md

@@ -21,7 +21,7 @@ ms.workload:
 
 In enterprise environments, it's common for system administrators to deploy installations to end-users from a network share or by using systems management software. We've designed the Visual Studio setup engine to support enterprise deployment, allowing system administrators the ability to create a network install location, to pre-configure installation defaults, to deploy product keys during the installation process, and to manage product updates after a successful rollout. This administrator guide provides scenario-based guidance for enterprise deployment in networked environments.
 
-## Deploying Visual Studio 2017 in an enterprise environment
+## Deploy Visual Studio 2017 in an enterprise environment
 
 You can deploy Visual Studio 2017 to client workstations as long as each target computer meets the [minimum installation requirements](https://www.visualstudio.com/en-us/productinfo/vs2017-system-requirements-vs). Whether you're deploying through software like System Center or through a batch file, you'll typically want to go through the following steps:
 
@@ -44,7 +44,7 @@ You can deploy Visual Studio 2017 to client workstations as long as each target
 > [!IMPORTANT]
 > Note that installations from a network share will "remember" the source location they came from. This means that a repair of a client machine might need to return to the network share that the client originally installed from. Choose your network location carefully so that it aligns to the lifetime that you expect to have Visual Studio 2017 clients running in your organization.
 
-## Visual Studio tools
+## Use Visual Studio tools
 
 We have several tools available to help you [detect and manage installed Visual Studio instances](tools-for-managing-visual-studio-instances.md) on client machines.