1750982, fixed column header missing suggestions.

john-par · john-par · commit 406ca8c9bb1b · 2020-07-27T13:17:17.000-07:00
diff --git a/docs/connect/oledb/ole-db-date-time/conversions-performed-from-client-to-server.md b/docs/connect/oledb/ole-db-date-time/conversions-performed-from-client-to-server.md
@@ -64,8 +64,8 @@ ms.author: pelopes
 |15|Conversion semantics prior to [!INCLUDE[ssKatmai](../../../includes/sskatmai-md.md)] for **datetime** are maintained. Seconds are rounded to the nearest 300th of a second.|  
 |16|The conversion behavior of a value (of a given type) embedded in a SSVARIANT client struct is the same as the behavior of the same value and type when not embedded in a SSVARIANT client struct.|  
   
-|Type|Length (in chars)|Scale|  
-|-|-|-|  
+| Type | Length (in chars) | Scale |  
+| ---- | ----------------- | ----- |  
 |DBTIME2|8, 10..18|0,1..9|  
 |DBTIMESTAMP|19, 21..29|0,1..9|  
 |DBTIMESTAMPOFFSET|26, 28..36|0,1..9|  
diff --git a/docs/relational-databases/native-client-odbc-api/sqldescribecol.md b/docs/relational-databases/native-client-odbc-api/sqldescribecol.md
@@ -31,8 +31,8 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
 ## SQLDescribeCol Support for Enhanced Date and Time Features  
  The values returned for date/time types are as follows:  
   
-||*DataTypePtr*|*ColumnSizePtr*|*DecimalDigitsPtr*|  
-|-|-------------------|---------------------|------------------------|  
+| Attribute | *DataTypePtr* | *ColumnSizePtr* | *DecimalDigitsPtr* |  
+| --------- | ------------- |---------------- | ------------------ |  
 |datetime|SQL_TYPE_TIMESTAMP|23|3|  
 |smalldatetime|SQL_TYPE_TIMESTAMP|16|0|  
 |date|SQL_TYPE_DATE|10|0|  
diff --git a/docs/relational-databases/native-client-odbc-api/sqldescribeparam.md b/docs/relational-databases/native-client-odbc-api/sqldescribeparam.md
@@ -69,8 +69,8 @@ SQLPrepare(hstmt, "{call master..sp_who(?)}", SQL_NTS);
 ## SQLDescribeParam Support for Enhanced Date and Time Features  
  The values returned for date/time types are as follows:  
   
-||*DataTypePtr*|*ParameterSizePtr*|*DecimalDigitsPtr*|  
-|-|-------------------|------------------------|------------------------|  
+| Attribute | *DataTypePtr* | *ParameterSizePtr* | *DecimalDigitsPtr* |  
+| --------- | ------------- | ------------------ | ------------------ |  
 |datetime|SQL_TYPE_TIMESTAMP|23|3|  
 |smalldatetime|SQL_TYPE_TIMESTAMP|16|0|  
 |date|SQL_TYPE_DATE|10|0|  
diff --git a/docs/relational-databases/native-client-odbc-api/sqlgetdescrec.md b/docs/relational-databases/native-client-odbc-api/sqlgetdescrec.md
@@ -41,8 +41,8 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
 ## SQLGetDescRec Support for Enhanced Date and Time Features  
  The values returned for date/time types are as follows:  
   
-||*TypePtr*|*SubTypePtr*|*LengthPtr*|*PrecisionPtr*|*ScalePtr*|  
-|-|---------------|------------------|-----------------|--------------------|----------------|  
+| Attribute | *TypePtr* | *SubTypePtr* | *LengthPtr* | *PrecisionPtr* | *ScalePtr* |  
+| --------- | --------- | ------------ | ----------- | -------------- | ---------- |  
 |datetime|SQL_DATETIME|SQL_CODE_TIMESTAMP|4|3|3|  
 |smalldatetime|SQL_DATETIME|SQL_CODE_TIMESTAMP|8|0|0|  
 |date|SQL_DATETIME|SQL_CODE_DATE|6|0|0|  
diff --git a/docs/relational-databases/native-client-odbc-api/sqlsetdescrec.md b/docs/relational-databases/native-client-odbc-api/sqlsetdescrec.md
@@ -40,8 +40,8 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
 ## SQLSetDescRec Support for Enhanced Date and Time Features  
  The values allowed for date/time types are as follows:  
   
-||*Type*|*SubType*|*Length*|*Precision*|*Scale*|  
-|-|------------|---------------|--------------|-----------------|-------------|  
+| Attribute | *Type* | *SubType* | *Length* | *Precision* | *Scale* |
+| --------- | ------ | --------- | -------- | ----------- | ------- |
 |datetime|SQL_DATETIME|SQL_CODE_TIMESTAMP|4|3|3|  
 |smalldatetime|SQL_SQL_DATETIME|SQL_CODE_TIMESTAMP|8|0|0|  
 |date|SQL_DATETIME|SQL_CODE_DATE|6|0|0|  
diff --git a/docs/relational-databases/native-client-odbc-date-time/datetime-data-type-conversions-from-c-to-sql.md b/docs/relational-databases/native-client-odbc-date-time/datetime-data-type-conversions-from-c-to-sql.md
@@ -21,23 +21,22 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
   
  The conversions described in the following table apply to conversions made on the client. In cases where the client specifies fractional second precision for a parameter that differs from that defined on the server, the client conversion might succeed but the server will return an error when **SQLExecute** or **SQLExecuteDirect** is called. In particular, ODBC treats any truncation of fractional seconds as an error, whereas the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] behavior is to round; for example, rounding occurs when you go from **datetime2(6)** to **datetime2(2)**. Datetime column values are rounded to 1/300th of a second and smalldatetime columns have seconds set to zero by the server.  
   
-|||||||||  
-|-|-|-|-|-|-|-|-|  
-||SQL_TYPE_DATE|SQL_TYPE_TIME|SQL_SS_TIME2|SQL_TYPE_TIMESTAMP|SQL_SS_TIMSTAMPOFFSET|SQL_CHAR|SQL_WCHAR|  
-|SQL_C_DATE|1|-|-|1,6|1,5,6|1,13|1,13|  
-|SQL_C_TIME|-|1|1|1,7|1,5,7|1,13|1,13|  
-|SQL_C_SS_TIME2|-|1,3|1,10|1,7|1,5,7|1,13|1,13|  
-|SQL_C_BINARY(SQL_SS_TIME2_STRUCT)|N/A|N/A|1,10,11|N/A|N/A|N/A|N/A|  
-|SQL_C_TYPE_TIMESTAMP|1,2|1,3,4|1,4,10|1,10|1,5,10|1,13|1,13|  
-|SQL_C_SS_TIMESTAMPOFFSET|1,2,8|1,3,4,8|1,4,8,10|1,8,10|1,10|1,13|1,13|  
-|SQL_C_BINARY(SQL_SS_TIMESTAMPOFFSET_STRUCT)|N/A|N/A|N/A|N/A|1,10,11|N/A|N/A|  
-|SQL_C_CHAR/SQL_WCHAR (date)|9|9|9|9,6|9,5,6|N/A|N/A|  
-|SQL_C_CHAR/SQL_WCHAR (time2)|9|9,3|9,10|9,7,10|9,5,7,10|N/A|N/A|  
-|SQL_C_CHAR/SQL_WCHAR (datetime)|9,2|9,3,4|9,4,10|9,10|9,5,10|N/A|N/A|  
-|SQL_C_CHAR/SQL_WCHAR (datetimeoffset)|9,2,8|9,3,4,8|9,4,8,10|9,8,10|9,10|N/A|N/A|  
-|SQL_C_BINARY(SQL_DATE_STRUCT)|1,11|N/A|N/A|N/A|N/A|N/A|N/A|  
-|SQL_C_BINARY(SQL_TIME_STRUCT)|N/A|N/A|N/A|N/A|N/A|N/A|N/A|  
-|SQL_C_BINARY(SQL_TIMESTAMP_STRUCT)|N/A|N/A|N/A|N/A|N/A|N/A|N/A|  
+|   | SQL_TYPE_DATE | SQL_TYPE_TIME | SQL_SS_TIME2 | SQL_TYPE_TIMESTAMP | SQL_SS_TIMSTAMPOFFSET | SQL_CHAR | SQL_WCHAR |
+| - | ------------- | ------------- | ------------ | ------------------ | --------------------- | -------- | --------- |
+| **SQL_C_DATE** |1|-|-|1,6|1,5,6|1,13|1,13|  
+| **SQL_C_TIME** |-|1|1|1,7|1,5,7|1,13|1,13|  
+| **SQL_C_SS_TIME2** |-|1,3|1,10|1,7|1,5,7|1,13|1,13|  
+| **SQL_C_BINARY(SQL_SS_TIME2_STRUCT)** |N/A|N/A|1,10,11|N/A|N/A|N/A|N/A|  
+| **SQL_C_TYPE_TIMESTAMP** |1,2|1,3,4|1,4,10|1,10|1,5,10|1,13|1,13|  
+| **SQL_C_SS_TIMESTAMPOFFSET** |1,2,8|1,3,4,8|1,4,8,10|1,8,10|1,10|1,13|1,13|  
+| **SQL_C_BINARY(SQL_SS_TIMESTAMPOFFSET_STRUCT)** |N/A|N/A|N/A|N/A|1,10,11|N/A|N/A|  
+| **SQL_C_CHAR/SQL_WCHAR (date)** |9|9|9|9,6|9,5,6|N/A|N/A|  
+| **SQL_C_CHAR/SQL_WCHAR (time2)** |9|9,3|9,10|9,7,10|9,5,7,10|N/A|N/A|  
+| **SQL_C_CHAR/SQL_WCHAR (datetime)** |9,2|9,3,4|9,4,10|9,10|9,5,10|N/A|N/A|  
+| **SQL_C_CHAR/SQL_WCHAR (datetimeoffset)** |9,2,8|9,3,4,8|9,4,8,10|9,8,10|9,10|N/A|N/A|  
+| **SQL_C_BINARY(SQL_DATE_STRUCT)** |1,11|N/A|N/A|N/A|N/A|N/A|N/A|  
+| **SQL_C_BINARY(SQL_TIME_STRUCT)** |N/A|N/A|N/A|N/A|N/A|N/A|N/A|  
+| **SQL_C_BINARY(SQL_TIMESTAMP_STRUCT)** |N/A|N/A|N/A|N/A|N/A|N/A|N/A|  
   
 ## Key to Symbols  
   
@@ -73,10 +72,10 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
   
      The number of fractional seconds digits (the scale) is determined from the destination column's size according to the following table:  
   
-    ||||  
-    |-|-|-|  
-    |Type|Implied Scale<br /><br /> 0|Implied Scale<br /><br /> 1..9|  
-    |SQL_C_TYPE_TIMESTAMP|19|21..29|  
+    |   | Implied Scale | Implied Scale |
+    | - | ------------- | ------------- |
+    | **Type** | 0 | 1..9 |  
+    |**SQL_C_TYPE_TIMESTAMP** |19|21..29|  
   
      However, for SQL_C_TYPE_TIMESTAMP, if the fractional seconds can be represented with three digits without data loss and the column size is 23 or larger, then exactly three fractional seconds' digits are generated. This behavior ensures backwards compatibility for applications developed using older ODBC drivers.  
   
diff --git a/docs/relational-databases/native-client-odbc-date-time/datetime-data-type-conversions-from-sql-to-c.md b/docs/relational-databases/native-client-odbc-date-time/datetime-data-type-conversions-from-sql-to-c.md
@@ -21,15 +21,14 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
   
 ## Conversions  
   
-||||||||||  
-|-|-|-|-|-|-|-|-|-|  
-||SQL_C_DATE|SQL_C_TIME|SQL_C_TIMESTAMP|SQL_C_SS_TIME2|SQL_C_SS_TIMESTAMPOFFSET|SQL_C_BINARY|SQL_C_CHAR|SQL_C_WCHAR|  
-|SQL_CHAR|2,3,4,5|2,3,6,7,8|2,3,9,10,11|2,3,6,7|2,3,9,10,11|1|1|1|  
-|SQL_WCHAR|2,3,4,5|2,3,6,7,8|2,3,9,10,11|2,3,6,7|2,3,9,10,11|1|1|1|  
-|SQL_TYPE_DATE|OK|12|13|12|13,23|14|16|16|  
-|SQL_SS_TIME2|12|8|15|OK|10,23|17|16|16|  
-|SQL_TYPE_TIMESTAMP|18|7,8|OK|7|23|19|16|16|  
-|SQL_SS_TIMESTAMPOFFSET|18,22|7,8,20|20|7,20|OK|21|16|16|  
+|   | SQL_C_DATE | SQL_C_TIME | SQL_C_TIMESTAMP | SQL_C_SS_TIME2 | SQL_C_SS_TIMESTAMPOFFSET | SQL_C_BINARY | SQL_C_CHAR | SQL_C_WCHAR |
+| - | ---------- | ---------- | --------------- | -------------- | ------------------------ | ------------ | ---------- | ----------- |
+| **SQL_CHAR** |2,3,4,5|2,3,6,7,8|2,3,9,10,11|2,3,6,7|2,3,9,10,11|1|1|1|  
+| **SQL_WCHAR** |2,3,4,5|2,3,6,7,8|2,3,9,10,11|2,3,6,7|2,3,9,10,11|1|1|1|  
+| **SQL_TYPE_DATE** |OK|12|13|12|13,23|14|16|16|  
+| **SQL_SS_TIME2** |12|8|15|OK|10,23|17|16|16|  
+| **SQL_TYPE_TIMESTAMP** |18|7,8|OK|7|23|19|16|16|  
+| **SQL_SS_TIMESTAMPOFFSET** |18,22|7,8,20|20|7,20|OK|21|16|16|  
   
 ## Key to Symbols  
   
diff --git a/docs/relational-databases/native-client/sql-server-native-client-error-mssqlserver-50000.md b/docs/relational-databases/native-client/sql-server-native-client-error-mssqlserver-50000.md
@@ -19,8 +19,8 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
     
 ## Details  
   
-|||  
-|-|-|  
+| Attribute | Value |
+| --------- | ----- |
 |Product Name|SQL Server|  
 |Product Version|11.0|  
 |Event ID|50000|  
diff --git a/docs/relational-databases/security/authentication-access/application-roles.md b/docs/relational-databases/security/authentication-access/application-roles.md
@@ -51,8 +51,8 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||=sqlallproducts-allversio
   
 ## Related Tasks  
   
-|||  
-|-|-|  
+| Task | Type |
+| ---- | ---- |
 |Create an application role.|[Create an Application Role](../../../relational-databases/security/authentication-access/create-an-application-role.md) and [CREATE APPLICATION ROLE &#40;Transact-SQL&#41;](../../../t-sql/statements/create-application-role-transact-sql.md)|  
 |Alter an application role.|[ALTER APPLICATION ROLE &#40;Transact-SQL&#41;](../../../t-sql/statements/alter-application-role-transact-sql.md)|  
 |Delete an application role.|[DROP APPLICATION ROLE &#40;Transact-SQL&#41;](../../../t-sql/statements/drop-application-role-transact-sql.md)|  
diff --git a/docs/relational-databases/security/encryption/choose-an-encryption-algorithm.md b/docs/relational-databases/security/encryption/choose-an-encryption-algorithm.md
@@ -60,8 +60,8 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
   
 ## Related Tasks  
   
-|||  
-|-|-|  
+| Task | Type |
+| ---- | ---- |
 |Encrypting using a symmetric key.|[CREATE SYMMETRIC KEY &#40;Transact-SQL&#41;](../../../t-sql/statements/create-symmetric-key-transact-sql.md)|  
 |Encrypting using an asymmetric key.|[CREATE ASYMMETRIC KEY &#40;Transact-SQL&#41;](../../../t-sql/statements/create-asymmetric-key-transact-sql.md)|  
 |Encrypting using a certificate.|[CREATE CERTIFICATE &#40;Transact-SQL&#41;](../../../t-sql/statements/create-certificate-transact-sql.md)|  
diff --git a/docs/relational-databases/security/metadata-visibility-configuration.md b/docs/relational-databases/security/metadata-visibility-configuration.md
@@ -37,21 +37,43 @@ GO
   
 ## Scope and Impact of Metadata Visibility Configuration  
  Metadata visibility configuration only applies to the following securables.  
-  
-|||  
-|-|-|  
-|Catalog views|[!INCLUDE[ssDE](../../includes/ssde-md.md)] **sp_help** stored procedures|  
-|Metadata exposing built-in functions|Information schema views|  
-|Compatibility views|Extended properties|  
+
+:::row:::
+    :::column:::
+        Catalog views
+
+        Metadata exposing built-in functions
+
+        Compatibility views
+    :::column-end:::
+    :::column:::
+         [!INCLUDE[ssDE](../../includes/ssde-md.md)] **sp_help** stored procedures
+
+        Information schema views
+
+        Extended properties
+    :::column-end:::
+:::row-end:::
   
  Metadata visibility configuration does not apply to the following securables.  
-  
-|||  
-|-|-|  
-|Log shipping system tables|[!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent system tables|  
-|Database maintenance plan system tables|Backup system tables|  
-|Replication system tables|Replication and [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent **sp_help** stored procedures|  
-  
+
+:::row:::
+    :::column:::
+        Log shipping system tables
+
+        Database maintenance plan system tables
+
+        Replication system tables
+    :::column-end:::
+    :::column:::
+         [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent system tables
+
+        Backup system tables
+
+        Replication and [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent **sp_help** stored procedures
+    :::column-end:::
+:::row-end:::
+
  Limited metadata accessibility means the following:  
   
 -   Applications that assume **public** metadata access will break.  
@@ -171,19 +193,45 @@ GO
   
  The metadata that is returned by the DB_ID() and DB_NAME() functions is visible to all users.  
   
- The following table lists the catalog views that are visible to the **public** role.  
-  
-|||  
-|-|-|  
-|**sys.partition_functions**|**sys.partition_range_values**|  
-|**sys.partition_schemes**|**sys.data_spaces**|  
-|**sys.filegroups**|**sys.destination_data_spaces**|  
-|**sys.database_files**|**sys.allocation_units**|  
-|**sys.partitions**|**sys.messages**|  
-|**sys.schemas**|**sys.configurations**|  
-|**sys.sql_dependencies**|**sys.type_assembly_usages**|  
-|**sys.parameter_type_usages**|**sys.column_type_usages**|  
-  
+ This is a list of the catalog views that are visible to the **public** role.  
+
+:::row:::
+    :::column:::
+        **sys.partition_functions**
+
+        **sys.partition_schemes**
+
+        **sys.filegroups**
+
+        **sys.database_files**
+
+        **sys.partitions**
+
+        **sys.schemas**
+
+        **sys.sql_dependencies**
+
+        **sys.parameter_type_usages**
+    :::column-end:::
+    :::column:::
+        **sys.partition_range_values**
+
+        **sys.data_spaces**
+
+        **sys.destination_data_spaces**
+
+        **sys.allocation_units**
+
+        **sys.messages**
+
+        **sys.configurations**
+
+        **sys.type_assembly_usages**
+
+        **sys.column_type_usages**
+    :::column-end:::
+:::row-end:::
+
 ## See Also  
  [GRANT &#40;Transact-SQL&#41;](../../t-sql/statements/grant-transact-sql.md)   
  [DENY &#40;Transact-SQL&#41;](../../t-sql/statements/deny-transact-sql.md)   
diff --git a/docs/relational-databases/security/sql-server-certificates-and-asymmetric-keys.md b/docs/relational-databases/security/sql-server-certificates-and-asymmetric-keys.md
@@ -62,9 +62,8 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
 ## Tools  
  [!INCLUDE[msCoName](../../includes/msconame-md.md)] provides tools and utilities that will generate certificates and strong name key files. These tools offer a richer amount of flexibility in the key generation process than the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] syntax. You can use these tools to create RSA keys with more complex key lengths and then import them into [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. The following table shows where to find these tools.  
   
-|||  
-|-|-|  
-|Tool|Purpose|  
+| Tool | Purpose |
+| ---- | ------- |
 |[New-SelfSignedCertificate](/powershell/module/pkiclient/new-selfsignedcertificate)|Creates self-signed certificates.|  
 |[makecert](/windows/desktop/SecCrypto/makecert)|Creates certificates. Deprecated in favor of **New-SelfSignedCertificate**.|  
 |[sn](/dotnet/framework/tools/sn-exe-strong-name-tool)|Creates strong names for symmetric keys.|  
diff --git a/docs/relational-databases/sqlxml-annotated-xsd-schemas-xpath-queries/xpath-data-types-sqlxml-4-0.md b/docs/relational-databases/sqlxml-annotated-xsd-schemas-xpath-queries/xpath-data-types-sqlxml-4-0.md
@@ -120,12 +120,11 @@ CONVERT(float(CONVERT(money, m)) + CONVERT(float(53), 3) = CONVERT(float(53), 3)
   
  As shown in the following table, this is the same conversion that is applied for other XPath expressions (such as literals or compound expressions).  
   
-||||||  
-|-|-|-|-|-|  
-||X is unknown|X is **string**|X is **number**|X is **boolean**|  
-|string(X)|CONVERT (nvarchar(4000), X, 126)|-|CONVERT (nvarchar(4000), X, 126)|CASE WHEN X THEN N'true' ELSE N'false' END|  
-|number(X)|CONVERT (float(53), X)|CONVERT (float(53), X)|-|CASE WHEN X THEN 1 ELSE 0 END|  
-|boolean(X)|-|LEN(X) > 0|X != 0|-|  
+|   | X is unknown | X is string | X is number | X is boolean |
+| - | ------------ | ----------- | ----------- | ------------ |
+| **string(X)** |CONVERT (nvarchar(4000), X, 126)|-|CONVERT (nvarchar(4000), X, 126)|CASE WHEN X THEN N'true' ELSE N'false' END|  
+| **number(X)** |CONVERT (float(53), X)|CONVERT (float(53), X)|-|CASE WHEN X THEN 1 ELSE 0 END|  
+| **boolean(X)** |-|LEN(X) > 0|X != 0|-|  
   
 ## Examples  
   
diff --git a/docs/relational-databases/stored-procedures/ole-automation-result-sets.md b/docs/relational-databases/stored-procedures/ole-automation-result-sets.md
@@ -30,9 +30,8 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
   
  When all data values in a column share the same data type, that data type is used for the whole column. When data values in a column are different data types, the data type of the whole column is chosen based on the following table. To use the following table, find one data type along the left row axis and a second data type along the top column axis. The intersection of the row and column describes the data type of the result set column.  
   
-||||||||  
-|-|-|-|-|-|-|-|  
-||**int**|**float**|**money**|**datetime**|**varchar**|**nvarchar**|  
+|   | **int** | **float** | **money** | **datetime** | **varchar** | **nvarchar** |
+| - | ------- | --------- | --------- | ------------ | ----------- | ------------ |
 |**int**|**int**|**float**|**money**|**varchar**|**varchar**|**nvarchar**|  
 |**float**|**float**|**float**|**money**|**varchar**|**varchar**|**nvarchar**|  
 |**money**|**money**|**money**|**money**|**varchar**|**varchar**|**nvarchar**|  
diff --git a/docs/relational-databases/stored-procedures/stored-procedures-database-engine.md b/docs/relational-databases/stored-procedures/stored-procedures-database-engine.md
@@ -73,9 +73,8 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
   
 ## Related Tasks  
   
-|||  
-|-|-|  
-|**Task Description**|**Topic**|  
+| Task Description | Topic |
+| ---------------- | ----- |
 |Describes how to create a stored procedure.|[Create a Stored Procedure](../../relational-databases/stored-procedures/create-a-stored-procedure.md)|  
 |Describes how to modify a stored procedure.|[Modify a Stored Procedure](../../relational-databases/stored-procedures/modify-a-stored-procedure.md)|  
 |Describes how to delete a stored procedure.|[Delete a Stored Procedure](../../relational-databases/stored-procedures/delete-a-stored-procedure.md)|  
diff --git a/docs/relational-databases/system-catalog-views/policy-based-management-views-transact-sql.md b/docs/relational-databases/system-catalog-views/policy-based-management-views-transact-sql.md
@@ -19,14 +19,26 @@ ms.author: vanto
 [!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
 
   Policy-Based Management has the following views for displaying information about Policy-Based Management policies, conditions, expressions, groups, and filters. These views are in the msdb database and are owned by the dbo schema.  
-  
-|||  
-|-|-|  
-|[syspolicy_conditions](../../relational-databases/system-catalog-views/syspolicy-conditions-transact-sql.md)|[syspolicy_policy_group_subscriptions](../../relational-databases/system-catalog-views/syspolicy-policy-category-subscriptions-transact-sql.md)|  
-|[syspolicy_policies](../../relational-databases/system-catalog-views/syspolicy-policies-transact-sql.md)|[syspolicy_policy_groups](../../relational-databases/system-catalog-views/syspolicy-policy-categories-transact-sql.md)|  
-|[syspolicy_policy_execution_history](../../relational-databases/system-catalog-views/syspolicy-policy-execution-history-transact-sql.md)|[syspolicy_system_health_state](../../relational-databases/system-catalog-views/syspolicy-system-health-state-transact-sql.md)|  
-|[syspolicy_policy_execution_history_details](../../relational-databases/system-catalog-views/syspolicy-policy-execution-history-details-transact-sql.md)||  
-  
+
+:::row:::
+    :::column:::
+        [syspolicy_conditions](../../relational-databases/system-catalog-views/syspolicy-conditions-transact-sql.md)
+
+        [syspolicy_policies](../../relational-databases/system-catalog-views/syspolicy-policies-transact-sql.md)
+
+        [syspolicy_policy_execution_history](../../relational-databases/system-catalog-views/syspolicy-policy-execution-history-transact-sql.md)
+
+        [syspolicy_policy_execution_history_details](../../relational-databases/system-catalog-views/syspolicy-policy-execution-history-details-transact-sql.md)
+    :::column-end:::
+    :::column:::
+        [syspolicy_policy_group_subscriptions](../../relational-databases/system-catalog-views/syspolicy-policy-category-subscriptions-transact-sql.md)
+
+        [syspolicy_policy_groups](../../relational-databases/system-catalog-views/syspolicy-policy-categories-transact-sql.md)
+
+        [syspolicy_system_health_state](../../relational-databases/system-catalog-views/syspolicy-system-health-state-transact-sql.md)
+    :::column-end:::
+:::row-end:::
+
 ## See Also  
  [Administer Servers by Using Policy-Based Management](../../relational-databases/policy-based-management/administer-servers-by-using-policy-based-management.md)  
   
diff --git a/docs/relational-databases/system-catalog-views/sys-pdw-loader-run-stages-transact-sql.md b/docs/relational-databases/system-catalog-views/sys-pdw-loader-run-stages-transact-sql.md
diff --git a/docs/relational-databases/system-dynamic-management-views/sys-dm-pdw-exec-connections-transact-sql.md b/docs/relational-databases/system-dynamic-management-views/sys-dm-pdw-exec-connections-transact-sql.md
diff --git a/docs/relational-databases/views/create-indexed-views.md b/docs/relational-databases/views/create-indexed-views.md
diff --git a/docs/relational-databases/xml/selective-xml-indexes-sxi.md b/docs/relational-databases/xml/selective-xml-indexes-sxi.md
diff --git a/docs/sql-server/install/uninstall-an-existing-instance-of-sql-server-setup.md b/docs/sql-server/install/uninstall-an-existing-instance-of-sql-server-setup.md
