Style and Acrolinx fixes

Make the grammar checker happy. 
Use consistent formatting of compiler options.

Author: colin-home

docs/build/reference/debug-generate-debug-info.md

@@ -20,9 +20,9 @@ The linker puts the debugging information into a program database (PDB) file. It
 
 An executable (.exe file or DLL) created for debugging contains the name and path of the corresponding PDB. The debugger reads the embedded name and uses the PDB when you debug the program. The linker uses the base name of the program and the extension .pdb to name the program database, and embeds the path where it was created. To override this default, set [/PDB](pdb-use-program-database.md) and specify a different file name.
 
-The **/DEBUG:FASTLINK** option is available in Visual Studio 2017 and later. This option generates a limited PDB that indexes into the debug information in the object files and libraries used to build the executable instead of making a full copy. This limited PDB can't be used to debug on computers other than the computer where the binary and its libs were built as the PDB is not intended to be used on any other computer. In Visual Studio 2017, this option can sometimes greatly improve link times compared with /DEBUG:FULL. In Visual Studio 2019 and later, /DEBUG:FULL is faster than earlier versions. Now, /DEBUG:FASTLINK isn't always faster than /DEBUG:FULL, and it is rarely more than twice as fast.
+The **/DEBUG:FASTLINK** option is available in Visual Studio 2017 and later. This option generates a limited PDB that indexes into the debug information in the object files and libraries used to build the executable instead of making a full copy. You can't use this limited PDB to debug on computers other than the computer where the binary and its libs were built, as the PDB isn't intended to be used on any other computer. In Visual Studio 2017, this option can sometimes greatly improve link times compared with **/DEBUG:FULL**. In Visual Studio 2019 and later, **/DEBUG:FULL** is faster than earlier versions. Now, **/DEBUG:FASTLINK** isn't always faster than **/DEBUG:FULL**, and it's rarely more than twice as fast.
 
-A /DEBUG:FASTLINK PDB can be converted to a full PDB. In Visual Studio, use the Project or Build menu items for generating a full PDB file to create a full PDB for the project or solution. In a developer command prompt, you can use the mspdbcmf.exe tool. 
+A **/DEBUG:FASTLINK** PDB can be converted to a full PDB. In Visual Studio, use the Project or Build menu items for generating a full PDB file to create a full PDB for the project or solution. In a developer command prompt, you can use the `mspdbcmf.exe` tool.
 
 The **/DEBUG:FULL** option moves all private symbol information from individual compilation products (object files and libraries) into a single PDB, and can be the most time-consuming part of the link. However, the full PDB can be used to debug the executable when no other build products are available, such as when the executable is deployed.