fixes

v-thepet · v-thepet · commit a5ba66c03f93 · 2021-03-25T17:11:32.000-07:00
diff --git a/docs/database-engine/configure-windows/server-configuration-options-sql-server.md b/docs/database-engine/configure-windows/server-configuration-options-sql-server.md
@@ -149,7 +149,7 @@ Self-configuring options are those that [!INCLUDE[ssNoVersion](../../includes/ss
 | [two digit year cutoff](../../database-engine/configure-windows/configure-the-two-digit-year-cutoff-server-configuration-option.md) (A) | 1753 | 9999 | 2049 |
 | [user connections](../../database-engine/configure-windows/configure-the-user-connections-server-configuration-option.md) (A, RR, SC) | 0 | 32767 | 0 |
 | [user options](../../database-engine/configure-windows/configure-the-user-options-server-configuration-option.md) | 0 | 32767 | 0 |
-| [xp_cmdshell](../../database-engine/configure-windows/xp-cmdshell-server-configuration-option.md) (A) | 0 | 1 | 0 |  |
+| [xp_cmdshell](../../database-engine/configure-windows/xp-cmdshell-server-configuration-option.md) (A) | 0 | 1 | 0 |
 
 ## See also
  [sp_configure &#40;Transact-SQL&#41;](../../relational-databases/system-stored-procedures/sp-configure-transact-sql.md) 
diff --git a/docs/integration-services/control-flow/file-system-task.md b/docs/integration-services/control-flow/file-system-task.md
@@ -130,7 +130,7 @@ ms.author: chugu
  **IsSourcePathVariable**  
  Indicate whether the destination path is stored in a variable. This property has the options listed in the following table.  
   
-|Value||  
+|Value|Description|  
 |-----------|-|  
 |**True**|The destination path is stored in a variable. Selecting this value displays the dynamic option, **SourceVariable**.|  
 |**False**|The destination path is specified in a File connection manager. Selecting this value displays the dynamic option, **DestinationVariable**.|  
diff --git a/docs/integration-services/system-views/catalog-operations-ssisdb-database.md b/docs/integration-services/system-views/catalog-operations-ssisdb-database.md
@@ -56,7 +56,7 @@ ms.author: chugu
 |`202`|**stop_operation**<br /><br /> (Stored procedure)|Project ID|**NULL**|  
 |`300`|**validate_project**<br /><br /> (Stored procedure)|Project ID|Project name|  
 |`301`|**validate_package**<br /><br /> (Stored procedure)|Project ID|Package name|  
-|`1000`|**configure_catalog**<br /><br /> (Stored procedure)|**NULL**|**NULL**||  
+|`1000`|**configure_catalog**<br /><br /> (Stored procedure)|**NULL**|**NULL**|
   
 ## Permissions  
  This view requires one of the following permissions:  
diff --git a/docs/linux/sql-server-linux-setup.md b/docs/linux/sql-server-linux-setup.md
@@ -64,7 +64,7 @@ Microsoft also supports deploying and managing SQL Server containers by using Op
 
 SQL Server has the following system requirements for Linux:
 
-|||
+||Requirement|
 |-----|-----|
 | **Memory** | 2 GB |
 | **File System** | **XFS** or **EXT4** (other file systems, such as **BTRFS**, are unsupported) |
diff --git a/docs/machine-learning/install/sql-ml-cab-downloads.md b/docs/machine-learning/install/sql-ml-cab-downloads.md
@@ -71,7 +71,7 @@ CAB files are listed in reverse chronological order. When you download the CAB f
 | | Python Server         | [SPS_9.4.7.25_1033.cab](https://go.microsoft.com/fwlink/?LinkId=2085685)   |  |
 |**Initial Release** | | | |
 | | Microsoft R Open       | [SRO_3.5.2.125_1033.cab](https://go.microsoft.com/fwlink/?linkid=2085686)  |  |
-| | R Server               | [SRS_9.4.7.25_1033.cab](https://go.microsoft.com/fwlink/?linkid=2085792)|   |  |
+| | R Server               | [SRS_9.4.7.25_1033.cab](https://go.microsoft.com/fwlink/?linkid=2085792)|   |
 | | Microsoft Python Open  | [SPO_4.5.12.120_1033.cab](https://go.microsoft.com/fwlink/?linkid=2085793) |  |
 | | Python Server          | [SPS_9.4.7.25_1033.cab](https://go.microsoft.com/fwlink/?linkid=2085685)   |  |
 
diff --git a/docs/machine-learning/python/ref-py-revoscalepy.md b/docs/machine-learning/python/ref-py-revoscalepy.md
@@ -86,7 +86,7 @@ You should also review the functions in [microsoftml](/machine-learning-server/p
 
 | Function| Description|
 | ------- | ---------- |
-| [rx_predict](/machine-learning-server/python-reference/revoscalepy/rx-predict) | Generate predictions from a trained model|) | Generates predictions from a trained model and can be used for real-time scoring. |
+| [rx_predict](/machine-learning-server/python-reference/revoscalepy/rx-predict) | Generate predictions from a trained model and can be used for real-time scoring. |
 |[rx_predict_default](/machine-learning-server/python-reference/revoscalepy/rx-predict-default) | Compute predicted values and residuals using rx_lin_mod and rx_logit objects. |
 |[rx_predict_rx_dforest](/machine-learning-server/python-reference/revoscalepy/rx-predict-rx-dforest) | Calculate predicted or fitted values for a data set from an rx_dforest or rx_btrees object. |
 |[rx_predict_rx_dtree](/machine-learning-server/python-reference/revoscalepy/rx-predict-rx-dtree) | Calculate predicted or fitted values for a data set from an rx_dtree object. |
diff --git a/docs/odbc/reference/appendixes/odbc-functions-executed-by-the-cursor-library.md b/docs/odbc/reference/appendixes/odbc-functions-executed-by-the-cursor-library.md
@@ -23,20 +23,38 @@ ms.author: v-daenge
   
  The cursor library executes the following functions. When an application calls a function in this list, the Driver Manager invokes the cursor library, not the driver. Note that the cursor library may call the driver when executing the function.  
   
-|||  
-|-|-|  
-|**SQLBindCol**|**SQLGetStmtOption**|  
-|**SQLBindParam**|**SQLNativeSql**|  
-|**SQLBindParameter**|**SQLNumParams**|  
-|**SQLCloseCursor**|**SQLParamOptions**|  
-|**SQLEndTran**|**SQLRowCount**|  
-|**SQLExtendedFetch**|**SQLSetConnectAttr**|  
-|**SQLFetchScroll**|**SQLSetConnectOption**|  
-|**SQLFreeHandle**|**SQLSetDescField**|  
-|**SQLFreeStmt**|**SQLSetDescRec**|  
-|**SQLGetData**|**SQLSetPos**|  
-|**SQLGetDescField**|**SQLSetScrollOptions**|  
-|**SQLGetDescRec**|**SQLSetStmtAttr**|  
-|**SQLGetFunctions**|**SQLSetStmtOption**|  
-|**SQLGetInfo**|**SQLTransact**|  
-|**SQLGetStmtAttr**||
+:::row:::
+   :::column span="":::
+      **SQLBindCol**
+      **SQLBindParam**
+      **SQLBindParameter**
+      **SQLCloseCursor**
+      **SQLEndTran**
+      **SQLExtendedFetch**
+      **SQLFetchScroll**
+      **SQLFreeHandle**
+      **SQLFreeStmt**
+      **SQLGetData**
+      **SQLGetDescField**
+      **SQLGetDescRec**
+      **SQLGetFunctions**
+      **SQLGetInfo**
+      **SQLGetStmtAttr**
+   :::column-end:::
+   :::column span="":::
+      **SQLGetStmtOption**
+      **SQLNativeSql**
+      **SQLNumParams**
+      **SQLParamOptions**
+      **SQLRowCount**
+      **SQLSetConnectAttr**
+      **SQLSetConnectOption**
+      **SQLSetDescField**
+      **SQLSetDescRec**
+      **SQLSetPos**
+      **SQLSetScrollOptions**
+      **SQLSetStmtAttr**
+      **SQLSetStmtOption**
+      **SQLTransact**
+   :::column-end:::
+:::row-end:::
diff --git a/docs/odbc/reference/appendixes/odbc-functions-not-executed-by-the-cursor-library.md b/docs/odbc/reference/appendixes/odbc-functions-not-executed-by-the-cursor-library.md
@@ -23,9 +23,17 @@ ms.author: v-daenge
   
  The cursor library does not execute the following functions. When an application calls one of these functions, the Driver Manager invokes the driver, not the cursor library.  
   
-|||  
-|-|-|  
-|**SQLFetch**|**SQLGetEnvAttr**|  
-|**SQLGetConnectAttr**|**SQLSetDescRec**|  
-|**SQLGetDiagField**|**SQLSetEnvAttr**|  
-|**SQLGetDiagRec**||
+:::row:::
+   :::column span="":::
+      **SQLFetch**
+      **SQLGetConnectAttr**
+      **SQLGetDiagField**
+      **SQLGetDiagRec**||
+   :::column-end:::
+   :::column span="":::
+      **SQLGetEnvAttr**
+      **SQLSetDescRec**
+      **SQLSetEnvAttr**|  
+   :::column-end:::
+:::row-end:::
+
diff --git a/docs/odbc/reference/develop-app/unicode-function-arguments.md b/docs/odbc/reference/develop-app/unicode-function-arguments.md
@@ -25,40 +25,73 @@ The ODBC 3.5 (or higher) Driver Manager supports both ANSI and Unicode versions
   
  The following is a list of the ODBC API functions that support both Unicode (W) and ANSI (A) versions:  
   
-|||  
-|-|-|  
-|**SQLBrowseConnect**|**SQLGetDiagRec**|  
-|**SQLColAttribute**|**SQLGetInfo**|  
-|**SQLColAttributes**|**SQLGetStmtAttr**|  
-|**SQLColumnPrivileges**|**SQLGetTypeInfo**|  
-|**SQLColumns**|**SQLNativeSql**|  
-|**SQLConnect**|**SQLPrepare**|  
-|**SQLDataSources**|**SQLPrimaryKeys**|  
-|**SQLDescribeCol**|**SQLProcedureColumns**|  
-|**SQLDriverConnect**|**SQLProcedures**|  
-|**SQLDrivers**|**SQLSetConnectAttr**|  
-|**SQLError**|**SQLSetConnectOption**|  
-|**SQLExecDirect**|**SQLSetCursorName**|  
-|**SQLForeignKeys**|**SQLSetDescField**|  
-|**SQLGetConnectAttr**|**SQLSetStmtAttr**|  
-|**SQLGetConnectOption**|**SQLSpecialColumns**|  
-|**SQLGetCursorName**|**SQLStatistics**|  
-|**SQLGetDescField**|**SQLTablePrivileges**|  
-|**SQLGetDescRec**|**SQLTables**|  
-|**SQLGetDiagField**||  
+:::row:::
+   :::column span="":::
+      **SQLBrowseConnect**
+      **SQLColAttribute**
+      **SQLColAttributes**
+      **SQLColumnPrivileges**
+      **SQLColumns** 
+      **SQLConnect** 
+      **SQLDataSources**
+      **SQLDescribeCol**  
+      **SQLDriverConnect** 
+      **SQLDrivers** 
+      **SQLError  
+      **SQLExecDirect**
+      **SQLForeignKeys**
+      **SQLGetConnectAttr** 
+      **SQLGetConnectOption** 
+      **SQLGetCursorName**
+      **SQLGetDescField** 
+      **SQLGetDescRec** 
+      **SQLGetDiagField**
+   :::column-end:::
+   :::column span="":::
+      **SQLGetDiagRec**        
+      **SQLGetInfo**        
+      **SQLGetStmtAttr**
+      **SQLGetTypeInfo**
+      **SQLNativeSql**
+      **SQLPrepare**
+      **SQLPrimaryKeys**
+      **SQLProcedureColumns**
+      **SQLProcedures**
+      **SQLSetConnectAttr**
+      **SQLSetConnectOption**
+      **SQLSetCursorName**
+      **SQLSetDescField**
+      **SQLSetStmtAttr**
+      **SQLSpecialColumns**
+      **SQLStatistics**
+      **SQLTablePrivileges**
+      **SQLTables**
+   :::column-end:::
+:::row-end:::
   
  The following is a list of the ODBC Installer and ODBC Translator functions that support both Unicode (W) and ANSI (A) versions:  
   
-|||  
-|-|-|  
-|**SQLConfigDataSource**|**SQLInstallDriverManager**|  
-|**SQLCreateDataSource**|**SQLInstallerError**|  
-|**SQLDataSourceToDriver**|**SQLInstallODBC**|  
-|**SQLDriverToDataSource**|**SQLReadFileDSN**|  
-|**SQLGetAvailableDrivers**|**SQLRemoveDSNFromINI**|  
-|**SQLGetInstalledDrivers**|**SQLValidDSN**|  
-|**SQLGetTranslator**|**SQLWriteDSNToINI**|  
-|**SQLInstallDriver**||  
+:::row:::
+   :::column span="":::
+      **SQLConfigDataSource**
+      **SQLCreateDataSource**
+      **SQLDataSourceToDriver**
+      **SQLDriverToDataSource**
+      **SQLGetAvailableDrivers**
+      **SQLGetInstalledDrivers**
+      **SQLGetTranslator**
+      **SQLInstallDriver**
+   :::column-end:::
+   :::column span="":::
+      **SQLInstallDriverManager**  
+      **SQLInstallerError**  
+      **SQLInstallODBC**  
+      **SQLReadFileDSN**  
+      **SQLRemoveDSNFromINI**  
+      **SQLValidDSN**  
+      **SQLWriteDSNToINI**  
+   :::column-end:::
+:::row-end:::
   
 > [!NOTE]
 >  Deprecated functions have Unicode-to-ANSI mapping support because the ODBC *3.x* Driver Manager supports recompiling ODBC *2.x* applications with the UNICODE **#define**.  
diff --git a/docs/powershell/encode-and-decode-sql-server-identifiers.md b/docs/powershell/encode-and-decode-sql-server-identifiers.md
@@ -27,9 +27,8 @@ The **Encode-SqlName** cmdlet takes as input a [!INCLUDE[ssNoVersion](../include
 
 The **Encode-Sqlname** and **Decode-Sqlname** cmdlets only encode or decode the characters that are allowed in SQL Server-delimited identifiers, but are not supported in PowerShell paths. The following are the characters encoded by **Encode-SqlName** and decoded by **Decode-SqlName**:
 
-|||||||||||||
-|-|-|-|-|-|-|-|-|-|-|-|-|
 |**Character**|\ |/|:|%|\<|>|*|?|[|]|&#124;|  
+|-|-|-|-|-|-|-|-|-|-|-|-|
 |**Hexadecimal Encoding**|%5C|%2F|%3A|%25|%3C|%3E|%2A|%3F|%5B|%5D|%7C|
 
 ## Encoding an Identifier  
diff --git a/docs/relational-databases/backup-restore/back-up-database-backup-options-page.md b/docs/relational-databases/backup-restore/back-up-database-backup-options-page.md
@@ -47,7 +47,7 @@ ms.author: chadam
  **Backup set will expire**  
  Choose one of the following expiration options. This option is disabled if **URL** is chosen as the backup destination.  
   
-|||  
+|Option|Description|  
 |-|-|  
 |**After**|Specify the number of days that must elapse before this backup set expires and can be overwritten. This value can be from 0 to 99999 days; a value of 0 days means that the backup set will never expire.<br /><br /> The default value for backup expiration is the value set in the **Default backup media retention (in days)** option. To access this, right-click the server name in Object Explorer and select **Properties**; then click the **Database Settings** page of the **Server Properties** dialog box.|  
 |**On**|Specify a specific date when the backup set expires and can be overwritten.|  
@@ -58,7 +58,7 @@ ms.author: chadam
  **Set backup compression**  
  In [!INCLUDE[ssEnterpriseEd10](../../includes/ssenterpriseed10-md.md)] (or a later version), select one of the following backup compression values:  
   
-|||  
+|Value|Description|  
 |-|-|  
 |**Use the default server setting**|Click to use the server-level default.<br /><br /> This default is set by the **backup compression default** server-configuration option. For information about how to view the current setting of this option, see [View or Configure the backup compression default Server Configuration Option](../../database-engine/configure-windows/view-or-configure-the-backup-compression-default-server-configuration-option.md).|  
 |**Compress backup**|Click to compress the backup, regardless of the server-level default.<br /><br /> **\*\* Important \*\*** By default, compression significantly increases CPU usage, and the additional CPU consumed by the compression process might adversely impact concurrent operations. Therefore, you might want to create low-priority compressed backups in a session whose CPU usage is limited by [Resource Governor](../../relational-databases/resource-governor/resource-governor.md). For more information, see [Use Resource Governor to Limit CPU Usage by Backup Compression &#40;Transact-SQL&#41;](../../relational-databases/backup-restore/use-resource-governor-to-limit-cpu-usage-by-backup-compression-transact-sql.md).|  
diff --git a/docs/relational-databases/backup-restore/back-up-database-general-page.md b/docs/relational-databases/backup-restore/back-up-database-general-page.md
@@ -67,7 +67,7 @@ ms.author: chadam
   
  Select one of the following option buttons:  
   
-|||  
+|Option|Description|  
 |-|-|  
 |**Database**|Specifies that the entire database be backed up.|  
 |**Files and filegroups**|Specifies that the specified files and/or filegroups be backed up.<br /><br /> Selecting this option, opens the **Select Files and Filegroups** dialog box. After you select the filegroups or files you want to back up and click **Ok**, your selections appear in the **Filegroups and files** box.|  
@@ -81,7 +81,7 @@ ms.author: chadam
  **Back up to**  
  Select one of the following types of media to which to back up. The destinations you select appear in the **Back up to** list.  
   
-|||  
+|Media type|Description|  
 |-|-|  
 |**Disk**|Backs up to disk. This may be a system file or a disk-based logical backup device created for the database. The currently selected disks appear in the **Back up to** list. You can select up to 64 disk devices for your backup operation.|  
 |**Tape**|Backs up to tape. This may be a local tape drive or a tape-based logical backup device created for the database. The currently selected tapes appear in the **Back up to** list. The maximum number is 64. If there are no tape devices attached to the server, this option is deactivated. The tapes you select are listed in the **Back up to** list.<br /><br /> Note: Support for tape backup devices will be removed in a future version of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. Avoid using this feature in new development work, and plan to modify applications that currently use this feature.|  
diff --git a/docs/relational-databases/backup-restore/select-backup-destination.md b/docs/relational-databases/backup-restore/select-backup-destination.md
@@ -35,15 +35,15 @@ ms.author: chadam
  **Destination on disk**  
  To specify a backup destination, choose one of the following options.  
   
-|||  
+|Option|Description|  
 |-|-|  
 |**File name**|Choose this option to enter a local or remote file as the backup destination in the text box to:<br /><br /> Specify a local file, click the browse button to the right of the text box and navigate to a file on the fixed drives of the computer running the server, or enter the full path and file name directly; for example, `C:\Program Files\Microsoft SQL Server\MSSQL\Backup\AdventureWorksBackup.bak`.<br /><br /> Specify a remote file as your backup destination, enter its fully qualified universal naming convention (UNC) name. For more information, see [Backup Devices &#40;SQL Server&#41;](../../relational-databases/backup-restore/backup-devices-sql-server.md).<br /><br /> <br /><br /> **\*\* Important \*\*** Backing up data over a network can be subject to network errors; therefore, we recommend that you verify the backup operation after it finishes. For more information, see [RESTORE VERIFYONLY &#40;Transact-SQL&#41;](../../t-sql/statements/restore-statements-verifyonly-transact-sql.md).|  
 |**Backup device**|Choose this option to select a logical backup device.<br /><br /> Note: For information about how to create a disk backup device, see [Define a Logical Backup Device for a Disk File &#40;SQL Server&#41;](../../relational-databases/backup-restore/define-a-logical-backup-device-for-a-disk-file-sql-server.md).|  
   
  **Destination on tape**  
  Specify a backup destination on a tape drive physically connected to the computer running the server (that is, the instance of the [!INCLUDE[ssDE](../../includes/ssde-md.md)]). Choose one of the following options.  
   
-|||  
+|Option|Description|  
 |-|-|  
 |**Tape drive**|Choose this option to select a tape drive as the backup destination from the list of tape drives that are physically connected to the computer that is running the server instance.<br /><br /> Note: Tape backup devices on remote computers are not valid backup destinations.|  
 |**Backup device**|Choose this option to select an existing logical backup device. These logical backup devices correspond to tape drives that are physically connected to the computer that is running the server instance.<br /><br /> Note: For information about how to create a tape backup device, see [Define a Logical Backup Device for a Tape Drive &#40;SQL Server&#41;](../../relational-databases/backup-restore/define-a-logical-backup-device-for-a-tape-drive-sql-server.md).|  
diff --git a/docs/relational-databases/clr-integration-database-objects-types-net-framework/mapping-clr-parameter-data.md b/docs/relational-databases/clr-integration-database-objects-types-net-framework/mapping-clr-parameter-data.md
@@ -31,9 +31,8 @@ ms.author: "jroth"
  [!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
   The following table lists [!INCLUDE[msCoName](../../includes/msconame-md.md)] [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] data types, their equivalents in the common language runtime (CLR) for [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] in the **System.Data.SqlTypes** namespace, and their native CLR equivalents in the [!INCLUDE[msCoName](../../includes/msconame-md.md)] .NET Framework.  
   
-||||  
-|-|-|-|  
 |**SQL Server data type**|Type (in System.Data.SqlTypes or Microsoft.SqlServer.Types)|**CLR data type (.NET Framework)**|  
+|-|-|-|  
 |**bigint**|**SqlInt64**|**Int64, Nullable\<Int64>**|  
 |**binary**|**SqlBytes, SqlBinary**|**Byte[]**|  
 |**bit**|**SqlBoolean**|**Boolean, Nullable\<Boolean>**|  
@@ -102,9 +101,8 @@ AS EXTERNAL NAME TestStoredProc.StoredProcedures.PriceSum
   
  Not all CLR data types can be automatically converted to their equivalent [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] data types through an out parameter, however. The following table lists these exceptions.  
   
-|||  
-|-|-|  
 |**CLR data type (SQL Server)**|**SQL Server data type**|  
+|-|-|  
 |**Decimal**|smallmoney|  
 |**SqlMoney**|smallmoney|  
 |**Decimal**|money|  
diff --git a/docs/relational-databases/databases/log-shipping-transaction-log-backup-settings.md b/docs/relational-databases/databases/log-shipping-transaction-log-backup-settings.md
@@ -60,7 +60,7 @@ ms.author: "sstein"
  **Set backup compression**  
  In [!INCLUDE[ssEnterpriseEd10](../../includes/ssenterpriseed10-md.md)] (or a later version), select one the following backup compression values for the log backups of this log shipping configuration:  
   
-|||  
+|Value|Description|  
 |-|-|  
 |**Use the default server setting**|Click to use the server-level default.<br /><br /> This default is set by the **backup compression default** server-configuration option. For information about how to view the current setting of this option, see [View or Configure the backup compression default Server Configuration Option](../../database-engine/configure-windows/view-or-configure-the-backup-compression-default-server-configuration-option.md).|  
 |**Compress backup**|Click to compress the backup, regardless of the server-level default.<br /><br /> **\*\* Important \*\*** By default, compression significantly increases CPU usage, and the additional CPU consumed by the compression process might adversely impact concurrent operations. Therefore, you might want to create low-priority compressed backups in a session whose CPU usage is limited by the [Resource Governor](../../relational-databases/resource-governor/resource-governor.md). For more information, see [Use Resource Governor to Limit CPU Usage by Backup Compression &#40;Transact-SQL&#41;](../../relational-databases/backup-restore/use-resource-governor-to-limit-cpu-usage-by-backup-compression-transact-sql.md).|  
diff --git a/docs/relational-databases/errors-events/database-engine-events-and-errors.md b/docs/relational-databases/errors-events/database-engine-events-and-errors.md
diff --git a/docs/relational-databases/security/security-center-for-sql-server-database-engine-and-azure-sql-database.md b/docs/relational-databases/security/security-center-for-sql-server-database-engine-and-azure-sql-database.md
diff --git a/docs/reporting-services/custom-report-items/custom-report-item-class-libraries.md b/docs/reporting-services/custom-report-items/custom-report-item-class-libraries.md
