diff --git a/windows/manage/appv-auto-batch-sequencing.md b/windows/manage/appv-auto-batch-sequencing.md
index 1d370065aa..db30fd169b 100644
--- a/windows/manage/appv-auto-batch-sequencing.md
+++ b/windows/manage/appv-auto-batch-sequencing.md
@@ -44,7 +44,7 @@ Sequencing multiple apps at the same time requires that you create a **ConfigFil
 
     - **<Installer>.** The file name for the app executable. This will typically be an .exe or .msi file.
 
-    - **&lt;InstallerOptions&gt;.** The command-line options required for the app installation. <!-- [Liz] Add the command-line improvements section as a subheading here -->
+    - **&lt;InstallerOptions&gt;.** The command-line options required for the app installation.
 
     - **&lt;TimeoutInMinutes&gt;.** The maximum amount of time, in minutes, that the cmdlet should wait for sequencing to complete. You can enter a different value for each app, based on the size and complexity of the app itself.
 
diff --git a/windows/manage/appv-auto-batch-updating.md b/windows/manage/appv-auto-batch-updating.md
index 847f5807f9..9ddfe5c45e 100644
--- a/windows/manage/appv-auto-batch-updating.md
+++ b/windows/manage/appv-auto-batch-updating.md
@@ -42,7 +42,7 @@ Updating multiple apps at the same time requires that you create a **ConfigFile*
 
     - **&lt;Installer&gt;.** The file name for the app executable. This will typically be an .exe or .msi file.
 
-    - **&lt;InstallerOptions&gt;.** The command-line options required for the app installation. <!-- [Liz] Add the command-line improvements section as a subheading here -->
+    - **&lt;InstallerOptions&gt;.** The command-line options required for the app installation.
 
     - **&lt;Package&gt;.** The file path to the location of your App-V packages. These packages were created when you sequenced your apps.
 
diff --git a/windows/manage/appv-create-and-use-a-project-template.md b/windows/manage/appv-create-and-use-a-project-template.md
index 9ea8d246a9..c430efef24 100644
--- a/windows/manage/appv-create-and-use-a-project-template.md
+++ b/windows/manage/appv-create-and-use-a-project-template.md
@@ -53,7 +53,7 @@ After creating the template, you can apply it to all of your new virtual app pac
 
 - [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md)
 
-- [Manually sequence a single app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) [Liz] Do we want to continue to point to the manual steps? Is there a reason to do one over the other?
+- [Manually sequence a single app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md)
 
 **Have a suggestion for App-V?**<p>
 Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).