incorp feedback

Clarified command syntax

Author: TylerMSFT

docs/overview/how-to-report-a-problem-with-the-visual-cpp-toolset.md

@@ -320,7 +320,7 @@ It's ideal if the example can be condensed to a single source code file, without
 Reducing the amount of code we have to consider as a possible contributor to the problem is enormously helpful to us. Using **/MP** or multi-source invocations can cause the trace to represent only the last compiled file or be incomplete. If you can't reduce the problem to a single source file, package your code into a .zip file or similar, or consider using an IDE project repro. For more information, see [Other repros](#other-repros).
 
 1. Open the **Developer Command Prompt** that matches the Visual Studio version and configuration architecture used to build your project.
-1. Enter the command `cl /d1module:enableLogging` *trace.json* [*other-args*] *filename.cpp*. For *trace.json*, specify the desired output file name for the module trace. For [*other-args*], include any additional compilation arguments. For *filename.cpp*, specify the source file that reproduces the problem.
+1. Enter the command `cl /d1module:enableLogging`*trace.json* [*other-args*] *filename.cpp*. For *trace.json*, specify the desired output file name for the module trace. There can't be a space between `/d1module:enableLogging` and the output file name. For [*other-args*], include any additional compilation arguments. For *filename.cpp*, specify the source file that reproduces the problem.
 1. If multiple translation units are involved in the problem, run separate single-file invocations to collect a trace for the specific file that reproduces the problem. You can collect traces for additional relevant files if needed.
 
 Finally, attach the generated *trace.json* file along with the preprocessed repro to your report.