Front-run acrolinx fixes before emsp bulk (MicrosoftDocs#3507)

* Front-run acrolinx fixes before emsp bulk

* fix genprofile syntax block

Author: Colin Robertson

docs/build/reference/genprofile-fastgenprofile-generate-profiling-instrumented-build.md

@@ -1,64 +1,72 @@
 ---
 description: "Learn more about: /GENPROFILE, /FASTGENPROFILE (Generate Profiling Instrumented Build)"
 title: "/GENPROFILE, /FASTGENPROFILE (Generate Profiling Instrumented Build)"
-ms.date: "03/14/2018"
+ms.date: 04/14/2021
 f1_keywords: ["GENPROFILE", "FASTGENPROFILE", "/GENPROFILE", "/FASTGENPROFILE"]
 helpviewer_keywords: ["GENPROFILE", "FASTGENPROFILE"]
-ms.assetid: deff5ce7-46f5-448a-b9cd-a7a83a6864c6
 ---
-# /GENPROFILE, /FASTGENPROFILE (Generate Profiling Instrumented Build)
+# `/GENPROFILE`, `/FASTGENPROFILE` (Generate Profiling Instrumented Build)
 
-Specifies generation of a .pgd file by the linker to support profile-guided optimization (PGO). **/GENPROFILE** and **/FASTGENPROFILE** use different default parameters. Use **/GENPROFILE** to favor precision over speed and memory usage during profiling. Use **/FASTGENPROFILE** to favor smaller memory usage and speed over precision.
+Specifies generation of a *`.pgd`* file by the linker to support profile-guided optimization (PGO). **`/GENPROFILE`** and **`/FASTGENPROFILE`** use different default parameters. Use **`/GENPROFILE`** to favor precision over speed and memory usage during profiling. Use **`/FASTGENPROFILE`** to favor smaller memory usage and speed over precision.
 
 ## Syntax
 
-> **/GENPROFILE**\[**:**{\[**COUNTER32**\|**COUNTER64**]\|\[**EXACT**\|**NOEXACT**]\|**MEMMAX=**_#_\|**MEMMIN=**_#_\|\[**PATH**\|**NOPATH**]\|\[**TRACKEH** \|**NOTRACKEH** ]\|**PGD=**_filename_}]\
-> **/FASTGENPROFILE**\[**:**{\[**COUNTER32**\|**COUNTER64**]\|\[**EXACT**\|**NOEXACT**]\|**MEMMAX=**_#_\|**MEMMIN=**_#_\|[**PATH**\|**NOPATH** ]\|\[**TRACKEH** \|**NOTRACKEH** ]\|**PGD=**_filename_}]
+> **`/GENPROFILE`**\[**`:`**_`profile-argument`_\[**`,`**_`profile-argument`_ ...]]\
+> **`/FASTGENPROFILE`**\[**`:`**_`profile-argument`_\[**`,`**_`profile-argument`_ ...]]\
+
+> *`profile-argument`*\
+>  { **`COUNTER32`** | **`COUNTER64`** }\
+>  { **`EXACT`** | **`NOEXACT`** }\
+>  **`MEMMAX=`**_value_\
+>  **`MEMMIN=`**_value_\
+>  { **`PATH`** | **`NOPATH`** }\
+>  { **`TRACKEH`** | **`NOTRACKEH`** }\
+>  **`PGD=`**_filename_
 
 ### Arguments
 
-Any of the following arguments may be specified to **/GENPROFILE** or **/FASTGENPROFILE**. Arguments listed here separated by a pipe (**|**) character are mutually exclusive. Use a comma (**,**) character to separate options.
+Any of the *`profile-argument`* arguments may be specified to **`/GENPROFILE`** or **`/FASTGENPROFILE`**. Arguments listed here separated by a pipe character (**`|`**) are mutually exclusive. Use a comma character (**`,`**) to separate arguments. Don't put spaces between arguments, commas, or after the colon (**`:`**).
 
-**COUNTER32** &#124; **COUNTER64**<br/>
-Use **COUNTER32** to specify the use of 32-bit probe counters, and **COUNTER64** to specify  64-bit probe counters. When you specify **/GENPROFILE**, the default is **COUNTER64**. When you specify **/FASTGENPROFILE**, the default is **COUNTER32**.
+**`COUNTER32`** &vert; **`COUNTER64`**\
+Use **`COUNTER32`** to specify the use of 32-bit probe counters, and **`COUNTER64`** to specify  64-bit probe counters. When you specify **`/GENPROFILE`**, the default is **`COUNTER64`**. When you specify **`/FASTGENPROFILE`**, the default is **`COUNTER32`**.
 
-**EXACT** &#124; **NOEXACT**<br/>
-Use **EXACT** to specify thread-safe interlocked increments for probes. **NOEXACT** specifies unprotected increment operations for probes. The default is **NOEXACT**.
+**`EXACT`** &vert; **`NOEXACT`**\
+Use **`EXACT`** to specify thread-safe interlocked increments for probes. **`NOEXACT`** specifies unprotected increment operations for probes. The default is **`NOEXACT`**.
 
-**MEMMAX**=*value*, **MEMMIN**=*value*<br/>
-Use **MEMMAX** and **MEMMIN** to specify the maximum and minimum reservation sizes for training data in memory. The value is the amount of memory to reserve in bytes. By default, these values are determined by an internal heuristic.
+**`MEMMAX`**=*value*, **`MEMMIN`**=*value*\
+Use **`MEMMAX`** and **`MEMMIN`** to specify the maximum and minimum reservation sizes for training data in memory. The value is the amount of memory to reserve in bytes. By default, these values are determined by an internal heuristic.
 
-**PATH**  &#124; **NOPATH** <br/>
-Use **PATH**  to specify a separate set of PGO counters for each unique path to a function. Use **NOPATH**  to specify only one set of counters for each function. When you specify **/GENPROFILE**, the default is **PATH** . When you specify **/FASTGENPROFILE**, the default is **NOPATH** .
+**`PATH`**  &vert; **`NOPATH`**\
+Use **`PATH`**  to specify a separate set of PGO counters for each unique path to a function. Use **`NOPATH`**  to specify only one set of counters for each function. When you specify **`/GENPROFILE`**, the default is **`PATH`** . When you specify **`/FASTGENPROFILE`**, the default is **`NOPATH`** .
 
-**TRACKEH**  &#124; **NOTRACKEH** <br/>
-Specifies whether to use extra counters to keep an accurate count when exceptions are thrown during training. Use **TRACKEH**  to specify extra counters for an exact count. Use **NOTRACKEH**  to specify single counters for code that does not use exception handling or that does not encounter exceptions in your training scenarios.  When you specify **/GENPROFILE**, the default is **TRACKEH** . When you specify **/FASTGENPROFILE**, the default is **NOTRACKEH** .
+**`TRACKEH`**  &vert; **`NOTRACKEH`**\
+Specifies whether to use extra counters to keep an accurate count when exceptions are thrown during training. Use **`TRACKEH`**  to specify extra counters for an exact count. Use **`NOTRACKEH`**  to specify single counters for code that doesn't use exception handling or that doesn't run into exceptions in your training scenarios.  When you specify **`/GENPROFILE`**, the default is **`TRACKEH`** . When you specify **`/FASTGENPROFILE`**, the default is **`NOTRACKEH`** .
 
-**PGD**=*filename*<br/>
-Specifies a base file name for the .pgd file. By default, the linker uses the base executable image file name with a .pgd extension.
+**`PGD`**=*filename*\
+Specifies a base file name for the *`.pgd`* file. By default, the linker uses the base executable image file name with a *`.pgd`* extension.
 
 ## Remarks
 
-The **/GENPROFILE** and **/FASTGENPROFILE** options tell the linker to generate the profiling instrumentation file needed to support application training for profile-guided optimization (PGO). These options are new in Visual Studio 2015. Prefer these options to the deprecated **/LTCG:PGINSTRUMENT**, **/PGD** and **/POGOSAFEMODE** options and the **PogoSafeMode**, **VCPROFILE_ALLOC_SCALE** and **VCPROFILE_PATH** environment variables. The profiling information generated by application training is used as input to perform targeted whole-program optimizations during builds. You can set additional options to control various profiling features for performance during app training and builds. The default options specified by **/GENPROFILE** give most accurate results, especially for large, complex multi-threaded apps. The **/FASTGENPROFILE** option uses different defaults for a lower memory footprint and faster performance during training, at the expense of accuracy.
+The **`/GENPROFILE`** and **`/FASTGENPROFILE`** options tell the linker to generate the profiling instrumentation file needed to support application training for profile-guided optimization (PGO). These options are new in Visual Studio 2015. Prefer these options to the deprecated **`/LTCG:PGINSTRUMENT`**, **`/PGD`**, and **`/POGOSAFEMODE`** options, and to the **`PogoSafeMode`**, **`VCPROFILE_ALLOC_SCALE`**, and **`VCPROFILE_PATH`** environment variables. The profiling information generated by application training is used as input for targeted whole-program optimizations during builds. You can also set other options to control various profiling features for performance during app training and builds. The default options specified by **`/GENPROFILE`** give the most accurate results, especially for large, complex multi-threaded apps. The **`/FASTGENPROFILE`** option uses different defaults for a lower memory footprint and faster performance during training, at the expense of accuracy.
 
-Profiling information is captured when you run the instrumented app after you build by using **/GENPROFILE** of **/FASTGENPROFILE**. This information is captured when you specify the [/USEPROFILE](useprofile.md) linker option to perform the profiling step and then used to guide the optimized build step. For more information on how to train your app and details on the collected data, see [Profile-Guided Optimizations](../profile-guided-optimizations.md).
+Profiling information is captured when you run the instrumented app after you build by using **`/GENPROFILE`** of **`/FASTGENPROFILE`**. This information is captured when you specify the [`/USEPROFILE`](useprofile.md) linker option to do the profiling step and then used to guide the optimized build step. For more information on how to train your app and details on the collected data, see [Profile-guided optimizations](../profile-guided-optimizations.md).
 
-You must also specify **/LTCG** when you specify **/GENPROFILE** or **/FASTGENPROFILE**.
+Always specify **`/LTCG`** when you specify **`/GENPROFILE`** or **`/FASTGENPROFILE`**.
 
 ### To set this linker option in the Visual Studio development environment
 
 1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
 1. Select the **Configuration Properties** > **Linker** > **Command Line** property page.
 
-1. Enter the **/GENPROFILE** or **/FASTGENPROFILE** options and arguments into the **Additional Options** box. Choose **OK** to save your changes.
+1. Enter the **`/GENPROFILE`** or **`/FASTGENPROFILE`** options and arguments into the **Additional Options** box. Choose **`OK`** to save your changes.
 
 ### To set this linker option programmatically
 
 - See <xref:Microsoft.VisualStudio.VCProjectEngine.VCLinkerTool.AdditionalOptions%2A>.
 
 ## See also
 
-[MSVC linker reference](linking.md)<br/>
-[MSVC Linker Options](linker-options.md)<br/>
-[/LTCG (Link-time Code Generation)](ltcg-link-time-code-generation.md)<br/>
+[MSVC linker reference](linking.md)\
+[MSVC linker options](linker-options.md)\
+[`/LTCG` (Link-time code generation)](ltcg-link-time-code-generation.md)

docs/c-language/c-constant-expressions.md

@@ -1,40 +1,39 @@
 ---
 description: "Learn more about: C Constant Expressions"
 title: "C Constant Expressions"
-ms.date: "06/14/2018"
+ms.date: 04/14/2021
 helpviewer_keywords: ["constant expressions, syntax", "constant expressions", "expressions [C++], constant"]
-ms.assetid: d48a6c47-e44c-4be2-9c8b-7944c7ef8de7
 ---
 # C Constant Expressions
 
-A constant expression is evaluated at compile time, not run time, and can be used in any place that a constant can be used. The constant expression must evaluate to a constant that is in the range of representable values for that type. The operands of a constant expression can be integer constants, character constants, floating-point constants, enumeration constants, type casts, **`sizeof`** expressions, and other constant expressions.
+A constant expression gets evaluated at compile time, not run time, and can be used in any place that a constant can be used. The constant expression must evaluate to a constant that is in the range of representable values for that type. The operands of a constant expression can be integer constants, character constants, floating-point constants, enumeration constants, type casts, **`sizeof`** expressions, and other constant expressions.
 
 ## Syntax
 
-*constant-expression*:<br/>
-&nbsp;&nbsp;&nbsp;&nbsp;*conditional-expression*
+*`constant-expression`*:\
+&emsp;*`conditional-expression`*
 
-*conditional-expression*:<br/>
-&nbsp;&nbsp;&nbsp;&nbsp;*logical-OR-expression*<br/>
-&nbsp;&nbsp;&nbsp;&nbsp;*logical-OR-expression* **?** *expression* **:** *conditional-expression*
+*`conditional-expression`*:\
+&emsp;*`logical-OR-expression`*\
+&emsp;*`logical-OR-expression`* **`?`** *`expression`* **`:`** *`conditional-expression`*
 
-*expression*:<br/>
-&nbsp;&nbsp;&nbsp;&nbsp;*assignment-expression*<br/>
-&nbsp;&nbsp;&nbsp;&nbsp;*expression* **,** *assignment-expression*
+*`expression`*:\
+&emsp;*`assignment-expression`*\
+&emsp;*`expression`* **`,`** *`assignment-expression`*
 
-*assignment-expression*:<br/>
-&nbsp;&nbsp;&nbsp;&nbsp;*conditional-expression*<br/>
-&nbsp;&nbsp;&nbsp;&nbsp;*unary-expression* *assignment-operator* *assignment-expression*
+*`assignment-expression`*:\
+&emsp;*`conditional-expression`*\
+&emsp;*`unary-expression`* *`assignment-operator`* *`assignment-expression`*
 
-*assignment-operator*: one of<br/>
-&nbsp;&nbsp;&nbsp;&nbsp;**=** **&#42;=** **/=** **%=** **+=** **-=** **\<\<=** **>>=** **&=** **^=** **&#124;=**
+*`assignment-operator`*: one of\
+&emsp;**`=`** **`*=`** **`/=`** **`%=`** **`+=`** **`-=`** **`<<=`** **`>>=`** **`&=`** **`^=`** **`|=`**
 
-The nonterminals for struct declarator, enumerator, direct declarator, direct-abstract declarator, and labeled statement contain the *constant-expression* nonterminal.
+The nonterminals for struct declarator, enumerator, direct declarator, direct-abstract declarator, and labeled statement contain the *`constant-expression`* nonterminal.
 
 An integral constant expression must be used to specify the size of a bit-field member of a structure, the value of an enumeration constant, the size of an array, or the value of a **`case`** constant.
 
-Constant expressions used in preprocessor directives are subject to additional restrictions. Consequently, they are known as "restricted constant expressions." A restricted constant expression cannot contain **`sizeof`** expressions, enumeration constants, type casts to any type, or floating-type constants. It can, however, contain the special constant expression **defined (** _identifier_ **)**.
+Constant expressions used in preprocessor directives are subject to several restrictions. They're known as *restricted* constant expressions. A restricted constant expression can't contain **`sizeof`** expressions, enumeration constants, type casts to any type, or floating-type constants. It can, however, contain the special constant expression **`defined (`** _identifier_ **`)`**.
 
 ## See also
 
-- [Operands and Expressions](../c-language/operands-and-expressions.md)
+[Operands and Expressions](../c-language/operands-and-expressions.md)

docs/c-language/c-extended-storage-class-attributes.md

@@ -1,41 +1,40 @@
 ---
-description: "Learn more about: C Extended Storage-Class Attributes"
-title: "C Extended Storage-Class Attributes"
-ms.date: "11/04/2016"
+description: "Learn more about: C extended storage-class attributes"
+title: "C extended storage-class attributes"
+ms.date: 04/14/2021
 helpviewer_keywords: ["__declspec keyword [C]", "extended attributes", "extended storage-class attributes", "storage class specifiers, C storage classes"]
-ms.assetid: 2580735c-f5bf-46ab-9468-0696893d82be
 ---
-# C Extended Storage-Class Attributes
+# C extended storage-class attributes
 
 **Microsoft Specific**
 
-More up-to-date information on this topic can be found under [__declspec (C++ Reference)](../cpp/declspec.md).
+More up-to-date information on storage class attributes can be found under [`__declspec` (C++ Reference)](../cpp/declspec.md).
 
-Extended attribute syntax simplifies and standardizes the Microsoft-specific extensions to the C language. The storage-class attributes that use extended attribute syntax include thread, naked, dllimport, and dllexport.
+Extended attribute syntax simplifies and standardizes the Microsoft-specific extensions to the C language. The storage-class attributes that use extended attribute syntax include **`thread`**, **`naked`**, **`dllimport`**, and **`dllexport`**.
 
-The extended attribute syntax for specifying storage-class information uses the __declspec keyword, which specifies that an instance of a given type is to be stored with a Microsoft-specific storage-class attribute (thread, naked, dllimport, or dllexport). Examples of other storage-class modifiers include the static and extern keywords. However, these keywords are part of the ANSI C standard and as such are not covered by extended attribute syntax.
+The extended attribute syntax for specifying storage-class information uses the **`__declspec`** keyword, which specifies that an instance of a given type is to be stored with a Microsoft-specific storage-class attribute (**`thread`**, **`naked`**, **`dllimport`**, or **`dllexport`**). Examples of other storage-class modifiers include the **`static`** and **`extern`** keywords. However, these keywords are part of the ISO C standard and aren't covered by extended attribute syntax.
 
 ## Syntax
 
-*storage-class-specifier*:<br/>
-&nbsp;&nbsp;&nbsp;&nbsp;**__declspec (** *extended-decl-modifier-seq* **)** /\* Microsoft-specific \*/
+*`storage-class-specifier`*:<br/>
+&emsp;**`__declspec (`** *`extended-decl-modifier-seq`* **`)`** /\* Microsoft-specific \*/
 
-*extended-decl-modifier-seq*:&nbsp;&nbsp;&nbsp;&nbsp;/\* Microsoft-specific \*/<br/>
-&nbsp;&nbsp;&nbsp;&nbsp;*extended-decl-modifier*<sub>opt</sub><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;*extended-decl-modifier-seq* *extended-decl-modifier*
+*`extended-decl-modifier-seq`*:&emsp;/\* Microsoft-specific \*/<br/>
+&emsp;*`extended-decl-modifier`*<sub>opt</sub><br/>
+&emsp;*`extended-decl-modifier-seq`* *`extended-decl-modifier`*
 
-*extended-decl-modifier*:&nbsp;&nbsp;&nbsp;&nbsp;/\* Microsoft-specific \*/<br/>
-&nbsp;&nbsp;&nbsp;&nbsp;**`thread`**<br/>
-&nbsp;&nbsp;&nbsp;&nbsp;**`naked`**<br/>
-&nbsp;&nbsp;&nbsp;&nbsp;**`dllimport`**<br/>
-&nbsp;&nbsp;&nbsp;&nbsp;**`dllexport`**
+*`extended-decl-modifier`*:&emsp;/\* Microsoft-specific \*/<br/>
+&emsp;**`thread`**<br/>
+&emsp;**`naked`**<br/>
+&emsp;**`dllimport`**<br/>
+&emsp;**`dllexport`**
 
-White space separates the declaration modifiers. Note that *extended-decl-modifier-seq* can be empty; in this case, __declspec has no effect.
+White space separates the declaration modifiers. An *`extended-decl-modifier-seq`* can be empty; in this case, **`__declspec`** has no effect.
 
-The thread, naked, dllimport, and dllexport storage-class attributes are a property only of the declaration of the data or function to which they are applied; they do not redefine the type attributes of the function itself. The thread attribute affects data only. The naked attribute affects functions only. The dllimport and dllexport attributes affect functions and data.
+The **`thread`**, **`naked`**, **`dllimport`**, and **`dllexport`** storage-class attributes are a property only of the declaration of the data or function to which they're applied. They don't redefine the type attributes of the function itself. The **`thread`** attribute affects data only. The **`naked`** attribute affects functions only. The **`dllimport`** and **`dllexport`** attributes affect functions and data.
 
 **END Microsoft Specific**
 
 ## See also
 
-[Declarations and Types](../c-language/declarations-and-types.md)
+[Declarations and types](../c-language/declarations-and-types.md)