Remove command processor prompt char

Colin Robertson · Colin Robertson · commit bada18279f2e · 2020-09-13T21:07:03.000-07:00
diff --git a/docs/build/reference/headerunit.md b/docs/build/reference/headerunit.md
@@ -39,7 +39,7 @@ Given a project that references two header files and their header units, listed
 The compiler options to reference the header units for these particular header files might look like this example:
 
 ```CMD
->cl ... /experimental:module /translateInclude /headerUnit C:\utils\util.h=C:\util.h.ifc /headerUnit C:\app\app.h=C:\app.h.ifc
+cl ... /experimental:module /translateInclude /headerUnit C:\utils\util.h=C:\util.h.ifc /headerUnit C:\app\app.h=C:\app.h.ifc
 ```
 
 ### To set this compiler option in the Visual Studio development environment
diff --git a/docs/build/reference/module-exportheader.md b/docs/build/reference/module-exportheader.md
@@ -35,13 +35,13 @@ The compiler resolves a *`header-name`* based on the include directory search or
 The argument *`header-name`* must be specified the same way it would appear in source. The argument is sensitive to quoting rules and to `<` and `>` operators on the command line. The properly escaped command to build a header unit such as `<vector>` using the VS2019 command prompt might look like:
 
 ```cmd
->cl ... /experimental:module /module:exportHeader "<vector>"
+cl ... /experimental:module /module:exportHeader "<vector>"
 ```
 
 Building a local project header such as `"utils/util.h"` might look like:
 
 ```cmd
->cl ... /experimental:module /module:exportHeader """util/util.h"""
+cl ... /experimental:module /module:exportHeader """util/util.h"""
 ```
 
 The quoting rules in other command-line processors may differ.
@@ -55,13 +55,13 @@ When using the *`header-name`* form of **`/module:exportHeader`**, you may find
 Given headers `"C:\util\util.h"` and `"C:\app\app.h"`, you can export them as *`header-name`* arguments by using this command:
 
 ```cmd
->cl /IC:\ /experimental:module /module:exportHeader """util/util.h""" """app/app.h""" /FoC:\obj
+cl /IC:\ /experimental:module /module:exportHeader """util/util.h""" """app/app.h""" /FoC:\obj
 ```
 
 You can export them as *`filename`* arguments by using this command:
 
 ```cmd
->cl /IC:\ /experimental:module /module:exportHeader C:\util\util.h C:\app\app.h /FoC:\obj
+cl /IC:\ /experimental:module /module:exportHeader C:\util\util.h C:\app\app.h /FoC:\obj
 ```
 
 ### To set this compiler option in the Visual Studio development environment
diff --git a/docs/build/reference/module-reference.md b/docs/build/reference/module-reference.md
@@ -45,7 +45,7 @@ Examples of full module partition names include:
 If a module reference is created using a *`module-name`*, other modules on the command line don't get searched if the compiler encounters an import of that name. For example, given this command line:
 
 ```cmd
->cl ... /experimental:module /module:reference m.ifc /module:reference m=n.ifc
+cl ... /experimental:module /module:reference m.ifc /module:reference m=n.ifc
 ```
 
 In the case above, if the compiler sees `import m;` then *`m.ifc`* doesn't get searched.
@@ -63,13 +63,13 @@ Given three modules as listed in this table:
 The reference options using a *`filename`* argument could look like:
 
 ```cmd
->cl ... /experimental:module /module:reference m.ifc /module:reference m-part.ifc /module:reference Networking.ifc
+cl ... /experimental:module /module:reference m.ifc /module:reference m-part.ifc /module:reference Networking.ifc
 ```
 
 The reference options using *`module-name=filename`* could look like:
 
 ```cmd
->cl ... /experimental:module /module:reference m=m.ifc /module:reference M:Part1=m-part.ifc /module:reference Core.Networking=Networking.ifc
+cl ... /experimental:module /module:reference m=m.ifc /module:reference M:Part1=m-part.ifc /module:reference Core.Networking=Networking.ifc
 ```
 
 ### To set this compiler option in the Visual Studio development environment
diff --git a/docs/build/reference/translateinclude.md b/docs/build/reference/translateinclude.md
@@ -52,7 +52,7 @@ int main() { }
 The **`/translateInclude`** option allows the compiler to import the header units instead of compile the headers again. Here's an example command line that translates the include directives for *`util.h`* and *`app.h`* into imports of the header units instead:
 
 ```CMD
->cl /IC:\ /experimental:module /translateInclude /headerUnit C:\utils\util.h=C:\util.h.ifc /headerUnit C:\app\app.h=C:\app.h.ifc
+cl /IC:\ /experimental:module /translateInclude /headerUnit C:\utils\util.h=C:\util.h.ifc /headerUnit C:\app\app.h=C:\app.h.ifc
 ```
 
 ### To set this compiler option in the Visual Studio development environment
