Merge pull request #2867 from corob-msft/cr-tc-tp-tc-tp

GitHubber17 · web-flow · commit 7ce6814fbb15 · 2020-05-04T19:29:33.000-07:00
Bulk Fix inconsistent formatting of options
diff --git a/docs/assembler/masm/dot-const.md b/docs/assembler/masm/dot-const.md
@@ -11,7 +11,7 @@ When used with [.MODEL](dot-model.md), starts a constant data segment (with segm
 
 ## Syntax
 
-> **.CONST**
+> **.CONST**\
 > ⟦ *segmentItem* ⟧...
 
 ## Remarks
diff --git a/docs/assembler/masm/struct-masm.md b/docs/assembler/masm/struct-masm.md
@@ -11,7 +11,7 @@ Declares a structure type having the specified *field-declarations*. Each field
 
 ## Syntax
 
-> *name* **STRUCT** ⟦*alignment*⟧ ⟦__,__ **NONUNIQUE**⟧
+> *name* **STRUCT** ⟦*alignment*⟧ ⟦__,__ **NONUNIQUE**⟧\
 > *field-declarations*\
 > *name* **ENDS**
 
diff --git a/docs/atl-mfc-shared/reference/cimage-class.md b/docs/atl-mfc-shared/reference/cimage-class.md
@@ -137,8 +137,8 @@ Through `CImage`, you have access to the actual bits of a DIB section. You can u
 You can use `CImage` from either MFC or ATL.
 
 > [!NOTE]
-> When you create a project using `CImage`, you must define `CString` before you include *atlimage.h*. If your project uses ATL without MFC, include *atlstr.h* before you include *atlimage.h*. If your project uses MFC (or if it is an ATL project with MFC support), include *afxstr.h* before you include *atlimage.h*.<br/>
-> <br/>
+> When you create a project using `CImage`, you must define `CString` before you include *atlimage.h*. If your project uses ATL without MFC, include *atlstr.h* before you include *atlimage.h*. If your project uses MFC (or if it is an ATL project with MFC support), include *afxstr.h* before you include *atlimage.h*.
+>
 > Likewise, you must include *atlimage.h* before you include *atlimpl.cpp*. To accomplish this easily, include *atlimage.h* in your *pch.h* (*stdafx.h* in Visual Studio 2017 and earlier).
 
 ## Requirements
diff --git a/docs/build/reference/constexpr-control-constexpr-evaluation.md b/docs/build/reference/constexpr-control-constexpr-evaluation.md
@@ -11,8 +11,8 @@ Use the **/constexpr** compiler options to control parameters for **constexpr**
 
 ## Syntax
 
-> **/constexpr:depth**<em>N</em>
-> **/constexpr:backtrace**<em>N</em>
+> **/constexpr:depth**<em>N</em>\
+> **/constexpr:backtrace**<em>N</em>\
 > **/constexpr:steps**<em>N</em>
 
 ## Arguments
diff --git a/docs/build/reference/fe-name-exe-file.md b/docs/build/reference/fe-name-exe-file.md
@@ -11,7 +11,7 @@ Specifies a name and a directory for the .exe file or DLL created by the compile
 
 ## Syntax
 
-> **/Fe**[_pathname_]
+> **/Fe**[_pathname_]\
 > **/Fe:** _pathname_
 
 ### Arguments
diff --git a/docs/build/reference/gd-gr-gv-gz-calling-convention.md b/docs/build/reference/gd-gr-gv-gz-calling-convention.md
@@ -11,9 +11,9 @@ These options determine the order in which function arguments are pushed onto th
 
 ## Syntax
 
-> **/Gd**<br/>
-> **/Gr**<br/>
-> **/Gv**<br/>
+> **/Gd**\
+> **/Gr**\
+> **/Gv**\
 > **/Gz**
 
 ## Remarks
diff --git a/docs/build/reference/genprofile-fastgenprofile-generate-profiling-instrumented-build.md b/docs/build/reference/genprofile-fastgenprofile-generate-profiling-instrumented-build.md
@@ -11,7 +11,7 @@ Specifies generation of a .pgd file by the linker to support profile-guided opti
 
 ## Syntax
 
-> **/GENPROFILE**[**:**{[**COUNTER32**|**COUNTER64**]|[**EXACT**|**NOEXACT**]|**MEMMAX=**_#_|**MEMMIN=**_#_|[**PATH**|**NOPATH** ]|[**TRACKEH** |**NOTRACKEH** ]|**PGD=**_filename_}]<br/>
+> **/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_}]
 
 ### Arguments
diff --git a/docs/build/reference/o1-o2-minimize-size-maximize-speed.md b/docs/build/reference/o1-o2-minimize-size-maximize-speed.md
@@ -11,7 +11,7 @@ Selects a predefined set of options that affect the size and speed of generated
 
 ## Syntax
 
-> /O1
+> /O1\
 > /O2
 
 ## Remarks
@@ -26,7 +26,7 @@ The **/O1** and **/O2** compiler options are a quick way to set several specific
 **/O1** and **/O2** are mutually exclusive.
 
 > [!NOTE]
-> **x86 Specific**
+> **x86 Specific**\
 > These options imply the use of the Frame-Pointer Omission ([/Oy](oy-frame-pointer-omission.md)) option.
 
 ### To set this compiler option in the Visual Studio development environment
diff --git a/docs/build/reference/opt-optimizations.md b/docs/build/reference/opt-optimizations.md
@@ -11,8 +11,8 @@ Controls the optimizations that LINK performs during a build.
 
 ## Syntax
 
-> **/OPT:**{**REF** | **NOREF**}<br/>
-> **/OPT:**{**ICF**[**=**_iterations_] | **NOICF**}<br/>
+> **/OPT:**{**REF** | **NOREF**}\
+> **/OPT:**{**ICF**[**=**_iterations_] | **NOICF**}\
 > **/OPT:**{**LBR** | **NOLBR**}
 
 ## Arguments
diff --git a/docs/build/reference/tc-tp-tc-tp-specify-source-file-type.md b/docs/build/reference/tc-tp-tc-tp-specify-source-file-type.md
@@ -12,12 +12,12 @@ The **/Tc** option specifies that its filename argument is a C source file, even
 
 ## Syntax
 
-> **/Tc** _filename_
-> **/Tp** _filename_
-> **/TC**
+> **/Tc** _filename_\
+> **/Tp** _filename_\
+> **/TC**\
 > **/TP**
 
-## Arguments
+### Arguments
 
 *filename*<br/>
 A C or C++ source file.
diff --git a/docs/build/reference/yc-create-precompiled-header-file.md b/docs/build/reference/yc-create-precompiled-header-file.md
@@ -11,7 +11,7 @@ Instructs the compiler to create a precompiled header (.pch) file that represent
 
 ## Syntax
 
-> __/Yc__<br/>
+> __/Yc__\
 > __/Yc__*filename*
 
 ## Arguments
diff --git a/docs/build/reference/yl-inject-pch-reference-for-debug-library.md b/docs/build/reference/yl-inject-pch-reference-for-debug-library.md
@@ -11,8 +11,8 @@ The **/Yl** option generates a unique symbol in a precompiled header file, and a
 
 ## Syntax
 
->**/Yl**
->**/Yl**_name_
+>**/Yl**\
+>**/Yl**_name_\
 >**/Yl-**
 
 ### Arguments
diff --git a/docs/build/reference/za-ze-disable-language-extensions.md b/docs/build/reference/za-ze-disable-language-extensions.md
@@ -11,7 +11,7 @@ The **/Za** compiler option disables and emits errors for Microsoft extensions t
 
 ## Syntax
 
-> **/Za**<br/>
+> **/Za**\
 > **/Ze**
 
 ## Remarks
diff --git a/docs/c-language/structure-and-union-members.md b/docs/c-language/structure-and-union-members.md
@@ -8,7 +8,7 @@ ms.assetid: bb1fe304-af49-4f98-808d-afdc99b3e319
 
 A "member-selection expression" refers to members of structures and unions. Such an expression has the value and type of the selected member.
 
-> *postfix-expression* **.** *identifier*
+> *postfix-expression* **.** *identifier*\
 > *postfix-expression* **->** *identifier*
 
 This list describes the two forms of the member-selection expressions:
diff --git a/docs/c-language/switch-statement-c.md b/docs/c-language/switch-statement-c.md
@@ -12,11 +12,11 @@ The __`switch`__ and __`case`__ statements help control complex conditional and
 
 ## Syntax
 
-> *`selection-statement`*:<br/>
+> *`selection-statement`*:\
 > &nbsp;&nbsp;&nbsp;&nbsp; __`switch (`__&nbsp;*`expression`* &nbsp;__`)`__&nbsp;*`statement`*
 
-> *`labeled-statement`*:<br/>
-> &nbsp;&nbsp;&nbsp;&nbsp; __`case`__&nbsp;*`constant-expression`*&nbsp;__`:`__&nbsp;*`statement`*<br/>
+> *`labeled-statement`*:\
+> &nbsp;&nbsp;&nbsp;&nbsp; __`case`__&nbsp;*`constant-expression`*&nbsp;__`:`__&nbsp;*`statement`*\
 > &nbsp;&nbsp;&nbsp;&nbsp; __`default`__&nbsp;__`:`__&nbsp;*`statement`*
 
 ## Remarks
diff --git a/docs/c-runtime-library/format-specification-syntax-printf-and-wprintf-functions.md b/docs/c-runtime-library/format-specification-syntax-printf-and-wprintf-functions.md
@@ -39,7 +39,7 @@ The arguments that follow the format string are interpreted according to the cor
 Integer types such as `short`, `int`, `long`, `long long`, and their `unsigned` variants, are specified by using **d**, **i**, **o**, **u**, **x**, and **X**. Floating-point types such as `float`, `double`, and `long double`, are specified by using **a**, **A**, **e**, **E**, **f**, **F**, **g**, and **G**. By default, unless they are modified by a *size* prefix, integer arguments are coerced to `int` type, and floating-point arguments are coerced to `double`. On 64-bit systems, an `int` is a 32-bit value; therefore, 64-bit integers will be truncated when they are formatted for output unless a *size* prefix of **ll** or **I64** is used. Pointer types that are specified by **p** use the default pointer size for the platform.
 
 > [!NOTE]
-> **Microsoft-specific:**
+> **Microsoft-specific:**\
 > The **Z** type character, and the behavior of the **c**, **C**, **s**, and  **S** type characters when they are used with the `printf` and `wprintf` functions, are Microsoft extensions. The ISO C standard uses **c** and **s** consistently for narrow characters and strings, and **C** and **S** for wide characters and strings, in all formatting functions.
 
 ### Type field characters
@@ -193,7 +193,7 @@ In Visual C++, although `long double` is a distinct type, it has the same intern
 An **hc** or **hC** type specifier is synonymous with **c** in `printf` functions and with **C** in `wprintf` functions. An **lc**, **lC**, **wc**, or **wC** type specifier is synonymous with **C** in `printf` functions and with **c** in `wprintf` functions. An **hs** or **hS** type specifier is synonymous with **s** in `printf` functions and with **S** in `wprintf` functions. An **ls**, **lS**, **ws** or **wS** type specifier is synonymous with **S** in `printf` functions and with **s** in `wprintf` functions.
 
 > [!NOTE]
-> **Microsoft-specific:**
+> **Microsoft-specific:**\
 > The **I** (uppercase i), **I32**, **I64**, and **w** argument size modifier prefixes are Microsoft extensions and are not ISO C-compatible. The **h** prefix when it's used with data of type `char` and the **l** (lowercase L) prefix when it's used with data of type `double` are Microsoft extensions.
 
 ## See also
diff --git a/docs/c-runtime-library/inp-inpw-inpd.md b/docs/c-runtime-library/inp-inpw-inpd.md
@@ -15,7 +15,7 @@ ms.assetid: 5d9c2e38-fc85-4294-86d5-7282cc02d1b3
 Inputs, from a port, a byte (`inp`, `_inp`), a word (`inpw`, `_inpw`), or a double word (`_inpd`).
 
 > [!IMPORTANT]
-> These functions are obsolete. Beginning in Visual Studio 2015, they are not available in the CRT.  
+> These functions are obsolete. Beginning in Visual Studio 2015, they are not available in the CRT.\
 > This API cannot be used in applications that execute in the Windows Runtime. For more information, see [CRT functions not supported in Universal Windows Platform apps](../cppcx/crt-functions-not-supported-in-universal-windows-platform-apps.md).
 
 ## Syntax
diff --git a/docs/c-runtime-library/outp-outpw-outpd.md b/docs/c-runtime-library/outp-outpw-outpd.md
@@ -15,7 +15,7 @@ ms.assetid: c200fe22-41f6-46fd-b0be-ebb805b35181
 Outputs, at a port, a byte (`outp`, `_outp`), a word (`outpw`, `_outpw`), or a double word (`_outpd`).
 
 > [!IMPORTANT]
-> These functions are obsolete. Beginning in Visual Studio 2015, they are not available in the CRT.  
+> These functions are obsolete. Beginning in Visual Studio 2015, they are not available in the CRT.\
 > This API cannot be used in applications that execute in the Windows Runtime. For more information, see [CRT functions not supported in Universal Windows Platform apps](../cppcx/crt-functions-not-supported-in-universal-windows-platform-apps.md).
 
 ## Syntax
diff --git a/docs/code-quality/understanding-sal.md b/docs/code-quality/understanding-sal.md
@@ -29,7 +29,7 @@ void * memcpy(
 
 Can you tell what this function does? When a function is implemented or called, certain properties must be maintained to ensure program correctness. Just by looking at a declaration such as the one in the example, you don't know what they are. Without SAL annotations, you'd have to rely on documentation or code comments. Here's what the MSDN documentation for `memcpy` says:
 
-> "Copies count bytes of src to dest. If the source and destination overlap, the behavior of memcpy is undefined. Use memmove to handle overlapping regions.
+> "Copies count bytes of src to dest. If the source and destination overlap, the behavior of memcpy is undefined. Use memmove to handle overlapping regions.\
 > **Security Note:** Make sure that the destination buffer is the same size or larger than the source buffer. For more information, see Avoiding Buffer Overruns."
 
 The documentation contains a couple of bits of information that suggest that your code has to maintain certain properties to ensure program correctness:
diff --git a/docs/cpp/left-shift-and-right-shift-operators-input-and-output.md b/docs/cpp/left-shift-and-right-shift-operators-input-and-output.md
@@ -11,7 +11,7 @@ The bitwise shift operators are the right-shift operator (**&gt;&gt;**), which m
 
 ## Syntax
 
-> *shift-expression* `<<` *additive-expression*
+> *shift-expression* `<<` *additive-expression*\
 > *shift-expression* `>>` *additive-expression*
 
 ## Remarks
diff --git a/docs/cpp/noexcept-cpp.md b/docs/cpp/noexcept-cpp.md
@@ -10,8 +10,8 @@ ms.assetid: df24edb9-c6a6-4e37-9914-fd5c0c3716a8
 
 ## Syntax
 
-> *noexcept-expression*:
-> &nbsp;&nbsp;&nbsp;&nbsp;**noexcept**
+> *noexcept-expression*:\
+> &nbsp;&nbsp;&nbsp;&nbsp;**noexcept**\
 > &nbsp;&nbsp;&nbsp;&nbsp;**noexcept(** *constant-expression* **)**
 
 ### Parameters
diff --git a/docs/cpp/switch-statement-cpp.md b/docs/cpp/switch-statement-cpp.md
@@ -13,19 +13,19 @@ Allows selection among multiple sections of code, depending on the value of an i
 
 ## Syntax
 
-> *`selection-statement`*:<br/>
+> *`selection-statement`*:\
 > &nbsp;&nbsp;&nbsp;&nbsp; __`switch`__&nbsp;__`(`__&nbsp;*`init-statement`*<sub>opt</sub><sup>C++17</sup>&nbsp;*`condition`*&nbsp;__`)`__&nbsp;*`statement`*
 
-> *`init-statement`*:<br/>
-> &nbsp;&nbsp;&nbsp;&nbsp; *`expression-statement`*<br/>
+> *`init-statement`*:\
+> &nbsp;&nbsp;&nbsp;&nbsp; *`expression-statement`*\
 > &nbsp;&nbsp;&nbsp;&nbsp; *`simple-declaration`*
 
-> *`condition`*:<br/>
-> &nbsp;&nbsp;&nbsp;&nbsp; *`expression`*<br/>
+> *`condition`*:\
+> &nbsp;&nbsp;&nbsp;&nbsp; *`expression`*\
 > &nbsp;&nbsp;&nbsp;&nbsp; *`attribute-specifier-seq`*<sub>opt</sub>&nbsp;*`decl-specifier-seq`*&nbsp;*`declarator`*&nbsp;*`brace-or-equal-initializer`*
 
-> *`labeled-statement`*:<br/>
-> &nbsp;&nbsp;&nbsp;&nbsp; __`case`__&nbsp;*`constant-expression`*&nbsp;__`:`__&nbsp;*`statement`*<br/>
+> *`labeled-statement`*:\
+> &nbsp;&nbsp;&nbsp;&nbsp; __`case`__&nbsp;*`constant-expression`*&nbsp;__`:`__&nbsp;*`statement`*\
 > &nbsp;&nbsp;&nbsp;&nbsp; __`default`__&nbsp;__`:`__&nbsp;*`statement`*
 
 ## Remarks
diff --git a/docs/cpp/try-except-statement.md b/docs/cpp/try-except-statement.md
@@ -12,13 +12,13 @@ The **try-except** statement is a Microsoft extension that supports structured e
 
 ## Syntax
 
-> **\_\_try**<br/>
-> {<br/>
-> &nbsp;&nbsp;&nbsp;&nbsp;// guarded code<br/>
-> }<br/>
-> **\_\_except** ( *expression* )<br/>
-> {<br/>
-> &nbsp;&nbsp;&nbsp;&nbsp;// exception handler code<br/>
+> **\_\_try**\
+> {\
+> &nbsp;&nbsp;&nbsp;&nbsp;// guarded code\
+> }\
+> **\_\_except** ( *expression* )\
+> {\
+> &nbsp;&nbsp;&nbsp;&nbsp;// exception handler code\
 > }
 
 ## Remarks
diff --git a/docs/cpp/try-finally-statement.md b/docs/cpp/try-finally-statement.md
@@ -12,12 +12,12 @@ ms.assetid: 826e0347-ddfe-4f6e-a7bc-0398e0edc7c2
 The following syntax describes the **try-finally** statement:
 
 > **\_\_try**<br/>
-> {<br/>
-> &nbsp;&nbsp;&nbsp;&nbsp;// guarded code<br/>
-> }<br/>
-> **\_\_finally**<br/>
-> {<br/>
-> &nbsp;&nbsp;&nbsp;&nbsp;// termination code<br/>
+> {\
+> &nbsp;&nbsp;&nbsp;&nbsp;// guarded code\
+> }\
+> **\_\_finally**\
+> {\
+> &nbsp;&nbsp;&nbsp;&nbsp;// termination code\
 > }
 
 ## Grammar
diff --git a/docs/dotnet/for-each-in.md b/docs/dotnet/for-each-in.md
@@ -14,8 +14,8 @@ Iterates through an array or collection. This non-standard keyword is available
 
 ### Syntax
 
-> **for each (** *type* *identifier* **in** *expression* **) {**<br/>
-> &nbsp;&nbsp;&nbsp;&nbsp;*statements*<br/>
+> **for each (** *type* *identifier* **in** *expression* **) {**\
+> &nbsp;&nbsp;&nbsp;&nbsp;*statements*\
 > **}**
 
 ### Parameters
diff --git a/docs/error-messages/compiler-warnings/c4473.md b/docs/error-messages/compiler-warnings/c4473.md
@@ -6,12 +6,12 @@ helpviewer_keywords: ["C4473"]
 ---
 # Compiler Warning (level 1) C4473
 
-> '*function*' : not enough arguments passed for format string
-> placeholders and their parameters expect *number* variadic arguments, but *number* were provided
-> the missing variadic argument *index* is required by format string '*format_string*'
-> this argument is used by a conversion specifier
-> this argument is used as a field width
-> this argument is used as a precision
+> '*function*' : not enough arguments passed for format string\
+> placeholders and their parameters expect *number* variadic arguments, but *number* were provided\
+> the missing variadic argument *index* is required by format string '*format_string*'\
+> this argument is used by a conversion specifier\
+> this argument is used as a field width\
+> this argument is used as a precision\
 > this argument is used as a buffer size
 
 The compiler detected a mismatch between the number of arguments required to satisfy the placeholders in a format string, and the number of arguments supplied. Correct use of the printf and scanf families of variadic functions requires that you supply as many arguments as specified by the format string. Certain placeholders require additional arguments, to specify the width, precision, or buffer size, as well as an argument for the content. A mismatch generally means there is a bug in your code.
diff --git a/docs/windows/attributes/db-command.md b/docs/windows/attributes/db-command.md
@@ -27,11 +27,11 @@ A command string containing the text of an OLE DB command. A simple example is:
 
 The *command* syntax is as follows:
 
-> binding parameter block 1
-> &nbsp;&nbsp;OLE DB command
-> binding parameter block 2
-> &nbsp;&nbsp;continuation of OLE DB command
-> binding parameter block 3
+> binding parameter block 1\
+> &nbsp;&nbsp;OLE DB command\
+> binding parameter block 2\
+> &nbsp;&nbsp;continuation of OLE DB command\
+> binding parameter block 3\
 > ...
 
 A *binding parameter block* is defined as follows:
