Merge pull request #19298 from julieMSFT/20210510_buildwarnings

updates for warning in repo

Author: MikeRayMSFT

docs/connect/jdbc/release-notes-for-the-jdbc-driver.md

@@ -52,7 +52,8 @@ Released: January 29, 2021
 **[![Download](../../ssms/media/download-icon.png) Download Microsoft JDBC Driver 9.2.0 for SQL Server (zip)](https://go.microsoft.com/fwlink/?linkid=2153622)**  
 **[![Download](../../ssms/media/download-icon.png) Download Microsoft JDBC Driver 9.2.0 for SQL Server (tar.gz)](https://go.microsoft.com/fwlink/?linkid=2153521)**  
 
-Zip file: [Chinese (Simplified)](https://go.microsoft.com/fwlink/?linkid=2153622&clcid=0x804) | [Chinese (Traditional)](https://go.microsoft.com/fwlink/?linkid=2153622&clcid=0x404) | [English (United States)](https://go.microsoft.com/fwlink/?linkid=2153622&clcid=0x409) | [French](https://go.microsoft.com/fwlink/?linkid=2153622&clcid=0x40c) | [German](https://go.microsoft.com/fwlink/?linkid=2153622&clcid=0x407) | [Italian](https://go.microsoft.com/fwlink/?linkid=2153622&clcid=0x410) | [Japanese](https://go.microsoft.com/fwlink/?linkid=2153622&clcid=0x411) | [Korean](https://go.microsoft.com/fwlink/?linkid=2153622&clcid=0x412) | [Portuguese (Brazil)](https://go.microsoft.com/fwlink/?linkid=2153622&clcid=0x416) | [Russian](https://go.microsoft.com/fwlink/?linkid=2153622&clcid=0x419) | [Spanish](https://go.microsoft.com/fwlink/?linkid=2153622&clcid=0x40a)  
+If you need to download the driver in a language other than the one detected for you, you can use these direct links.  
+For the driver in a zip file: [Chinese (Simplified)](https://go.microsoft.com/fwlink/?linkid=2153622&clcid=0x804) | [Chinese (Traditional)](https://go.microsoft.com/fwlink/?linkid=2153622&clcid=0x404) | [English (United States)](https://go.microsoft.com/fwlink/?linkid=2153622&clcid=0x409) | [French](https://go.microsoft.com/fwlink/?linkid=2153622&clcid=0x40c) | [German](https://go.microsoft.com/fwlink/?linkid=2153622&clcid=0x407) | [Italian](https://go.microsoft.com/fwlink/?linkid=2153622&clcid=0x410) | [Japanese](https://go.microsoft.com/fwlink/?linkid=2153622&clcid=0x411) | [Korean](https://go.microsoft.com/fwlink/?linkid=2153622&clcid=0x412) | [Portuguese (Brazil)](https://go.microsoft.com/fwlink/?linkid=2153622&clcid=0x416) | [Russian](https://go.microsoft.com/fwlink/?linkid=2153622&clcid=0x419) | [Spanish](https://go.microsoft.com/fwlink/?linkid=2153622&clcid=0x40a)  
 Tar.gz file: [Chinese (Simplified)](https://go.microsoft.com/fwlink/?linkid=2153521&clcid=0x804) | [Chinese (Traditional)](https://go.microsoft.com/fwlink/?linkid=2153521&clcid=0x404) | [English (United States)](https://go.microsoft.com/fwlink/?linkid=2153521&clcid=0x409) | [French](https://go.microsoft.com/fwlink/?linkid=2153521&clcid=0x40c) | [German](https://go.microsoft.com/fwlink/?linkid=2153521&clcid=0x407) | [Italian](https://go.microsoft.com/fwlink/?linkid=2153521&clcid=0x410) | [Japanese](https://go.microsoft.com/fwlink/?linkid=2153521&clcid=0x411) | [Korean](https://go.microsoft.com/fwlink/?linkid=2153521&clcid=0x412) | [Portuguese (Brazil)](https://go.microsoft.com/fwlink/?linkid=2153521&clcid=0x416) | [Russian](https://go.microsoft.com/fwlink/?linkid=2153521&clcid=0x419) | [Spanish](https://go.microsoft.com/fwlink/?linkid=2153521&clcid=0x40a)  
 
 ### Support for JDK 15

docs/integration-services/control-flow/bulk-insert-task.md

@@ -194,8 +194,9 @@ ms.author: chugu
  **FirstRow**  
  Specify the first row from which to start copying.  
 
- **Options**  
- |Term|Definition|  
+ **Options**
+ 
+|Term|Definition|  
 |----------|----------------|  
 |**Check constraints**|Select to check the table and column constraints.|  
 |**Keep nulls**|Select to retain null values during the bulk insert operation, instead of inserting any default values for empty columns.|  

docs/relational-databases/query-processing-architecture-guide.md

@@ -1333,13 +1333,15 @@ The following illustration shows the properties of the `Clustered Index Seek` op
 
 When an operator such as an Index Seek is executed on a partitioned table or index, the `Partitioned` attribute appears in the compile-time and run-time plan and is set to `True` (1). The attribute does not display when it is set to `False` (0).
 
-The `Partitioned` attribute can appear in the following physical and logical operators:  
-|||
-|--------|--------|
-|Table Scan|Index Scan|
-|Index Seek|Insert|
-|Update|Delete|
-|Merge||
+The `Partitioned` attribute can appear in the following physical and logical operators:
+
+- Table Scan
+- Index Scan
+- Index Seek
+- Insert
+- Update
+- Delete
+- Merge
 
 As shown in the previous illustration, this attribute is displayed in the properties of the operator in which it is defined. In the XML Showplan output, this attribute appears as `Partitioned="1"` in the `RelOp` node of the operator in which it is defined.
 

docs/relational-databases/search/use-the-full-text-indexing-wizard.md

@@ -92,12 +92,13 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||
      d. **Select index filegroup**  
      Specify the filegroup on which to create the full-text index.  
 
-     e. Select a value:  
+     e. Select a value:
+       
       |Value|Description|  
       |-----------|-----------------|
       |**<default>**| If the table or view is not partitioned, select to use the same filegroup as the underlying table or view. If the       table or view is partitioned, the primary filegroup is used|
       |**PRIMARY**|Select to use the primary filegroup for the new full-text index.|
-      *user-specified default filegroup*|If a user-defined default stoplist exists, select its name from the list to use that filegroup       for the new full-text index.|   
+      *user-specified default filegroup*|If a user-defined default stoplist exists, select its name from the list to use that filegroup       for the new full-text index.|
 
      
  11. **Select full-text stoplist**  

docs/relational-databases/system-dynamic-management-views/sys-dm-io-pending-io-requests-transact-sql.md

@@ -28,22 +28,23 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
   Returns a row for each pending I/O request in [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].  
 
 > [!NOTE]  
->  To call this from [!INCLUDE[ssSDWfull](../../includes/sssdwfull-md.md)] or [!INCLUDE[ssPDW](../../includes/sspdw-md.md)], use the name **sys.dm_pdw_nodes_io_pending_io_requests**.  
-  
+>  To call this from [!INCLUDE[ssSDWfull](../../includes/sssdwfull-md.md)] or [!INCLUDE[ssPDW](../../includes/sspdw-md.md)], use the name **sys.dm_pdw_nodes_io_pending_io_requests**.
+>
+
 |Column name|Data type|Description|  
 |-----------------|---------------|-----------------|  
 |**io_completion_request_address**|**varbinary(8)**|Memory address of the IO request. Is not nullable.|  
 |**io_type**|**nvarchar(60)**|Type of pending I/O request. Is not nullable.|  
 |**io_pending_ms_ticks**|**bigint**|Internal use only. Is not nullable.| 
 |**io_pending**|**int**|Indicates whether the I/O request is pending (1) or has been completed by the operating system (0). An I/O request can still be pending even when OS has completed the request, but [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] has not yet performed a context switch in which it would process the I/O request and remove it from this list. Is not nullable. <br /> **Value** <br /> 0 = Pending SQL Server <br /> 1 = Pending OS <br />|  
-
 |**io_completion_routine_address**|**varbinary(8)**|Internal function to call when the I/O request is completed. Is nullable.|  
 |**io_user_data_address**|**varbinary(8)**|Internal use only. Is nullable.|  
 |**scheduler_address**|**varbinary(8)**|Scheduler on which this I/O request was issued. The I/O request will appear on the pending I/O list of the scheduler. For more information, see [sys.dm_os_schedulers &#40;Transact-SQL&#41;](../../relational-databases/system-dynamic-management-views/sys-dm-os-schedulers-transact-sql.md). Is not nullable.|  
 |**io_handle**|**varbinary(8)**|File handle of the file that is used in the I/O request. Is nullable.|  
 |**io_offset**|**bigint**|Offset of the I/O request. Is not nullable.|  
 |**io_handle_path**|**nvarchar(256)**| Path of file that is used in the I/O request. Is nullable.|
-|**pdw_node_id**|**int**|**Applies to**: [!INCLUDE[ssSDWfull](../../includes/sssdwfull-md.md)], [!INCLUDE[ssPDW](../../includes/sspdw-md.md)]<br /><br /> The identifier for the node that this distribution is on.|  
+|**pdw_node_id**|**int**|**Applies to**: [!INCLUDE[ssSDWfull](../../includes/sssdwfull-md.md)], [!INCLUDE[ssPDW](../../includes/sspdw-md.md)]<br /><br /> The identifier for the node that this distribution is on.|
+
 
 ## Permissions  
 

docs/reporting-services/report-server/add-a-snapshot-to-report-history-report-manager.md

@@ -72,8 +72,6 @@ Report snapshots are not saved in a particular rendering format. Instead, report
 
 ::: moniker range=">=sql-server-2017"
 
-## To manually add snapshots to report history
-  
 1. In the web portal, navigate to the item that you want to view history for and right-click it.  
 
 2. In the drop-down menu, select **Manage**.  

docs/t-sql/queries/hints-transact-sql-join.md

@@ -52,25 +52,30 @@ ms.author: vanto
 [!INCLUDE[sql-server-tsql-previous-offline-documentation](../../includes/sql-server-tsql-previous-offline-documentation.md)]
 
 ## Arguments
- LOOP \| HASH \| MERGE  
- Specifies that the join in the query should use looping, hashing, or merging. Using LOOP |HASH | MERGE JOIN enforces a particular join between two tables. LOOP cannot be specified together with RIGHT or FULL as a join type. For more information, see [Joins](../../relational-databases/performance/joins.md).
-  
- REMOTE  
- Specifies that the join operation is performed on the site of the right table. This is useful when the left table is a local table and the right table is a remote table. REMOTE should be used only when the left table has fewer rows than the right table.  
-  
- If the right table is local, the join is performed locally. If both tables are remote but from different data sources, REMOTE causes the join to be performed on the site of the right table. If both tables are remote tables from the same data source, REMOTE is not required.  
-  
- REMOTE cannot be used when one of the values being compared in the join predicate is cast to a different collation using the COLLATE clause.  
-  
- REMOTE can be used only for INNER JOIN operations.  
+
+LOOP \| HASH \| MERGE
+
+Specifies that the join in the query should use looping, hashing, or merging. Using LOOP |HASH | MERGE JOIN enforces a particular join between two tables. LOOP cannot be specified together with RIGHT or FULL as a join type. For more information, see [Joins](../../relational-databases/performance/joins.md).
+
+REMOTE
+
+Specifies that the join operation is performed on the site of the right table. This is useful when the left table is a local table and the right table is a remote table. REMOTE should be used only when the left table has fewer rows than the right table.  
+
+If the right table is local, the join is performed locally. If both tables are remote but from different data sources, REMOTE causes the join to be performed on the site of the right table. If both tables are remote tables from the same data source, REMOTE is not required.  
+
+REMOTE cannot be used when one of the values being compared in the join predicate is cast to a different collation using the COLLATE clause.  
+
+REMOTE can be used only for INNER JOIN operations.  
 
-## Remarks  
- Join hints are specified in the FROM clause of a query. Join hints enforce a join strategy between two tables. If a join hint is specified for any two tables, the query optimizer automatically enforces the join order for all joined tables in the query, based on the position of the ON keywords. When a CROSS JOIN is used without the ON clause, parentheses can be used to indicate the join order.  
+## Remarks
+
+Join hints are specified in the FROM clause of a query. Join hints enforce a join strategy between two tables. If a join hint is specified for any two tables, the query optimizer automatically enforces the join order for all joined tables in the query, based on the position of the ON keywords. When a CROSS JOIN is used without the ON clause, parentheses can be used to indicate the join order.  
 
 ## Examples  
 
-### A. Using HASH  
- The following example specifies that the `JOIN` operation in the query is performed by a `HASH` join. The example uses the [!INCLUDE[ssSampleDBnormal](../../includes/sssampledbnormal-md.md)] database.  
+### A. Using HASH
+
+The following example specifies that the `JOIN` operation in the query is performed by a `HASH` join. The example uses the [!INCLUDE[ssSampleDBnormal](../../includes/sssampledbnormal-md.md)] database.  
 
 ```sql
 SELECT p.Name, pr.ProductReviewID  
@@ -104,6 +109,6 @@ GO
 ```  
 
 ## See Also  
- [Hints (Transact-SQL)](../../t-sql/queries/hints-transact-sql.md)  
+[Hints (Transact-SQL)](../../t-sql/queries/hints-transact-sql.md)