Merge pull request #1231 from msebolt/preprocessor-formatting-review-pr2

preprocessor formatting review pr2

Author: rmca14

docs/preprocessor/hash-import-attributes-cpp.md

@@ -12,11 +12,11 @@ ms.author: "corob"
 ms.workload: ["cplusplus"]
 ---
 # #import Attributes (C++)
-Provides links to attributes used with the #import directive.  
+Provides links to attributes used with the `#import` directive.  
 
- **Microsoft Specific**  
+**Microsoft Specific**  
 
- The following attributes are available to the #import directive.  
+The following attributes are available to the `#import` directive.  
 
 |Attribute|Description|  
 |---------------|-----------------|  
@@ -29,15 +29,15 @@ Provides links to attributes used with the #import directive.
 |[implementation_only](../preprocessor/implementation-only.md)|Suppresses the generation of the .tlh header file (the primary header file).|  
 |[include()](../preprocessor/include-parens.md)|Disables automatic exclusion.|  
 |[inject_statement](../preprocessor/inject-statement.md)|Inserts its argument as source text into the type-library header.|  
-|[named_guids](../preprocessor/named-guids.md)|Tells the compiler to define and initialize GUID variables in old style, of the form **LIBID_MyLib**, **CLSID_MyCoClass**, **IID_MyInterface**, and **DIID_MyDispInterface**.|  
+|[named_guids](../preprocessor/named-guids.md)|Tells the compiler to define and initialize GUID variables in old style, of the form `LIBID_MyLib`, `CLSID_MyCoClass`, `IID_MyInterface`, and `DIID_MyDispInterface`.|  
 |[no_auto_exclude](../preprocessor/no-auto-exclude.md)|Disables automatic exclusion.|  
 |[no_dual_interfaces](../preprocessor/no-dual-interfaces.md)|Changes the way the compiler generates wrapper functions for dual interface methods.|  
 |[no_implementation](../preprocessor/no-implementation.md)|Suppresses the generation of the .tli header, which contains the implementations of the wrapper member functions.|  
 |[no_namespace](../preprocessor/no-namespace.md)|Specifies that the namespace name is not generated by the compiler.|  
 |[no_registry](../preprocessor/no-registry.md)|Tells the compiler not to search the registry for type libraries.|  
 |[no_search_namespace](../preprocessor/no-search-namespace.md)|Has the same functionality as the [no_namespace](../preprocessor/no-namespace.md) attribute but is used on type libraries that you use the #import directive with the [auto_search](../preprocessor/auto-search.md) attribute.|  
 |[no_smart_pointers](../preprocessor/no-smart-pointers.md)|Suppresses the creation of smart pointers for all interfaces in the type library.|  
-|[raw_dispinterfaces](../preprocessor/raw-dispinterfaces.md)|Tells the compiler to generate low-level wrapper functions for dispinterface methods and properties that call **IDispatch::Invoke** and return the `HRESULT` error code.|  
+|[raw_dispinterfaces](../preprocessor/raw-dispinterfaces.md)|Tells the compiler to generate low-level wrapper functions for dispinterface methods and properties that call `IDispatch::Invoke` and return the HRESULT error code.|  
 |[raw_interfaces_only](../preprocessor/raw-interfaces-only.md)|Suppresses the generation of error-handling wrapper functions and [property](../cpp/property-cpp.md) declarations that use those wrapper functions.|  
 |[raw_method_prefix](../preprocessor/raw-method-prefix.md)|Specifies a different prefix to avoid name collisions.|  
 |[raw_native_types](../preprocessor/raw-native-types.md)|Disables the use of COM support classes in the high-level wrapper functions and forces the use of low-level data types instead.|  
@@ -47,7 +47,8 @@ Provides links to attributes used with the #import directive.
 |[rename_search_namespace](../preprocessor/rename-search-namespace.md)|Has the same functionality as the [rename_namespace](../preprocessor/rename-namespace.md) attribute but is used on type libraries that you use the #import directive with the [auto_search](../preprocessor/auto-search.md) attribute.|  
 |[tlbid](../preprocessor/tlbid.md)|Allows for loading libraries other than the primary type library.|  
 
- **END Microsoft Specific**  
+**END Microsoft Specific**  
 
 ## See Also  
- [#import Directive](../preprocessor/hash-import-directive-cpp.md)
+ 
+[#import Directive](../preprocessor/hash-import-directive-cpp.md)

docs/preprocessor/hash-import-directive-cpp.md

@@ -18,77 +18,78 @@ Tells the preprocessor to treat the contents of a specified file as if they appe
 ## Syntax  
 
 ```  
-  
-      #include  "path-spec"  
+#include  "path-spec"  
 #include  <path-spec>  
 ```  
 
-## Remarks  
- You can organize constant and macro definitions into include files and then use `#include` directives to add them to any source file. Include files are also useful for incorporating declarations of external variables and complex data types. The types may be defined and named only once in an include file created for that purpose.  
+## Remarks 
+
+You can organize constant and macro definitions into include files and then use **#include** directives to add them to any source file. Include files are also useful for incorporating declarations of external variables and complex data types. The types may be defined and named only once in an include file created for that purpose.  
 
- The `path-spec` is a file name that may optionally be preceded by a directory specification. The file name must name an existing file. The syntax of the `path-spec` depends on the operating system on which the program is compiled.  
+The `path-spec` is a file name that may optionally be preceded by a directory specification. The file name must name an existing file. The syntax of the `path-spec` depends on the operating system on which the program is compiled.  
 
- For information about how to reference assemblies in a C++ application that's compiled by using [/clr](../build/reference/clr-common-language-runtime-compilation.md), see [#using](../preprocessor/hash-using-directive-cpp.md).  
+For information about how to reference assemblies in a C++ application that's compiled by using [/clr](../build/reference/clr-common-language-runtime-compilation.md), see [#using](../preprocessor/hash-using-directive-cpp.md).  
 
- Both syntax forms cause that directive to be replaced by the entire contents of the specified include file. The difference between the two forms is the order in which the preprocessor searches for header files when the path is incompletely specified. The following table shows the difference between the two syntax forms.  
+Both syntax forms cause that directive to be replaced by the entire contents of the specified include file. The difference between the two forms is the order in which the preprocessor searches for header files when the path is incompletely specified. The following table shows the difference between the two syntax forms.  
 
 |Syntax Form|Action|  
 |-----------------|------------|  
-|Quoted form|The preprocessor searches for include files in this order:<br /><br /> 1) In the same directory as the file that contains the `#include` statement.<br /><br /> 2) In the directories of the currently opened include files, in the reverse order in which they were opened. The search begins in the directory of the parent include file and continues upward through the directories of any grandparent include files.<br /><br /> 3) Along the path that's specified by each /I compiler option.<br /><br /> 4)<br /><br /> Along the paths that are specified by the INCLUDE environment variable.|  
-|Angle-bracket form|The preprocessor searches for include files in this order:<br /><br /> 1) Along the path that's specified by each /I compiler option.<br /><br /> 2) When compiling occurs on the command line, along the paths that are specified by the INCLUDE environment variable.|  
+|Quoted form|The preprocessor searches for include files in this order:<br /><br /> 1) In the same directory as the file that contains the **#include** statement.<br /><br /> 2) In the directories of the currently opened include files, in the reverse order in which they were opened. The search begins in the directory of the parent include file and continues upward through the directories of any grandparent include files.<br /><br /> 3) Along the path that's specified by each `/I` compiler option.<br /><br /> 4)<br /><br /> Along the paths that are specified by the INCLUDE environment variable.|  
+|Angle-bracket form|The preprocessor searches for include files in this order:<br /><br /> 1) Along the path that's specified by each `/I` compiler option.<br /><br /> 2) When compiling occurs on the command line, along the paths that are specified by the INCLUDE environment variable.|  
 
- The preprocessor stops searching as soon as it finds a file that has the given name. If you enclose a complete, unambiguous path specification for the include file between double quotation marks (" "), the preprocessor searches only that path specification and ignores the standard directories.  
+The preprocessor stops searching as soon as it finds a file that has the given name. If you enclose a complete, unambiguous path specification for the include file between double quotation marks (" "), the preprocessor searches only that path specification and ignores the standard directories.  
 
- If the file name that's enclosed in double quotation marks is an incomplete path specification, the preprocessor first searches the "parent" file's directory. A parent file is the file that contains the `#include` directive. For example, if you include a file named `file2` in a file named `file1`, `file1` is the parent file.  
+If the file name that's enclosed in double quotation marks is an incomplete path specification, the preprocessor first searches the "parent" file's directory. A parent file is the file that contains the **#include** directive. For example, if you include a file named `file2` in a file named `file1`, `file1` is the parent file.  
 
- Include files can be "nested"; that is, an `#include` directive can appear in a file that's named by another `#include` directive. For example, `file2` could include `file3`. In this case, `file1` would still be the parent of `file2`, but it would be the "grandparent" of `file3`.  
+Include files can be "nested"; that is, an **#include** directive can appear in a file that's named by another **#include** directive. For example, `file2` could include `file3`. In this case, `file1` would still be the parent of `file2`, but it would be the "grandparent" of `file3`.  
 
- When include files are nested and when compiling occurs on the command line, directory searching begins with the directories of the parent file and then proceeds through the directories of any grandparent files. That is, searching begins relative to the directory that contains the source that's currently being processed. If the file is not found, the search moves to directories that are specified by the /I compiler option. Finally, the directories that are specified by the INCLUDE environment variable are searched.  
+When include files are nested and when compiling occurs on the command line, directory searching begins with the directories of the parent file and then proceeds through the directories of any grandparent files. That is, searching begins relative to the directory that contains the source that's currently being processed. If the file is not found, the search moves to directories that are specified by the `/I` compiler option. Finally, the directories that are specified by the INCLUDE environment variable are searched.  
 
- From the development environment, the INCLUDE environment variable is ignored. For information about how to set the directories that are searched for include files—this also applies to the LIB environment variable—see [VC++ Directories Property Page](../ide/vcpp-directories-property-page.md).  
+From the development environment, the INCLUDE environment variable is ignored. For information about how to set the directories that are searched for include files—this also applies to the LIB environment variable—see [VC++ Directories Property Page](../ide/vcpp-directories-property-page.md).  
 
- This example shows file inclusion by using angle brackets:  
+This example shows file inclusion by using angle brackets:  
 
 ```  
 #include <stdio.h>  
 ```  
 
- This example adds the contents of the file named STDIO.H to the source program. The angle brackets cause the preprocessor to search the directories that are specified by the INCLUDE environment variable for STDIO.H, after it searches directories that are specified by the /I compiler option.  
+This example adds the contents of the file named STDIO.H to the source program. The angle brackets cause the preprocessor to search the directories that are specified by the INCLUDE environment variable for STDIO.H, after it searches directories that are specified by the `/I` compiler option.  
 
- The next example shows file inclusion by using the quoted form:  
+The next example shows file inclusion by using the quoted form:  
 
 ```  
 #include "defs.h"  
 ```  
 
- This example adds the contents of the file that's specified by DEFS.H to the source program. The quotation marks mean that the preprocessor first searches the directory that contains the parent source file.  
+This example adds the contents of the file that's specified by DEFS.H to the source program. The quotation marks mean that the preprocessor first searches the directory that contains the parent source file.  
 
- Nesting of include files can continue up to 10 levels. When the nested `#include` is processed, the preprocessor continues to insert the enclosing include file into the original source file.  
+Nesting of include files can continue up to 10 levels. When the nested **#include** is processed, the preprocessor continues to insert the enclosing include file into the original source file.  
 
- **Microsoft Specific**  
+**Microsoft Specific**  
 
- To locate includable source files, the preprocessor first searches the directories that are specified by the /I compiler option. If the /I option is not present or fails, the preprocessor uses the INCLUDE environment variable to find any include files within angle brackets. The INCLUDE environment variable and /I compiler option can contain multiple paths, separated by semicolons (;). If more than one directory appears as part of the /I option or within the INCLUDE environment variable, the preprocessor searches them in the order in which they appear.  
+To locate includable source files, the preprocessor first searches the directories that are specified by the `/I` compiler option. If the `/I` option is not present or fails, the preprocessor uses the INCLUDE environment variable to find any include files within angle brackets. The INCLUDE environment variable and `/I` compiler option can contain multiple paths, separated by semicolons (;). If more than one directory appears as part of the `/I` option or within the INCLUDE environment variable, the preprocessor searches them in the order in which they appear.  
 
- For example, the command  
+For example, the command  
 
 ```  
 CL /ID:\MSVC\INCLUDE MYPROG.C  
 ```  
 
- causes the preprocessor to search the directory D:\MSVC\INCLUDE\ for include files such as STDIO.H. The commands  
+causes the preprocessor to search the directory D:\MSVC\INCLUDE\ for include files such as STDIO.H. The commands  
 
 ```  
 SET INCLUDE=D:\MSVC\INCLUDE  
 CL MYPROG.C  
 ```  
 
- have the same effect. If both sets of searches fail, a fatal compiler error is generated.  
+have the same effect. If both sets of searches fail, a fatal compiler error is generated.  
 
- If the file name is fully specified for an include file that has a path that includes a colon (for example, F:\MSVC\SPECIAL\INCL\TEST.H), the preprocessor follows the path.  
+If the file name is fully specified for an include file that has a path that includes a colon (for example, F:\MSVC\SPECIAL\INCL\TEST.H), the preprocessor follows the path.  
 
- For include files that are specified as `#include` "`path-spec`", directory searching begins with the directory of the parent file and then proceeds through the directories of any grandparent files. That is, searching begins relative to the directory that contains the source file that contains the `#include` directive that's being processed. If there is no grandparent file and the file has not been found, the search continues as if the file name were enclosed in angle brackets.  
+For include files that are specified as `#include` "`path-spec`", directory searching begins with the directory of the parent file and then proceeds through the directories of any grandparent files. That is, searching begins relative to the directory that contains the source file that contains the **#include** directive that's being processed. If there is no grandparent file and the file has not been found, the search continues as if the file name were enclosed in angle brackets.  
 
- **END Microsoft Specific**  
+**END Microsoft Specific**  
 
 ## See Also  
- [Preprocessor Directives](../preprocessor/preprocessor-directives.md)
+ 
+[Preprocessor Directives](../preprocessor/preprocessor-directives.md)