Fixes for table format

Author: Colin Robertson

docs/atl/understanding-parse-trees.md

@@ -12,15 +12,15 @@ You can define one or more parse trees in your registrar script, where each pars
 
 where:
 
-> \<root key> ::= HKEY_CLASSES_ROOT | HKEY_CURRENT_USER |\
-> &nbsp;&nbsp;&nbsp;&nbsp;HKEY_LOCAL_MACHINE | HKEY_USERS |\
-> &nbsp;&nbsp;&nbsp;&nbsp;HKEY_PERFORMANCE_DATA | HKEY_DYN_DATA |\
-> &nbsp;&nbsp;&nbsp;&nbsp;HKEY_CURRENT_CONFIG | HKCR | HKCU |\
-> &nbsp;&nbsp;&nbsp;&nbsp;HKLM | HKU | HKPD | HKDD | HKCC
+> \<root key> ::= HKEY_CLASSES_ROOT \| HKEY_CURRENT_USER \|\
+> &emsp;HKEY_LOCAL_MACHINE \| HKEY_USERS \|\
+> &emsp;HKEY_PERFORMANCE_DATA \| HKEY_DYN_DATA \|\
+> &emsp;HKEY_CURRENT_CONFIG \| HKCR \| HKCU \|\
+> &emsp;HKLM \| HKU \| HKPD \| HKDD \| HKCC
 
-> \<registry expression> ::= \<Add Key> | \<Delete Key>
+> \<registry expression> ::= \<Add Key> \| \<Delete Key>
 
-> \<Add Key> ::= [**ForceRemove** | **NoRemove** | **val**]\<Key Name> [\<Key Value>][{\<Add Key>}]
+> \<Add Key> ::= \[**ForceRemove** \| **NoRemove** \| **val**]\<Key Name> [\<Key Value>][{\<Add Key>}]
 
 > \<Delete Key> ::= **Delete**\<Key Name>
 
@@ -30,7 +30,7 @@ where:
 
 > \<Key Value> ::= \<Key Type>\<Key Name>
 
-> \<Key Type> ::= **s** | **d**
+> \<Key Type> ::= **s** \| **d**
 
 > \<Key Value> ::= **'**\<AlphaNumeric>**'**
 

docs/build/reference/d-preprocessor-definitions.md

@@ -11,8 +11,8 @@ Defines a preprocessing symbol for a source file.
 
 ## Syntax
 
-> **/D**\[ ]_name_[`=` | `#` [{ *string* | *number* }] ]\
-> **/D**\[ ]`"`_name_[`=` | `#` [{ *string* | *number* }] ]`"`
+> **/D**\[ ]_name_\[`=` \| `#` \[{ *string* \| *number* }] ]\
+> **/D**\[ ]`"`_name_\[`=` \| `#` \[{ *string* \| *number* }] ]`"`
 
 ## Remarks
 

docs/build/reference/genprofile-fastgenprofile-generate-profiling-instrumented-build.md

@@ -11,8 +11,8 @@ 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_}]\
-> **/FASTGENPROFILE**[**:**{[**COUNTER32**|**COUNTER64**]|[**EXACT**|**NOEXACT**]|**MEMMAX=**_#_|**MEMMIN=**_#_|[**PATH**|**NOPATH** ]|[**TRACKEH** |**NOTRACKEH** ]|**PGD=**_filename_}]
+> **/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
 

docs/build/reference/opt-optimizations.md

@@ -11,9 +11,9 @@ Controls the optimizations that LINK performs during a build.
 
 ## Syntax
 
-> **/OPT:**{**REF** | **NOREF**}\
-> **/OPT:**{**ICF**[**=**_iterations_] | **NOICF**}\
-> **/OPT:**{**LBR** | **NOLBR**}
+> **/OPT:**{**REF** \| **NOREF**}\
+> **/OPT:**{**ICF**\[**=**_iterations_] \| **NOICF**}\
+> **/OPT:**{**LBR** \| **NOLBR**}
 
 ## Arguments
 

docs/cppcx/crt-functions-not-supported-in-universal-windows-platform-apps.md

@@ -12,7 +12,7 @@ The following table lists the CRT functions that are unavailable when you build
 
 ## Unsupported CRT Functions
 
-|Function|Description|Workaround|
+| Function | Description | Workaround |
 |-|-|-|
 |`_beep` `_sleep` `_seterrormode`|These functions were obsolete in previous versions of the CRT. Also, the corresponding Win32 APIs are not available for UWP apps.|No workaround.|
 |`chdir` `_chdrive` `getcwd`|These functions are obsolete or are not thread-safe.|Use `_chdir`, `_getcwd` and related functions.|
@@ -32,7 +32,7 @@ The following table lists the CRT functions that are unavailable when you build
 
 The following functions are available in the CRT for UWP apps. However, use them only when you can't use the corresponding Win32 or Windows Runtime APIs, such as when you're porting large code bases:
 
-|Functions|Workaround|
+| Functions | Workaround |
 |-|-|
 |Single-byte string functions—for example, `strcat`, `strcpy`, `strlwr`, and so on.|Make your UWP apps strictly Unicode because all Win32 APIs and Windows Runtime APIs that are exposed use Unicode character sets only.  Single-byte functions were left for porting large code bases, but should otherwise be avoided. The corresponding wide char functions should be used instead when possible.|
 |Stream IO and low-level file IO functions—for example, `fopen`, `open`, and so on.|These functions are synchronous, which isn't recommended for UWP apps. In your UWP apps, use asynchronous APIs to open, read from, and write to files to prevent locking of the UI thread. Examples of such APIs are the ones in the `Windows::Storage::FileIO` class.|
@@ -41,7 +41,7 @@ The following functions are available in the CRT for UWP apps. However, use them
 
 Both the previously mentioned APIs and the following APIs are unavailable in Windows 8.x Store apps and Windows Phone 8.x apps.
 
-|Functions|Description|Workaround|
+| Functions | Description | Workaround |
 |-|-|-|
 |`_beginthread` `_beginthreadex` `_endthread` `_endthreadex`|Threading Win32 APIs are not available in Windows 8.x Store apps.|Use the `Windows Runtime Windows::System::Threading::ThreadPool` or `concurrency::task` instead.|
 |`_chdir` `_wchdir` `_getcwd` `_getdcwd` `_wgetcwd` `_wgetdcwd`|The concept of a working directory doesn't apply to Windows 8.x Store apps.|Use full paths instead.|