docset changes spacing

Author: msebolt

docs/atl/reference/com-plus-1-0-atl-com-plus-1-0-component-wizard.md

@@ -24,7 +24,7 @@ For more information on ATL projects and ATL COM classes, see [ATL COM Desktop C
    |Option|Description|
    |------------|-----------------|
    |**Dual**|Specifies that the object supports a dual interface (its vtable has custom interface functions and late-binding `IDispatch` methods). Allows both COM clients and Automation controllers to access the object.|
-   |**Custom**|Specifies that the object supports a custom interface (its vtable has custom interface functions). A custom interface can be faster than a dual interface, especially across process boundaries.<br /><br /> -   **Automation compatible** Adds automation support to the custom interface. For attributed projects, sets the **oleautomation** attribute in the coclass.|
+   |**Custom**|Specifies that the object supports a custom interface (its vtable has custom interface functions). A custom interface can be faster than a dual interface, especially across process boundaries.<br /><br /> - **Automation compatible** Adds automation support to the custom interface. For attributed projects, sets the **oleautomation** attribute in the coclass.|
 
 - **Queueable**
 

docs/atl/reference/options-atl-simple-object-wizard.md

@@ -49,7 +49,7 @@ For more information on ATL projects and ATL COM classes, see [ATL COM Desktop C
    |Option|Description|
    |------------|-----------------|
    |**Dual**|Specifies that the object supports a dual interface (its vtable has custom interface functions plus late-binding `IDispatch` methods). Allows both COM clients and [Automation controllers](../../mfc/automation-clients.md) to access the object. The default.|
-   |**Custom**|Specifies that the object supports a custom interface (its vtable has custom interface functions). A custom interface can be faster than a dual interface, especially across process boundaries.<br /><br /> -   **Automation compatible** Allows Automation controllers to access an object that has the custom interface support.|
+   |**Custom**|Specifies that the object supports a custom interface (its vtable has custom interface functions). A custom interface can be faster than a dual interface, especially across process boundaries.<br /><br /> - **Automation compatible** Allows Automation controllers to access an object that has the custom interface support.|
 
 - **Support**
 

docs/build/aggregates-and-unions.md

@@ -19,7 +19,7 @@ Other types, such as arrays, structs, and unions, have stricter alignment requir
 
    Contains an ordered group of adjacent data objects. Each object is called an element. All elements within an array have the same size and data type.
 
--  Structure
+- Structure
 
    Contains an ordered group of data objects. Unlike the elements of an array, the data objects within a structure can have different data types and sizes. Each data object in a structure is called a member.
 

docs/build/arm-exception-handling.md

@@ -73,15 +73,15 @@ This table shows the format of a .pdata record that has packed unwind data:
 |Word Offset|Bits|Purpose|
 |-----------------|----------|-------------|
 |0|0-31|*Function Start RVA* is the 32-bit RVA of the start of the function. If the function contains thumb code, the low bit of this address must be set.|
-|1|0-1|*Flag* is a 2-bit field that has these meanings:<br /><br /> -   00 = packed unwind data not used; remaining bits point to .xdata record.<br />-   01 = packed unwind data.<br />-   10 = packed unwind data where the function is assumed to have no prologue. This is useful for describing function fragments that are discontiguous with the start of the function.<br />-   11 = reserved.|
+|1|0-1|*Flag* is a 2-bit field that has these meanings:<br /><br />- 00 = packed unwind data not used; remaining bits point to .xdata record.<br />- 01 = packed unwind data.<br />- 10 = packed unwind data where the function is assumed to have no prologue. This is useful for describing function fragments that are discontiguous with the start of the function.<br />- 11 = reserved.|
 |1|2-12|*Function Length* is an 11-bit field that provides the length of the entire function in bytes divided by 2. If the function is larger than 4K bytes, a full .xdata record must be used instead.|
-|1|13-14|*Ret* is a 2-bit field that indicates how the function returns:<br /><br /> -   00 = return via pop {pc} (the *L* flag bit must be set to 1 in this case).<br />-   01 = return by using a 16-bit branch.<br />-   10 = return by using a 32-bit branch.<br />-   11 = no epilogue at all. This is useful for describing a discontiguous function fragment that may only contain a prologue, but whose epilogue is elsewhere.|
+|1|13-14|*Ret* is a 2-bit field that indicates how the function returns:<br /><br />- 00 = return via pop {pc} (the *L* flag bit must be set to 1 in this case).<br />- 01 = return by using a 16-bit branch.<br />- 10 = return by using a 32-bit branch.<br />- 11 = no epilogue at all. This is useful for describing a discontiguous function fragment that may only contain a prologue, but whose epilogue is elsewhere.|
 |1|15|*H* is a 1-bit flag that indicates whether the function "homes" the integer parameter registers (r0-r3) by pushing them at the start of the function, and deallocates the 16 bytes of stack before returning. (0 = does not home registers, 1 = homes registers.)|
 |1|16-18|*Reg* is a 3-bit field that indicates the index of the last saved non-volatile register. If the *R* bit is 0, then only integer registers are being saved, and are assumed to be in the range of r4-rN, where N is equal to 4 + *Reg*. If the *R* bit is 1, then only floating-point registers are being saved, and are assumed to be in the range of d8-dN, where N is equal to 8 + *Reg*. The special combination of *R* = 1 and *Reg* = 7 indicates that no registers are saved.|
 |1|19|*R* is a 1-bit flag that indicates whether the saved non-volatile registers are integer registers (0) or floating-point registers (1). If *R* is set to 1 and the *Reg* field is set to 7, no non-volatile registers were pushed.|
 |1|20|*L* is a 1-bit flag that indicates whether the function saves/restores LR, along with other registers indicated by the *Reg* field. (0 = does not save/restore, 1 = does save/restore.)|
 |1|21|*C* is a 1-bit flag that indicates whether the function includes extra instructions to set up a frame chain for fast stack walking (1) or not (0). If this bit is set, r11 is implicitly added to the list of integer non-volatile registers saved. (See restrictions below if the *C* flag is used.)|
-|1|22-31|*Stack Adjust* is a 10-bit field that indicates the number of bytes of stack that are allocated for this function, divided by 4. However, only values between 0x000-0x3F3 can be directly encoded. Functions that allocate more than 4044 bytes of stack must use a full .xdata record. If the *Stack Adjust* field is 0x3F4 or larger, then the low 4 bits have special meaning:<br /><br /> -   Bits 0-1 indicate the number of words of stack adjustment (1-4) minus 1.<br />-   Bit 2 is set to 1 if the prologue combined this adjustment into its push operation.<br />-   Bit 3 is set to 1 if the epilogue combined this adjustment into its pop operation.|
+|1|22-31|*Stack Adjust* is a 10-bit field that indicates the number of bytes of stack that are allocated for this function, divided by 4. However, only values between 0x000-0x3F3 can be directly encoded. Functions that allocate more than 4044 bytes of stack must use a full .xdata record. If the *Stack Adjust* field is 0x3F4 or larger, then the low 4 bits have special meaning:<br /><br />- Bits 0-1 indicate the number of words of stack adjustment (1-4) minus 1.<br />- Bit 2 is set to 1 if the prologue combined this adjustment into its push operation.<br />- Bit 3 is set to 1 if the epilogue combined this adjustment into its pop operation.|
 
 Due to possible redundancies in the encodings above, these restrictions apply:
 

docs/build/exit-codes-from-nmake.md

@@ -20,9 +20,9 @@ NMAKE returns the following exit codes:
 |0|No error (possibly a warning)|
 |1|Incomplete build (issued only when /K is used)|
 |2|Program error, possibly due to one of the following:|
-||-   A syntax error in the makefile|
-||-   An error or exit code from a command|
-||-   An interruption by the user|
+||- A syntax error in the makefile|
+||- An error or exit code from a command|
+||- An interruption by the user|
 |4|System error — out of memory|
 |255|Target is not up-to-date (issued only when /Q is used)|
 

docs/cpp/explicitly-defaulted-and-deleted-functions.md

@@ -39,8 +39,8 @@ This is convenient for simple types, but complex types often define one or more
 > [!NOTE]
 >  Additionally, the C++11 standard specifies the following additional rules:
 >
->  -   If a copy constructor or destructor is explicitly declared, then automatic generation of the copy-assignment operator is deprecated.
-> -   If a copy-assignment operator or destructor is explicitly declared, then automatic generation of the copy constructor is deprecated.
+> - If a copy constructor or destructor is explicitly declared, then automatic generation of the copy-assignment operator is deprecated.
+> - If a copy-assignment operator or destructor is explicitly declared, then automatic generation of the copy constructor is deprecated.
 >
 >  In both cases, Visual Studio continues to automatically generate the necessary functions implicitly, and does not emit a warning.
 

docs/cpp/pointers-to-members.md

@@ -42,7 +42,7 @@ Declarations of pointers to members are special cases of pointer declarations.
   - The qualified name of the class.
   - The `::` operator.
   - The name of a nonstatic member of the class of the appropriate type.
-  -  As always, multiple declarators (and any associated initializers) are allowed in a single declaration.
+  - As always, multiple declarators (and any associated initializers) are allowed in a single declaration.
 
 A pointer to a member of a class differs from a normal pointer because it has type information for the type of the member and for the class to which the member belongs. A normal pointer identifies (has the address of) only a single object in memory. A pointer to a member of a class identifies that member in any instance of the class. The following example declares a class, `Window`, and some pointers to member data.
 

docs/cpp/standard-conversions.md

@@ -150,7 +150,7 @@ Many binary operators (discussed in [Expressions with Binary Operators](../cpp/e
 |Either operand is of type **long double**.|Other operand is converted to type **long double**.|
 |Preceding condition not met and either operand is of type **double**.|Other operand is converted to type **double**.|
 |Preceding conditions not met and either operand is of type **float**.|Other operand is converted to type **float**.|
-|Preceding conditions not met (none of the operands are of floating types).|Integral promotions are performed on the operands as follows:<br /><br /> -   If either operand is of type **unsigned long**, the other operand is converted to type **unsigned long**.<br />-   If preceding condition not met, and if either operand is of type **long** and the other of type **unsigned int**, both operands are converted to type **unsigned long**.<br />-   If the preceding two conditions are not met, and if either operand is of type **long**, the other operand is converted to type **long**.<br />-   If the preceding three conditions are not met, and if either operand is of type **unsigned int**, the other operand is converted to type **unsigned int**.<br />-   If none of the preceding conditions are met, both operands are converted to type **int**.|
+|Preceding conditions not met (none of the operands are of floating types).|Integral promotions are performed on the operands as follows:<br /><br />- If either operand is of type **unsigned long**, the other operand is converted to type **unsigned long**.<br />- If preceding condition not met, and if either operand is of type **long** and the other of type **unsigned int**, both operands are converted to type **unsigned long**.<br />- If the preceding two conditions are not met, and if either operand is of type **long**, the other operand is converted to type **long**.<br />- If the preceding three conditions are not met, and if either operand is of type **unsigned int**, the other operand is converted to type **unsigned int**.<br />- If none of the preceding conditions are met, both operands are converted to type **int**.|
 
 The following code illustrates the conversion rules described in the table:
 

docs/cpp/storage-classes-cpp.md

@@ -206,13 +206,13 @@ Things to note about the `thread_local` specifier:
 
 - Dynamically initialized thread-local variables in DLLs may not be correctly initialized on all calling threads. For more information, see [thread](thread.md).
 
--  The `thread_local` specifier may be combined with **static** or **extern**.
+- The `thread_local` specifier may be combined with **static** or **extern**.
 
--  You can apply `thread_local` only to data declarations and definitions; `thread_local` cannot be used on function declarations or definitions.
+- You can apply `thread_local` only to data declarations and definitions; `thread_local` cannot be used on function declarations or definitions.
 
--  You can specify `thread_local` only on data items with static storage duration. This includes global data objects (both **static** and **extern**), local static objects, and static data members of classes. Any local variable declared `thread_local` is implicitly static if no other storage class is provided; in other words, at block scope `thread_local` is equivalent to `thread_local static`.
+- You can specify `thread_local` only on data items with static storage duration. This includes global data objects (both **static** and **extern**), local static objects, and static data members of classes. Any local variable declared `thread_local` is implicitly static if no other storage class is provided; in other words, at block scope `thread_local` is equivalent to `thread_local static`.
 
--  You must specify `thread_local` for both the declaration and the definition of a thread local object, whether the declaration and definition occur in the same file or separate files.
+- You must specify `thread_local` for both the declaration and the definition of a thread local object, whether the declaration and definition occur in the same file or separate files.
 
 On Windows, `thread_local` is functionally equivalent to  [__declspec(thread)](../cpp/thread.md) except that **__declspec(thread)** can be applied to a type definition and is valid in C code. Whenever possible, use `thread_local` because it is part of the C++ standard and is therefore more portable.
 

docs/cppcx/compiler-and-linker-options-c-cx.md

@@ -21,7 +21,7 @@ The %LIBPATH% environment variable specifies the default path to search for .win
 
 |Option|Description|
 |------------|-----------------|
-|[/ZW](../build/reference/zw-windows-runtime-compilation.md)<br /><br /> /ZW:nostdlib|Enables Windows Runtime language extensions.<br /><br /> The `nostdlib` parameter prevents the compiler from using the standard, predefined search path to find assembly and .winmd files.<br /><br /> The **/ZW** compiler option implicitly specifies the following compiler options:<br /><br /> -   **/FI** vccorlib.h, which forces inclusion of the vccorlib.h header file that defines many types that are required by the compiler.<br />-   [/FU](../build/reference/fu-name-forced-hash-using-file.md) Windows.winmd, which forces inclusion of the Windows.winmd metadata file that's provided by the operating system and defines many types in the Windows Runtime.<br />-   **/FU** Platform.winmd, which forces inclusion of the Platform.winmd metadata file that's provided by the compiler and defines most types in the Platform family of namespaces.|
+|[/ZW](../build/reference/zw-windows-runtime-compilation.md)<br /><br /> /ZW:nostdlib|Enables Windows Runtime language extensions.<br /><br /> The `nostdlib` parameter prevents the compiler from using the standard, predefined search path to find assembly and .winmd files.<br /><br /> The **/ZW** compiler option implicitly specifies the following compiler options:<br /><br />- **/FI** vccorlib.h, which forces inclusion of the vccorlib.h header file that defines many types that are required by the compiler.<br />- [/FU](../build/reference/fu-name-forced-hash-using-file.md) Windows.winmd, which forces inclusion of the Windows.winmd metadata file that's provided by the operating system and defines many types in the Windows Runtime.<br />- **/FU** Platform.winmd, which forces inclusion of the Platform.winmd metadata file that's provided by the compiler and defines most types in the Platform family of namespaces.|
 |[/AI](../build/reference/ai-specify-metadata-directories.md) *dir*|Adds a directory, which is specified by the *dir* parameter, to the search path that the compiler uses to find assembly and .winmd files.|
 |**/FU**  *file*|Forces the inclusion of the specified module, or .winmd file. That is, you don't have to specify `#using`*file* in your source code. The compiler automatically forces the inclusion of its own Windows metadata file, Platform.winmd.|
 |/D "WINAPI_FAMILY=2"|Creates a definition that enables the use of a subset of the Win32 SDK that's compatible with the Windows Runtime.|

docs/data/odbc/data-source-programmatically-configuring-an-odbc-data-source.md

@@ -88,13 +88,13 @@ One way to find the keynames and values for the *lpszAttributes* parameter is to
 
 1. Find the ODBC data sources information using one of the following:  
 
-    -   For 32 bit, find the key **HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\ODBC Data Sources** in the left pane.  
+    - For 32 bit, find the key **HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\ODBC Data Sources** in the left pane.  
 
-         The right pane lists entries of the form: "pub: REG_SZ:*<data source name>*", where *<data source name>* is a data source that has already been configured with the desired settings for the driver you intend to use. Select the data source you want, for example, SQL Server. The items following the string "pub:" are, in order, the keyname and value to use in your *lpszAttributes* parameter.  
+        The right pane lists entries of the form: "pub: REG_SZ:*<data source name>*", where *<data source name>* is a data source that has already been configured with the desired settings for the driver you intend to use. Select the data source you want, for example, SQL Server. The items following the string "pub:" are, in order, the keyname and value to use in your *lpszAttributes* parameter.  
 
-    -   For 16 bit, find the section in the Odbc.ini file marked by [*\<data source name>*].  
+    - For 16 bit, find the section in the Odbc.ini file marked by [*\<data source name>*].  
 
-         The lines following this line are of the form "keyname=value". These are exactly the entries to use in your *lpszAttributes* parameter.  
+        The lines following this line are of the form "keyname=value". These are exactly the entries to use in your *lpszAttributes* parameter.  
 
 You might also want to examine the documentation for the specific driver you are going to use. You can find useful information in the online Help for the driver, which you can access by running ODBC Administrator. These Help files are usually placed in the WINDOWS\SYSTEM directory for Windows NT, Windows 3.1, or Windows 95.