Table formatting fixes

chrisda · chrisda · commit 8fe964ecb84a · 2021-04-21T09:58:34.000-07:00
diff --git a/exchange/docs-conceptual/cmdlet-property-sets.md b/exchange/docs-conceptual/cmdlet-property-sets.md
@@ -27,6 +27,8 @@ For more information about filtering in the EXO V2 module, see [Filters in the E
 
 The available property sets for the **Get-EXOCasMailbox** cmdlet and the properties they contain are described in the following table:
 
+<br><br>
+
 ****
 
 |PropertySet|Properties|
@@ -56,6 +58,10 @@ For more information, see:
 
 The available property sets for the **Get-EXOMailbox** cmdlet and the properties they contain are described in the following table:
 
+<br><br>
+
+****
+
 |PropertySet|Properties|
 |---|---|
 |**Minimum**|Alias <br> DisplayName <br> DistinguishedName <br> EmailAddresses <br> ExchangeVersion <br> ExternalDirectoryObjectId <br> Guid <br> Id <br> Name <br> OrganizationId <br> PrimarySmtpAddress <br> RecipientType <br> RecipientTypeDetails <br> UserPrincipalName|
@@ -94,6 +100,8 @@ For more information, see:
 
 The available property sets for the **Get-EXOMailboxStatistics** cmdlet and the properties they contain are described in the following table:
 
+<br><br>
+
 ****
 
 |PropertySet|Properties|
@@ -111,6 +119,8 @@ For more information, see:
 
 The available property sets for the **Get-EXORecipient** cmdlet and the properties they contain are described in the following table:
 
+<br><br>
+
 ****
 
 |PropertySet|Properties|
diff --git a/exchange/docs-conceptual/exchange-cmdlet-syntax.md b/exchange/docs-conceptual/exchange-cmdlet-syntax.md
@@ -27,6 +27,10 @@ This article explains these conventions, and also the syntax that's required to
 
 Exchange PowerShell help follows conventions that indicate what's required or optional, and how to enter parameters and values when you run a command. These command conventions are listed in the following table.
 
+<br><br>
+
+****
+
 |Symbol|Description|
 |---|---|
 |`-`|A hyphen indicates a parameter. For example, `-Identity`.|
@@ -107,6 +111,10 @@ If you enclose the string in single quotation marks, the only special character
 
 The following table shows the valid operators that you can use in an Exchange command. Some of these symbols were also described in the earlier [Command conventions in Exchange PowerShell](#command-conventions-in-exchange-powershell) section. However, these symbols have different meanings when they're used on the command line as operators. For example, the minus sign that's used to indicate a parameter can also be used in a command as a mathematical operator.
 
+<br><br>
+
+****
+
 |Operator|Description|
 |---|---|
 |`=`|The equal sign is used as an assignment character. The value on the right side of the equal sign is assigned to the variable on the left side of the equal sign. The following characters are also assignment characters: <ul><li>`+=`: Add the value on the right side of the equal sign to the current value that's contained in the variable on the left side of the equal sign.</li><li>`-=`: Subtract the value on the right side of the equal sign from the current value that's contained in the variable on the left side of the equal sign.</li><li>`*=`: Multiply the current value of the variable on the left side of the equal sign by the value that's specified on the right side of the equal sign.</li><li>`/=`: Divide the current value of the variable on the left side of the equal sign by the value that's specified on the right side of the equal sign.</li><li> `%=`: Modify the current value of the variable on the left side of the equal sign by the value that's specified on the right side of the equal sign.</li></ul>|
diff --git a/exchange/docs-conceptual/filter-properties.md b/exchange/docs-conceptual/filter-properties.md
@@ -61,6 +61,8 @@ The properties that have been _confirmed_ to work with the _Filter_ parameter in
 
 - For filtering considerations for connections using the Exchange Online PowerShell v2 module, see [Filters in the EXO V2 module](filters-v2.md).
 
+<br><br>
+
 ****
 
 |Property name|LDAP display name|Available on cmdlets|Value|Comments|
diff --git a/exchange/docs-conceptual/filters-v2.md b/exchange/docs-conceptual/filters-v2.md
@@ -33,6 +33,8 @@ Generally, you get much better performance in PowerShell cmdlets with server-sid
 
 Although the EXO V2 module supports the majority of filterable attributes, the following attributes are currently not supported for filtering:
 
+<br><br>
+
 ****
 
 |Cmdlet|Attribute|LDAP Display Name|
diff --git a/exchange/docs-conceptual/recipient-filters.md b/exchange/docs-conceptual/recipient-filters.md
@@ -196,6 +196,8 @@ When creating your own custom OPath filters, consider the following items:
 
   The compatibility of search criteria and the valid characters that you can use to enclose the whole OPath filter are summarized in the following table:
 
+  <br><br>
+
   ****
 
   |Search value|OPath filter <br> enclosed in <br> double quotation marks|OPath filter <br> enclosed in <br> single quotation marks|OPath filter enclosed in <br> braces|
@@ -235,11 +237,13 @@ When creating your own custom OPath filters, consider the following items:
 
 The following table contains links to articles that will help you learn more about the filterable properties that you can use with Exchange recipient commands.
 
+<br><br>
+
 ****
 
 |Article|Description|
 |---|---|
 |[Filterable properties for the RecipientFilter parameter on Exchange cmdlets](recipientfilter-properties.md)|Learn more about the filterable properties that are available for the _RecipientFilter_ parameter.|
 |[Filterable properties for the Filter parameter on Exchange cmdlets](filter-properties.md) |Learn more about the filterable properties that are available for the _Filter_ parameter.|
 |[Filters in the EXO V2 module](filters-v2.md)|Learn about the considerations for filters when you connect to Exchange Online PowerShell using the Exchange Online PowerShell V2 module.|
-|
+|
diff --git a/exchange/docs-conceptual/recipientfilter-properties.md b/exchange/docs-conceptual/recipientfilter-properties.md
@@ -48,6 +48,8 @@ The recipient properties that have been *confirmed* to work with the _RecipientF
 
 - For filtering considerations for connections using the Exchange Online PowerShell v2 module, see [Filters in the EXO V2 module](filters-v2.md).
 
+<br><br>
+
 ****
 
 |Property name|LDAP display name|Value|Comments|
diff --git a/exchange/docs-conceptual/v1-module-mfa-connect-to-exo-powershell.md b/exchange/docs-conceptual/v1-module-mfa-connect-to-exo-powershell.md
@@ -100,6 +100,8 @@ You need to do the following steps in a browser that supports ClickOnce (for exa
 
    - The _\<ConnectionUri\>_ and _\<AzureADUri\>_ values depend on the nature of your Microsoft 365 organization as described in the following table:
 
+     <br><br>
+
      ****
 
      |Microsoft 365 offering|_ConnectionUri_ parameter value|_AzureADAuthorizationEndPointUri_ parameter value|
diff --git a/exchange/docs-conceptual/v1-module-mfa-connect-to-scc-powershell.md b/exchange/docs-conceptual/v1-module-mfa-connect-to-scc-powershell.md
@@ -104,6 +104,8 @@ You need to do the following steps in a browser that supports ClickOnce (for exa
 
    - The _\<ConnectionUri\>_ and _\<AzureADUri\>_ values depend on the location of your Microsoft 365 organization as described in the following table:
 
+     <br><br>
+
      ****
 
      |Microsoft 365 offering|_ConnectionUri_ parameter value|_AzureADAuthorizationEndPointUri_ parameter value|
