@@ -23,20 +23,22 @@ textsection
 ", function1, ... )  
 ```  
 
-## Remarks  
- The **alloc_text** pragma does not handle C++ member functions or overloaded functions. It is applicable only to functions declared with C linkage — that is, functions declared with the **extern "C"** linkage specification. If you attempt to use this pragma on a function with C++ linkage, a compiler error is generated.  
+## Remarks 
+
+The **alloc_text** pragma does not handle C++ member functions or overloaded functions. It is applicable only to functions declared with C linkage — that is, functions declared with the **extern "C"** linkage specification. If you attempt to use this pragma on a function with C++ linkage, a compiler error is generated.  
 
- Since function addressing using `__based` is not supported, specifying section locations requires the use of the **alloc_text** pragma. The name specified by *textsection* should be enclosed in double quotation marks.  
+Since function addressing using `__based` is not supported, specifying section locations requires the use of the **alloc_text** pragma. The name specified by *textsection* should be enclosed in double quotation marks.  
 
- The **alloc_text** pragma must appear after the declarations of any of the specified functions and before the definitions of these functions.  
+The **alloc_text** pragma must appear after the declarations of any of the specified functions and before the definitions of these functions.  
 
- Functions referenced in an **alloc_text** pragma should be defined in the same module as the pragma. If this is not done and an undefined function is later compiled into a different text section, the error may or may not be caught. Although the program will usually run correctly, the function will not be allocated in the intended sections.  
+Functions referenced in an **alloc_text** pragma should be defined in the same module as the pragma. If this is not done and an undefined function is later compiled into a different text section, the error may or may not be caught. Although the program will usually run correctly, the function will not be allocated in the intended sections.  
 
- Other limitations on **alloc_text** are as follows:  
+Other limitations on **alloc_text** are as follows:  
 
--   It cannot be used inside a function.  
+- It cannot be used inside a function.  
 
--   It must be used after the function has been declared, but before the function has been defined.  
+- It must be used after the function has been declared, but before the function has been defined.  
 
-## See Also  
- [Pragma Directives and the __Pragma Keyword](../preprocessor/pragma-directives-and-the-pragma-keyword.md)
+## See Also 
+
+[Pragma Directives and the __Pragma Keyword](../preprocessor/pragma-directives-and-the-pragma-keyword.md)
@@ -22,7 +22,9 @@ Excludes any functions defined within the range where **off** is specified from
 ```  
 
 ## Remarks  
- To use the **auto_inline** pragma, place it before and immediately after (not in) a function definition. The pragma takes effect at the first function definition after the pragma is seen.  
+
+To use the **auto_inline** pragma, place it before and immediately after (not in) a function definition. The pragma takes effect at the first function definition after the pragma is seen.  
 
-## See Also  
- [Pragma Directives and the __Pragma Keyword](../preprocessor/pragma-directives-and-the-pragma-keyword.md)
+## See Also
+
+[Pragma Directives and the __Pragma Keyword](../preprocessor/pragma-directives-and-the-pragma-keyword.md)
@@ -15,19 +15,21 @@ ms.workload: ["cplusplus"]
 # auto_rename
 **C++ Specific**  
 
- Renames C++ reserved words by appending two underscores (__) to the variable name to resolve potential name conflicts.  
+Renames C++ reserved words by appending two underscores (__) to the variable name to resolve potential name conflicts.  
 
 ## Syntax  
 
 ```  
 auto_rename  
 ```  
 
-## Remarks  
- This attribute is used when importing a type library that uses one or more C++ reserved words (keywords or macros) as variable names.  
+## Remarks 
+
+This attribute is used when importing a type library that uses one or more C++ reserved words (keywords or macros) as variable names.  
 
  **END C++ Specific**  
 
-## See Also  
- [#import Attributes](../preprocessor/hash-import-attributes-cpp.md)   
- [#import Directive](../preprocessor/hash-import-directive-cpp.md)
+## See Also 
+
+[#import Attributes](../preprocessor/hash-import-attributes-cpp.md)   
+[#import Directive](../preprocessor/hash-import-directive-cpp.md)
@@ -15,7 +15,7 @@ ms.workload: ["cplusplus"]
 # auto_search
 **C++ Specific**  
 
- Specifies that, when a type library is referenced with `#import` and itself references another type library, the compiler can do an implicit `#import` for the other type library.  
+Specifies that, when a type library is referenced with `#import` and itself references another type library, the compiler can do an implicit `#import` for the other type library.  
 
 ## Syntax  
 
@@ -26,6 +26,7 @@ auto_search
 ## Remarks  
  **END C++ Specific**  
 
-## See Also  
- [#import Attributes](../preprocessor/hash-import-attributes-cpp.md)   
- [#import Directive](../preprocessor/hash-import-directive-cpp.md)
+## See Also 
+
+[#import Attributes](../preprocessor/hash-import-attributes-cpp.md)   
+[#import Directive](../preprocessor/hash-import-directive-cpp.md)
@@ -22,26 +22,27 @@ Specifies the segment where uninitialized variables are stored in the .obj file.
 ```  
 
 ## Remarks  
- Obj files can be viewed with the [dumpbin](../build/reference/dumpbin-command-line.md) application. The default segment in the .obj file for uninitialized data is .bss. In some cases use of **bss_seg** can speed load times by grouping uninitialized data into one section.  
+ 
+Obj files can be viewed with the [dumpbin](../build/reference/dumpbin-command-line.md) application. The default segment in the .obj file for uninitialized data is .bss. In some cases use of **bss_seg** can speed load times by grouping uninitialized data into one section.  
 
- **bss_seg** with no parameters resets the segment to .bss.  
+**bss_seg** with no parameters resets the segment to .bss.  
 
- *push* (optional)  
- Puts a record on the internal compiler stack. A *push* can have an *identifier* and *segment-name*.  
+*push* (optional)  
+Puts a record on the internal compiler stack. A *push* can have an *identifier* and *segment-name*.  
 
- *pop* (optional)  
- Removes a record from the top of the internal compiler stack.  
+*pop* (optional)  
+Removes a record from the top of the internal compiler stack.  
 
- *identifier* (optional)  
- When used with *push*, assigns a name to the record on the internal compiler stack. When used with *pop*, pops records off the internal stack until *identifier* is removed; if *identifier* is not found on the internal stack, nothing is popped.  
+*identifier* (optional)  
+When used with *push*, assigns a name to the record on the internal compiler stack. When used with *pop*, pops records off the internal stack until *identifier* is removed; if *identifier* is not found on the internal stack, nothing is popped.  
 
- *identifier* enables multiple records to be popped with a single *pop* command.  
+*identifier* enables multiple records to be popped with a single *pop* command.  
 
- *"segment-name"*(optional)  
- The name of a segment. When used with *pop*, the stack is popped and *segment-name* becomes the active segment name.  
+*"segment-name"*(optional)  
+The name of a segment. When used with *pop*, the stack is popped and *segment-name* becomes the active segment name.  
 
- *"segment-class"* (optional)  
- Included for compatibility with C++ prior to version 2.0. It is ignored.  
+*"segment-class"* (optional)  
+Included for compatibility with C++ prior to version 2.0. It is ignored.  
 
 ## Example  
 
@@ -61,11 +62,12 @@ int main() {
 }  
 ```  
 
- You can also specify sections for initialized data ([data_seg](../preprocessor/data-seg.md)), functions ([code_seg](../preprocessor/code-seg.md)), and const variables ([const_seg](../preprocessor/const-seg.md)).  
+You can also specify sections for initialized data ([data_seg](../preprocessor/data-seg.md)), functions ([code_seg](../preprocessor/code-seg.md)), and const variables ([const_seg](../preprocessor/const-seg.md)).  
 
- Data allocated using the **bss_seg** pragma does not retain any information about its location.  
+Data allocated using the **bss_seg** pragma does not retain any information about its location.  
 
- See [/SECTION](../build/reference/section-specify-section-attributes.md) for a list of names you should not use when creating a section.  
+See [/SECTION](../build/reference/section-specify-section-attributes.md) for a list of names you should not use when creating a section.  
 
 ## See Also  
- [Pragma Directives and the __Pragma Keyword](../preprocessor/pragma-directives-and-the-pragma-keyword.md)
+ 
+[Pragma Directives and the __Pragma Keyword](../preprocessor/pragma-directives-and-the-pragma-keyword.md)
@@ -15,27 +15,29 @@ ms.workload: ["cplusplus"]
 The *C/C++ Preprocessor Reference* explains the preprocessor as it is implemented in Microsoft C/C++. The preprocessor performs preliminary operations on C and C++ files before they are passed to the compiler. You can use the preprocessor to conditionally compile code, insert files, specify compile-time error messages, and apply machine-specific rules to sections of code.  
 
 ## In This Section  
- [Preprocessor Directives](../preprocessor/preprocessor-directives.md)  
- Describes directives, typically used to make source programs easy to change and easy to compile in different execution environments.  
+ 
+[Preprocessor Directives](../preprocessor/preprocessor-directives.md)  
+Describes directives, typically used to make source programs easy to change and easy to compile in different execution environments.  
 
- [Preprocessor Operators](../preprocessor/preprocessor-operators.md)  
- Discusses the four preprocessor-specific operators used in the context of the `#define` directive.  
+[Preprocessor Operators](../preprocessor/preprocessor-operators.md)  
+Discusses the four preprocessor-specific operators used in the context of the `#define` directive.  
 
- [Predefined Macros](../preprocessor/predefined-macros.md)  
- Discusses predefined macros as specified by ANSI and Microsoft C++.  
+[Predefined Macros](../preprocessor/predefined-macros.md)  
+Discusses predefined macros as specified by ANSI and Microsoft C++.  
 
- [Pragmas](../preprocessor/pragma-directives-and-the-pragma-keyword.md)  
- Discusses pragmas, which offer a way for each compiler to offer machine- and operating system-specific features while retaining overall compatibility with the C and C++ languages.  
+[Pragmas](../preprocessor/pragma-directives-and-the-pragma-keyword.md)  
+Discusses pragmas, which offer a way for each compiler to offer machine- and operating system-specific features while retaining overall compatibility with the C and C++ languages.  
 
 ## Related Sections  
- [C++ Language Reference](../cpp/cpp-language-reference.md)  
- Provides reference material for the Microsoft implementation of the C++ language.  
+ 
+[C++ Language Reference](../cpp/cpp-language-reference.md)  
+Provides reference material for the Microsoft implementation of the C++ language.  
 
- [C Language Reference](../c-language/c-language-reference.md)  
- Provides reference material for the Microsoft implementation of the C language.  
+[C Language Reference](../c-language/c-language-reference.md)  
+Provides reference material for the Microsoft implementation of the C language.  
 
- [Building a C/C++ Program](../build/reference/c-cpp-building-reference.md)  
- Provides links to topics discussing compiler and linker options.  
+[Building a C/C++ Program](../build/reference/c-cpp-building-reference.md)  
+Provides links to topics discussing compiler and linker options.  
 
- [Creating and Managing Visual C++ Projects](../ide/creating-and-managing-visual-cpp-projects.md)  
- Describes the user interface in Visual Studio that enables you to specify the directories that the project system will search to locate files for your C++ project.
+[Creating and Managing Visual C++ Projects](../ide/creating-and-managing-visual-cpp-projects.md)  
+Describes the user interface in Visual Studio that enables you to specify the directories that the project system will search to locate files for your C++ project.
@@ -15,27 +15,28 @@ ms.workload: ["cplusplus"]
 # Charizing Operator (#@)
 **Microsoft Specific**  
 
- The charizing operator can be used only with arguments of macros. If `#@` precedes a formal parameter in the definition of the macro, the actual argument is enclosed in single quotation marks and treated as a character when the macro is expanded. For example:  
+The charizing operator can be used only with arguments of macros. If `#@` precedes a formal parameter in the definition of the macro, the actual argument is enclosed in single quotation marks and treated as a character when the macro is expanded. For example:  
 
 ```  
 #define makechar(x)  #@x  
 ```  
 
- causes the statement  
+causes the statement  
 
 ```  
 a = makechar(b);  
 ```  
 
- to be expanded to  
+to be expanded to  
 
 ```  
 a = 'b';  
 ```  
 
- The single-quotation character cannot be used with the charizing operator.  
+The single-quotation character cannot be used with the charizing operator.  
 
- **END Microsoft Specific**  
+**END Microsoft Specific**  
 
 ## See Also  
- [Preprocessor Operators](../preprocessor/preprocessor-operators.md)
+ 
+[Preprocessor Operators](../preprocessor/preprocessor-operators.md)
@@ -22,10 +22,11 @@ Instructs the compiler to turn off stack probes if `off` (or `-`) is specified,
 #pragma check_stack{+ | -}  
 ```  
 
-## Remarks  
- If no argument is given, stack probes are treated according to the default. This pragma takes effect at the first function defined after the pragma is seen. Stack probes are neither a part of macros nor of functions that are generated inline.  
+## Remarks 
+
+If no argument is given, stack probes are treated according to the default. This pragma takes effect at the first function defined after the pragma is seen. Stack probes are neither a part of macros nor of functions that are generated inline.  
 
- If you don't give an argument for the **check_stack** pragma, stack checking reverts to the behavior specified on the command line. For more information, see [Compiler Reference](../build/reference/compiler-options.md). The interaction of the `#pragma check_stack` and the [/Gs](../build/reference/gs-control-stack-checking-calls.md) option is summarized in the following table.  
+If you don't give an argument for the **check_stack** pragma, stack checking reverts to the behavior specified on the command line. For more information, see [Compiler Reference](../build/reference/compiler-options.md). The interaction of the `#pragma check_stack` and the [/Gs](../build/reference/gs-control-stack-checking-calls.md) option is summarized in the following table.  
 
 ### Using the check_stack Pragma  
 
@@ -37,4 +38,5 @@ Instructs the compiler to turn off stack probes if `off` (or `-`) is specified,
 |`#pragma check_stack(off)`<br /><br /> or `#pragma check_stack -`|Yes or No|Turns off stack checking for functions that follow|  
 
 ## See Also  
- [Pragma Directives and the __Pragma Keyword](../preprocessor/pragma-directives-and-the-pragma-keyword.md)
+ 
+[Pragma Directives and the __Pragma Keyword](../preprocessor/pragma-directives-and-the-pragma-keyword.md)