Table formatting correction correction

chrisda · chrisda · commit 4f0dae6bff7d · 2021-04-21T10:03:04.000-07:00
diff --git a/exchange/docs-conceptual/cmdlet-property-sets.md b/exchange/docs-conceptual/cmdlet-property-sets.md
@@ -27,7 +27,7 @@ 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>
+<br>
 
 ****
 
@@ -58,7 +58,7 @@ 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>
+<br>
 
 ****
 
@@ -100,7 +100,7 @@ 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>
+<br>
 
 ****
 
@@ -119,7 +119,7 @@ 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>
+<br>
 
 ****
 
diff --git a/exchange/docs-conceptual/exchange-cmdlet-syntax.md b/exchange/docs-conceptual/exchange-cmdlet-syntax.md
@@ -27,7 +27,7 @@ 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>
+<br>
 
 ****
 
@@ -111,7 +111,7 @@ 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>
+<br>
 
 ****
 
diff --git a/exchange/docs-conceptual/exchange-online-powershell-v2.md b/exchange/docs-conceptual/exchange-online-powershell-v2.md
@@ -47,7 +47,7 @@ The Exchange Online cmdlets in the EXO V2 module are meant to replace their olde
 
 The improved Exchange Online PowerShell cmdlets that are only available in the EXO V2 module are listed in the following table:
 
-<br><br>
+<br>
 
 ****
 
@@ -66,7 +66,7 @@ The improved Exchange Online PowerShell cmdlets that are only available in the E
 
 The connection-related cmdlets that are available in the EXO V2 module are listed in the following table:
 
-<br><br>
+<br>
 
 ****
 
@@ -79,7 +79,7 @@ The connection-related cmdlets that are available in the EXO V2 module are liste
 
 Miscellaneous Exchange Online cmdlets that happen to be in the EXO V2 module are listed in the following table:
 
-<br><br>
+<br>
 
 ****
 
diff --git a/exchange/docs-conceptual/filter-properties.md b/exchange/docs-conceptual/filter-properties.md
@@ -61,7 +61,7 @@ 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>
+<br>
 
 ****
 
diff --git a/exchange/docs-conceptual/filters-v2.md b/exchange/docs-conceptual/filters-v2.md
@@ -33,7 +33,7 @@ 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>
+<br>
 
 ****
 
diff --git a/exchange/docs-conceptual/recipient-filters.md b/exchange/docs-conceptual/recipient-filters.md
@@ -196,7 +196,7 @@ 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>
+  <br>
 
   ****
 
@@ -237,7 +237,7 @@ 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>
+<br>
 
 ****
 
diff --git a/exchange/docs-conceptual/recipientfilter-properties.md b/exchange/docs-conceptual/recipientfilter-properties.md
@@ -48,7 +48,7 @@ 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>
+<br>
 
 ****
 
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,7 +100,7 @@ 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>
+     <br>
 
      ****
 
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,7 +104,7 @@ 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>
+     <br>
 
      ****
 
diff --git a/exchange/docs-conceptual/values-for-custompropertynames-parameter.md b/exchange/docs-conceptual/values-for-custompropertynames-parameter.md
@@ -23,7 +23,7 @@ The _CustomPropertyNames_ parameter on the [Get-CalendarDiagnosticObjects](/powe
 
 The article describes the valid values for the _CustomPropertyNames_ parameter.
 
-<br><br>
+<br>
 
 ****
 
