Apply suggestions from code review

Co-authored-by: Paul Broadwith <[email protected]>

ReadMe.md

@@ -106,7 +106,8 @@ For more information on vagrant commands, see the [Vagrant Docs](http://docs.vag
 ## Using Hyper-V instead of VirtualBox
 
 > [!CAUTION]
-> It is recommended to favour running the Chocolatey Test Environment under VirtualBox.
+> It is recommended to favor running the Chocolatey Test Environment under VirtualBox.
+
 > Hyper-V support is intended to lower the barrier to entry for those using Windows features which force the usage of Hyper-V,
 > such as the Windows Subsystem for Linux (WSL 2), Windows Sandbox, Device Guard, and Credential Guard.
 >
@@ -116,22 +117,26 @@ For more information on vagrant commands, see the [Vagrant Docs](http://docs.vag
 > The Hyper-V role requires Windows 10 or 11 Enterprise, Pro, or Education.
 > It **cannot** be installed on Home editions of Windows.
 
- 1. Ensure setup above is complete, ignoring the need for VirtualBox
- 1. Enable the Hyper-V feature
-     * Open a PowerShell console as Administrator
-     * Run `Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All -All`
-     * Restart Windows
- 1. Follow the general [Preparing the Testing Environment](#preparing-the-testing-environment) instructions except swap the default `vagrant up` command for `vagrant up --provider=hyperv`
-     * The image downloaded the first time you run this command is specific to Hyper-V and so a large download will be required even if you've already downloaded the VirtualBox image
+ 1. Ensure setup above is complete, ignoring the need for VirtualBox.
+ 1. Enable the Hyper-V feature:
+     * Open a PowerShell console as Administrator.
+     * Run `Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All -All`.
+     * Restart Windows.
+ 1. Follow the general instructions to [prepare the testing environment](#preparing-the-testing-environment), swapping the default `vagrant up` command with `vagrant up --provider=hyperv`.
+     * The Hyper-V image, downloaded the first time you run command is very large (> 5GB) and specific to Hyper-V.
 
 ## Differences Between This and Package Verifier Service
 
-There are a couple of difference between the [verifier service](https://docs.chocolatey.org/en-us/community-repository/moderation/package-verifier) and this environment.
+There are a couple of difference between the [Package Verifier service](https://docs.chocolatey.org/en-us/community-repository/moderation/package-verifier) and this environment.
+
 
  * The verifier is run without the GUI - meaning it is run in a headless state. There is no box to interact with.
- * The verifier only runs against Windows 2019 currently. This repo is adding more boxes as they become available.
- * The verifier times out on waiting for a command after 12 minutes.
- * Synced folders are different - the verifier syncs the .chocolatey folder to gather the package information files.
+ * Package Verifier only runs against Windows Server 2019, currently.
+
+ * Package Verifier times out on waiting for a command after 12 minutes.
+
+ * Synced folders are different - Package Verifier syncs the `.chocolatey` folder to gather the package information files.
+
  * Specific VM settings are different (for performance):
     * No GUI (as previously mentioned) - `v.gui = false`
     * 6GB RAM - `v.customize ["modifyvm", :id, "--memory", "6144"]`