fixed up header name casing and added angle brackets (MicrosoftDocs#549)

mikeblome · web-flow · commit 667a90d33216 · 2018-01-24T12:04:22.000-08:00
* changed header names to lower case in cpp folder

* added angle brackets to header names in cpp folder

* Update event-handling-in-native-cpp.md

fixed oops.

* Update event-handling-in-native-cpp.md

Fix a missing newline, put spaces around headings
diff --git a/docs/cpp/abort-function.md b/docs/cpp/abort-function.md
@@ -18,7 +18,7 @@ ms.workload: ["cplusplus"]
 ---
 # abort Function
 
-The **abort** function, also declared in the standard include file STDLIB.H, terminates a C++ program. The difference between **exit** and **abort** is that **exit** allows the C++ run-time termination processing to take place (global object destructors will be called), whereas **abort** terminates the program immediately. For more information, see [abort](../c-runtime-library/reference/abort.md) in the *Run-Time Library Reference*.
+The **abort** function, also declared in the standard include file \<stdlib.h>, terminates a C++ program. The difference between **exit** and **abort** is that **exit** allows the C++ run-time termination processing to take place (global object destructors will be called), whereas **abort** terminates the program immediately. For more information, see [abort](../c-runtime-library/reference/abort.md) in the *Run-Time Library Reference*.
 
 ## See also
 
diff --git a/docs/cpp/additive-operators-plus-and.md b/docs/cpp/additive-operators-plus-and.md
@@ -103,7 +103,7 @@ for( int i = 0; i < 10; ++i )
 >  Code of the form `pIntArray = pIntArray + 1` is rarely found in C++ programs; to perform an increment, these forms are preferable: `pIntArray++` or `pIntArray += 1`.  
   
 ## Pointer subtraction  
- If both operands are pointers, the result of subtraction is the difference (in array elements) between the operands. The subtraction expression yields a signed integral result of type ptrdiff_t (defined in the standard include file STDDEF.H).  
+ If both operands are pointers, the result of subtraction is the difference (in array elements) between the operands. The subtraction expression yields a signed integral result of type ptrdiff_t (defined in the standard include file \<stddef.h>).  
   
  One of the operands can be of integral type, as long as it is the second operand. The result of the subtraction is of the same type as the original pointer. The value of the subtraction is a pointer to the (*n* - *i*)th array element, where *n* is the element pointed to by the original pointer and *i* is the integral value of the second operand.  
   
diff --git a/docs/cpp/bstr-t-class.md b/docs/cpp/bstr-t-class.md
@@ -54,7 +54,7 @@ ms.workload: ["cplusplus"]
 **END Microsoft Specific**  
   
 ## Requirements  
- **Header:** comutil.h  
+ **Header:** \<comutil.h>  
   
  **Lib:** comsuppw.lib or comsuppwd.lib (see [/Zc:wchar_t (wchar_t Is Native Type)](../build/reference/zc-wchar-t-wchar-t-is-native-type.md) for more information)  
   
diff --git a/docs/cpp/com-error-class.md b/docs/cpp/com-error-class.md
@@ -68,7 +68,7 @@ ms.workload: ["cplusplus"]
 **END Microsoft Specific**  
   
 ## Requirements  
- **Header:** comdef.h  
+ **Header:** \<comdef.h>  
   
  `Lib:` comsuppw.lib or comsuppwd.lib (see [/Zc:wchar_t (wchar_t Is Native Type)](../build/reference/zc-wchar-t-wchar-t-is-native-type.md) for more information)  
   
diff --git a/docs/cpp/com-ptr-t-class.md b/docs/cpp/com-ptr-t-class.md
@@ -62,7 +62,7 @@ _COM_SMARTPTR_TYPEDEF(IMyInterface, __uuidof(IMyInterface));
 **END Microsoft Specific**  
   
 ## Requirements  
- **Header:** comip.h  
+ **Header:** \<comip.h>  
   
  **Lib:** comsuppw.lib or comsuppwd.lib (see [/Zc:wchar_t (wchar_t Is Native Type)](../build/reference/zc-wchar-t-wchar-t-is-native-type.md) for more information)  
   
diff --git a/docs/cpp/com-raise-error.md b/docs/cpp/com-raise-error.md
@@ -40,7 +40,7 @@ ms.workload: ["cplusplus"]
  **IErrorInfo** object.  
   
 ## Remarks  
- `_com_raise_error`, which is defined in comdef.h, can be replaced by a user-written version of the same name and prototype. This could be done if you want to use `#import` but do not want to use C++ exception handling. In that case, a user version of **_com_raise_error** might decide to do a `longjmp` or display a message box and halt. The user version should not return, though, because the compiler COM support code does not expect it to return.  
+ `_com_raise_error`, which is defined in \<comdef.h>, can be replaced by a user-written version of the same name and prototype. This could be done if you want to use `#import` but do not want to use C++ exception handling. In that case, a user version of **_com_raise_error** might decide to do a `longjmp` or display a message box and halt. The user version should not return, though, because the compiler COM support code does not expect it to return.  
   
  You can also use [_set_com_error_handler](../cpp/set-com-error-handler.md) to replace the default error-handling function.  
   
@@ -55,7 +55,7 @@ void __stdcall _com_raise_error(HRESULT hr, IErrorInfo* perrinfo) {
 **END Microsoft Specific**  
   
 ## Requirements  
- **Header:** comdef.h  
+ **Header:** \<comdef.h>  
   
  **Lib:** If the **wchar_t is Native Type** compiler option is on, use comsuppw.lib or comsuppwd.lib. If **wchar_t is Native Type** is off, use comsupp.lib. For more information, see [/Zc:wchar_t (wchar_t Is Native Type)](../build/reference/zc-wchar-t-wchar-t-is-native-type.md).  
   
diff --git a/docs/cpp/compiler-com-support-classes.md b/docs/cpp/compiler-com-support-classes.md
@@ -20,7 +20,7 @@ ms.workload: ["cplusplus"]
 # Compiler COM Support Classes
 **Microsoft Specific**  
   
- Standard classes are used to support some of the COM types. The classes are defined in comdef.h and the header files generated from the type library.  
+ Standard classes are used to support some of the COM types. The classes are defined in \<comdef.h> and the header files generated from the type library.  
   
 |Class|Purpose|  
 |-----------|-------------|  
diff --git a/docs/cpp/convertbstrtostring.md b/docs/cpp/convertbstrtostring.md
@@ -67,7 +67,7 @@ char * text: Test
 **END Microsoft Specific**  
   
 ## Requirements  
- **Header:** comutil.h.  
+ **Header:** \<comutil.h>.  
   
  **Lib:** comsuppw.lib or comsuppwd.lib (see [/Zc:wchar_t (wchar_t Is Native Type)](../build/reference/zc-wchar-t-wchar-t-is-native-type.md) for more information)  
   
diff --git a/docs/cpp/convertstringtobstr.md b/docs/cpp/convertstringtobstr.md
@@ -64,7 +64,7 @@ BSTR text: Test
 **END Microsoft Specific**  
   
 ## Requirements  
- **Header:** comutil.h  
+ **Header:** \<comutil.h>  
   
  **Lib:** comsuppw.lib or comsuppwd.lib (see [/Zc:wchar_t (wchar_t Is Native Type)](../build/reference/zc-wchar-t-wchar-t-is-native-type.md) for more information)  
   
diff --git a/docs/cpp/event-handling-in-native-cpp.md b/docs/cpp/event-handling-in-native-cpp.md
@@ -17,28 +17,34 @@ manager: "ghogen"
 ms.workload: ["cplusplus"]
 ---
 # Event Handling in Native C++
-In native C++ event handling, you set up an event source and event receiver using the [event_source](../windows/event-source.md) and [event_receiver](../windows/event-receiver.md) attributes, respectively, specifying `type`=`native`. These attributes allow the classes to which they are applied to fire events and handle events in a native, non-COM context.  
+
+In native C++ event handling, you set up an event source and event receiver using the [event_source](../windows/event-source.md) and [event_receiver](../windows/event-receiver.md) attributes, respectively, specifying `type`=`native`. These attributes allow the classes to which they are applied to fire events and handle events in a native, non-COM context.
+
+## Declaring Events
+
+In an event source class, use the [__event](../cpp/event.md) keyword on a method declaration to declare the method as an event. Make sure to declare the method, but do not define it; to do so will generate a compiler error, because the compiler defines the method implicitly when it is made into an event. Native events can be methods with zero or more parameters. The return type can be void or any integral type.  
   
-## Declaring Events  
- In an event source class, use the [__event](../cpp/event.md) keyword on a method declaration to declare the method as an event. Make sure to declare the method, but do not define it; to do so will generate a compiler error, because the compiler defines the method implicitly when it is made into an event. Native events can be methods with zero or more parameters. The return type can be void or any integral type.  
-  
-## Defining Event Handlers  
- In an event receiver class, you define event handlers, which are methods with signatures (return types, calling conventions, and arguments) that match the event that they will handle.  
+## Defining Event Handlers
+
+In an event receiver class, you define event handlers, which are methods with signatures (return types, calling conventions, and arguments) that match the event that they will handle.  
   
 ## Hooking Event Handlers to Events  
- Also in an event receiver class, you use the intrinsic function [__hook](../cpp/hook.md) to associate events with event handlers and [__unhook](../cpp/unhook.md) to dissociate events from event handlers. You can hook several events to an event handler, or several event handlers to an event.  
+
+Also in an event receiver class, you use the intrinsic function [__hook](../cpp/hook.md) to associate events with event handlers and [__unhook](../cpp/unhook.md) to dissociate events from event handlers. You can hook several events to an event handler, or several event handlers to an event.  
   
 ## Firing Events  
- To fire an event, simply call the method declared as an event in the event source class. If handlers have been hooked to the event, the handlers will be called.  
+
+To fire an event, simply call the method declared as an event in the event source class. If handlers have been hooked to the event, the handlers will be called.  
   
 ### Native C++ Event Code  
- The following example shows how to fire an event in native C++. To compile and run the example, refer to the comments in the code.  
+
+The following example shows how to fire an event in native C++. To compile and run the example, refer to the comments in the code.  
   
 ## Example  
   
 ### Code  
   
-```  
+```cpp  
 // evh_native.cpp  
 #include <stdio.h>  
   
@@ -82,10 +88,12 @@ int main() {
   
 ### Output  
   
-```  
+```Output
 MyHandler2 was called with value 123.  
 MyHandler1 was called with value 123.  
 ```  
   
-## See Also  
- [Event Handling](../cpp/event-handling.md)
+## See Also
+
+[Event Handling](../cpp/event-handling.md)  
+
diff --git a/docs/cpp/exit-function.md b/docs/cpp/exit-function.md
@@ -18,12 +18,12 @@ manager: "ghogen"
 ms.workload: ["cplusplus"]
 ---
 # exit Function
-The **exit** function, declared in the standard include file STDLIB.H, terminates a C++ program.  
+The **exit** function, declared in the standard include file \<stdlib.h>, terminates a C++ program.  
   
  The value supplied as an argument to **exit** is returned to the operating system as the program's return code or exit code. By convention, a return code of zero means that the program completed successfully.  
   
 > [!NOTE]
->  You can use the constants `EXIT_FAILURE` and `EXIT_SUCCESS`, defined in STDLIB.H, to indicate success or failure of your program.  
+>  You can use the constants `EXIT_FAILURE` and `EXIT_SUCCESS`, defined in \<stdlib.h>, to indicate success or failure of your program.  
   
  Issuing a `return` statement from the **main** function is equivalent to calling the **exit** function with the return value as its argument.  
   
diff --git a/docs/cpp/floating-limits.md b/docs/cpp/floating-limits.md
@@ -8,7 +8,7 @@ ms.technology: ["cpp-language"]
 ms.tgt_pltfrm: ""
 ms.topic: "language-reference"
 dev_langs: ["C++"]
-helpviewer_keywords: ["ranges, floating-point constants", "floating-point constants, limits", "FLOAT.H header file", "limits, floating-point constants", "floating-point numbers [C++]", "floating limits"]
+helpviewer_keywords: ["ranges, floating-point constants", "floating-point constants, limits", "float.h header file", "limits, floating-point constants", "floating-point numbers [C++]", "floating limits"]
 ms.assetid: fc718652-1f4c-4ed8-af60-0e769637459c
 caps.latest.revision: 7
 author: "mikeblome"
@@ -19,7 +19,7 @@ ms.workload: ["cplusplus"]
 # Floating Limits
 **Microsoft Specific**  
   
- The following table lists the limits on the values of floating-point constants. These limits are also defined in the standard header file FLOAT.H.  
+ The following table lists the limits on the values of floating-point constants. These limits are also defined in the standard header file \<float.h>.  
   
 ### Limits on Floating-Point Constants  
   
diff --git a/docs/cpp/functions-with-variable-argument-lists-cpp.md b/docs/cpp/functions-with-variable-argument-lists-cpp.md
@@ -20,7 +20,7 @@ ms.workload: ["cplusplus"]
 Function declarations in which the last member of  is the ellipsis (...) can take a variable number of arguments. In these cases, C++ provides type checking only for the explicitly declared arguments. You can use variable argument lists when you need to make a function so general that even the number and types of arguments can vary. The  family of functions is an example of functions that use variable argument lists.`printf`*argument-declaration-list*  
   
 ## Functions with variable arguments  
- To access arguments after those declared, use the macros contained in the standard include file STDARG.H as described below.  
+ To access arguments after those declared, use the macros contained in the standard include file \<stdarg.h> as described below.  
   
  **Microsoft Specific**  
   
@@ -32,9 +32,9 @@ Function declarations in which the last member of  is the ellipsis (...) can tak
   
  When arguments of type `char` are passed as variable arguments, they are converted to type `int`. Similarly, when arguments of type **float** are passed as variable arguments, they are converted to type **double**. Arguments of other types are subject to the usual integral and floating-point promotions. See [Standard Conversions](standard-conversions.md) for more information.  
   
- Functions that require variable lists are declared by using the ellipsis (...) in the argument list. Use the types and macros that are described in the STDARG.H include file to access arguments that are passed by a variable list. For more information about these macros, see [va_arg, va_copy, va_end, va_start](../c-runtime-library/reference/va-arg-va-copy-va-end-va-start.md). in the documentation for the C Run-Time Library.  
+ Functions that require variable lists are declared by using the ellipsis (...) in the argument list. Use the types and macros that are described in the \<stdarg.h> include file to access arguments that are passed by a variable list. For more information about these macros, see [va_arg, va_copy, va_end, va_start](../c-runtime-library/reference/va-arg-va-copy-va-end-va-start.md). in the documentation for the C Run-Time Library.  
   
- The following example shows how the macros work together with the type (declared in STDARG.H): 
+ The following example shows how the macros work together with the type (declared in \<stdarg.h>): 
   
 ```  
 // variable_argument_lists.cpp  
diff --git a/docs/cpp/how-to-create-and-use-ccomptr-and-ccomqiptr-instances.md b/docs/cpp/how-to-create-and-use-ccomptr-and-ccomqiptr-instances.md
@@ -25,7 +25,7 @@ In classic Windows programming, libraries are often implemented as COM objects (
   
  [!code-cpp[COM_smart_pointers#01](../cpp/codesnippet/CPP/how-to-create-and-use-ccomptr-and-ccomqiptr-instances_1.cpp)]  
   
- `CComPtr` and its relatives are part of the ATL and are defined in atlcomcli.h. `_com_ptr_t` is declared in comip.h. The compiler creates specializations of `_com_ptr_t` when it generates wrapper classes for type libraries.  
+ `CComPtr` and its relatives are part of the ATL and are defined in \<atlcomcli.h>. `_com_ptr_t` is declared in \<comip.h>. The compiler creates specializations of `_com_ptr_t` when it generates wrapper classes for type libraries.  
   
 ## Example  
  ATL also provides `CComQIPtr`, which has a simpler syntax for querying a COM object to retrieve an additional interface. However, we recommend `CComPtr` because it does everything that `CComQIPtr` can do and is semantically more consistent with raw COM interface pointers. If you use a `CComPtr` to query for an interface, the new interface pointer is placed in an out parameter. If the call fails, an HRESULT is returned, which is the typical COM pattern. With `CComQIPtr`, the return value is the pointer itself, and if the call fails, the internal HRESULT return value cannot be accessed. The following two lines show how the error handling mechanisms in `CComPtr` and `CComQIPtr` differ.  
diff --git a/docs/cpp/integer-limits.md b/docs/cpp/integer-limits.md
@@ -8,7 +8,7 @@ ms.technology: ["cpp-language"]
 ms.tgt_pltfrm: ""
 ms.topic: "language-reference"
 dev_langs: ["C++"]
-helpviewer_keywords: ["integral limits", "limits, integer", "LIMITS.H header file", "integer limits"]
+helpviewer_keywords: ["integral limits", "limits, integer", "limits.h header file", "integer limits"]
 ms.assetid: 6922bdbf-0f49-443b-bc03-ee182e4cbd57
 caps.latest.revision: 8
 author: "mikeblome"
@@ -19,7 +19,7 @@ ms.workload: ["cplusplus"]
 # Integer Limits
 **Microsoft Specific**  
   
- The limits for integer types are listed in the following table. These limits are also defined in the standard header file LIMITS.H.  
+ The limits for integer types are listed in the following table. These limits are also defined in the standard header file \<limits.h>.  
   
 ### Limits on Integer Constants  
   
diff --git a/docs/cpp/m128.md b/docs/cpp/m128.md
@@ -19,7 +19,7 @@ ms.workload: ["cplusplus"]
 ---
 # __m128
 ## Microsoft Specific  
- The **__m128 data** type, for use with the Streaming SIMD Extensions and Streaming SIMD Extensions 2 instructions intrinsics, is defined in xmmintrin.h.  
+ The **__m128 data** type, for use with the Streaming SIMD Extensions and Streaming SIMD Extensions 2 instructions intrinsics, is defined in \<xmmintrin.h>.  
   
 ```  
 // data_types__m128.cpp  
diff --git a/docs/cpp/m128d.md b/docs/cpp/m128d.md
@@ -19,7 +19,7 @@ ms.workload: ["cplusplus"]
 ---
 # __m128d
 ## Microsoft Specific  
- The `__m128d` data type, for use with the Streaming SIMD Extensions 2 instructions intrinsics, is defined in emmintrin.h.  
+ The `__m128d` data type, for use with the Streaming SIMD Extensions 2 instructions intrinsics, is defined in \<emmintrin.h>.  
   
 ```  
 // data_types__m128d.cpp  
diff --git a/docs/cpp/m128i.md b/docs/cpp/m128i.md
@@ -19,7 +19,7 @@ ms.workload: ["cplusplus"]
 ---
 # __m128i
 ## Microsoft Specific  
- The `__m128i` data type, for use with the Streaming SIMD Extensions 2 (SSE2) instructions intrinsics, is defined in emmintrin.h.  
+ The `__m128i` data type, for use with the Streaming SIMD Extensions 2 (SSE2) instructions intrinsics, is defined in \<emmintrin.h>.  
   
 ```  
 // data_types__m128i.cpp  
diff --git a/docs/cpp/m64.md b/docs/cpp/m64.md
@@ -19,7 +19,7 @@ ms.workload: ["cplusplus"]
 ---
 # __m64
 ## Microsoft Specific  
- The `__m64` data type is for use with the MMX and 3DNow! intrinsics, and is defined in xmmintrin.h.  
+ The `__m64` data type is for use with the MMX and 3DNow! intrinsics, and is defined in \<xmmintrin.h>.  
   
 ```  
 // data_types__m64.cpp  
diff --git a/docs/cpp/new-and-delete-operators.md b/docs/cpp/new-and-delete-operators.md
@@ -46,7 +46,7 @@ The two scopes for `operator new` functions are described in the following table
 |**::operator new**|Global|  
 |*class-name* **::operator new**|Class|  
   
- The first argument to **operator new** must be of type **size_t** (a type defined in STDDEF.H), and the return type is always **void \***.  
+ The first argument to **operator new** must be of type **size_t** (a type defined in \<stddef.h>), and the return type is always **void \***.  
   
  The global **operator new** function is called when the **new** operator is used to allocate objects of built-in types, objects of class type that do not contain user-defined **operator new** functions, and arrays of any type. When the **new** operator is used to allocate objects of a class type where an **operator new** is defined, that class's **operator new** is called.  
   
diff --git a/docs/cpp/new-operator-cpp.md b/docs/cpp/new-operator-cpp.md
@@ -233,7 +233,7 @@ int main()
  When the compiler encounters the **new** operator to allocate an object of type `type`, it issues a call to `type`**::operator new( sizeof(** `type` **) )** or, if no user-defined `operator new` is defined, **::operator new( sizeof(** `type` **) )**. Therefore, the **new** operator can allocate the correct amount of memory for the object.  
   
 > [!NOTE]
->  The argument to `operator new` is of type **size_t**. This type is defined in DIRECT.H, MALLOC.H, MEMORY.H, SEARCH.H, STDDEF.H, STDIO.H, STDLIB.H, STRING.H, and TIME.H.  
+>  The argument to `operator new` is of type **size_t**. This type is defined in \<direct.h>, \<malloc.h>, \<memory.h>, \<search.h>, \<stddef.h>, \<stdio.h>, \<stdlib.h>, \<string.h>, and \<time.h>.  
   
  An option in the grammar allows specification of *placement* (see the Grammar for [new Operator](../cpp/new-operator-cpp.md)). The *placement* parameter can be used only for user-defined implementations of `operator new`; it allows extra information to be passed to `operator new`. An expression with a *placement* field such as `T *TObject = new ( 0x0040 ) T;` is translated to `T *TObject = T::operator new( sizeof( T ), 0x0040 );` if class T has member operator new, otherwise to `T *TObject = ::operator new( sizeof( T ), 0x0040 );`.  
   
diff --git a/docs/cpp/numerical-limits-cpp.md b/docs/cpp/numerical-limits-cpp.md
diff --git a/docs/cpp/obsolete-calling-conventions.md b/docs/cpp/obsolete-calling-conventions.md
diff --git a/docs/cpp/raising-software-exceptions.md b/docs/cpp/raising-software-exceptions.md
diff --git a/docs/cpp/set-com-error-handler.md b/docs/cpp/set-com-error-handler.md
diff --git a/docs/cpp/sizeof-operator.md b/docs/cpp/sizeof-operator.md
diff --git a/docs/cpp/timing-of-exception-handling-a-summary.md b/docs/cpp/timing-of-exception-handling-a-summary.md
diff --git a/docs/cpp/try-except-statement.md b/docs/cpp/try-except-statement.md
diff --git a/docs/cpp/using-setjmp-longjmp.md b/docs/cpp/using-setjmp-longjmp.md
diff --git a/docs/cpp/uuid-cpp.md b/docs/cpp/uuid-cpp.md
diff --git a/docs/cpp/variant-t-class.md b/docs/cpp/variant-t-class.md
