Merge branch 'master' of https://github.com/MicrosoftDocs/sql-docs-pr into release-synapse-pool-rebrand

Author: v-alje

docs/azure-data-studio/tutorial-qds-sql-server.md

@@ -131,7 +131,7 @@ To add the *slow queries widget* to your dashboard, edit the *dashboard.database
 
 5. View the query's execution plan:
 
-   ![showplan](./media/tutorial-qds-sql-server/showplan.png)
+   ![Screenshot showing the query's execution plan.](./media/tutorial-qds-sql-server/showplan.png)
 
 ## Next steps
 

docs/azure-data-studio/tutorial-sql-editor.md

@@ -61,11 +61,11 @@ Azure Data Studio provides many built-in T-SQL snippets for quickly creating sta
 
 2. Type **sql** in the editor, arrow down to **sqlCreateStoredProcedure**, and press the *Tab* key (or *Enter*) to load the create stored procedure snippet.
 
-   ![snippet-list](./media/tutorial-sql-editor/snippet-list.png)
+   ![Screenshot showing the Query Editor with sql typed in the editor and the sqlCreateStoredProcedure option called out.](./media/tutorial-sql-editor/snippet-list.png)
 
 3. The create stored procedure snippet has two fields set up for quick edit, *StoredProcedureName* and *SchemaName*. Select *StoredProcedureName*, right-click, and select **Change All Occurrences**. Now type *getCustomer* and all *StoredProcedureName* entries change to *getCustomer*.
 
-   ![snippet](./media/tutorial-sql-editor/snippet.png)
+   ![Screenshot showing the Query Editor with the Change All Occurrences option called out.](./media/tutorial-sql-editor/snippet.png)
 
 5. Change all occurrences of *SchemaName* to *dbo*. 
 6. The snippet contains placeholder parameters and body text that needs updating. The *EXECUTE* statement also contains placeholder text because it doesn't know how many parameters the procedure will have. For this tutorial update the snippet so it looks like the following code:

docs/connect/jdbc/reference/supportsresultsetconcurrency-method-sqlserverdatabasemetadata.md

@@ -57,12 +57,12 @@ public boolean supportsResultSetConcurrency(int type,
 
  An **int** that indicates the result set concurrency level, which can be one of the following values as defined in java.sql.ResultSet or SQLServerResultSet:  
 
-## java.sql.ResultSet Types  
+## Concurrency java.sql.ResultSet Types  
  CONCUR_READ_ONLY  
 
  CONCUR_UPDATABLE  
 
-## SQLServerResultSet Types  
+## Concurrency SQLServerResultSet Types  
  CONCUR_SS_OPTIMISTIC_CC  
 
  CONCUR_SS_SCROLL_LOCKS  

docs/database-engine/install-windows/change-the-database-compatibility-mode-and-use-the-query-store.md

@@ -40,7 +40,7 @@ The upgrade process to enable new query processor functionality is related to th
   
 The recommended workflow for upgrading the query processor to the latest version of the code is documented in the [Keep performance stability during the upgrade to newer SQL Server section of Query Store Usage Scenarios](../../relational-databases/performance/query-store-usage-scenarios.md#CEUpgrade), as seen below.  
 
-![query-store-usage-5](../../relational-databases/performance/media/query-store-usage-5.png "query-store-usage-5") 
+![Diagram showing the recommended workflow for upgrading the query processor to the latest version of the code.](../../relational-databases/performance/media/query-store-usage-5.png "query-store-usage-5") 
 
 Starting with [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] v18, users can be guided through the recommended workflow using the Query Tuning Assistant. For more information, see [Upgrading Databases by using the Query Tuning Assistant](../../relational-databases/performance/upgrade-dbcompat-using-qta.md).
 

docs/database-engine/install-windows/view-and-read-sql-server-setup-log-files.md

@@ -38,7 +38,7 @@ SQL Server Setup creates log files in a dated and time-stamped folder within **\
    | **For unattended installations** | %temp%\sqlsetup*.log |
 
 
- ![setup-bootstrap-example.png](media/view-and-read-sql-server-setup-log-files/setup-bootstrap-example.png)
+ ![Screenshot showing where to find the ConfigurationFiles.ini file in the Setup Bootstrap folder.](media/view-and-read-sql-server-setup-log-files/setup-bootstrap-example.png)
 
  >[!NOTE]
  > The numbers in the path *nnn* correspond to the version of SQL being installed. In the above picture, SQL 2017 was installed, so the folder is 140. For SQL 2016, the folder would be 130, and for SQL 2014 the folder would be 120.

docs/integration-services/expressions/subtract-ssis-expression.md

@@ -38,10 +38,9 @@ numeric_expression1 - numeric_expression2
  Determined by the data types of the two arguments. For more information, see [Integration Services Data Types in Expressions](../../integration-services/expressions/integration-services-data-types-in-expressions.md).  
 
 ## Remarks  
- Enclose the minus unary expression in parenthesis to ensure that the expression is evaluated in the correct order  
-  
-## Remarks  
- If either operand is null, the result is null.  
+ - Enclose the minus unary expression in parenthesis to ensure that the expression is evaluated in the correct order  
+
+ - If either operand is null, the result is null.  
 
 ## Expression Examples  
  This example subtracts numeric literals.  

docs/integration-services/functions-dm-execution-performance-counters.md

@@ -58,14 +58,18 @@ dm_execution_performance_counters [ @execution_id = ] execution_id
 |counter_name|**nvarchar(128)**|The name of the counter.|See the **Remarks** section of values.|  
 |counter_value|**BigInt**|Value returned by the counter.||  
 
-## Example  
+## Examples  
+
+### A. Return statistics for a running execution
+
  In the following example, the function returns statistics for a running execution with an ID of 34.  
 
 ```sql
 select * from [catalog].[dm_execution_performance_counters] (34)  
 ```  
 
-## Example  
+### B. Return statistics for all running executions
+
  In the following example, the function returns statistics for all the executions running on the [!INCLUDE[ssISnoversion](../includes/ssisnoversion-md.md)] server, depending on your permissions.  
 
 ```sql

docs/integration-services/system-stored-procedures/catalog-remove-data-tap.md

@@ -32,7 +32,10 @@ catalog.remove_data_tap [ @data_tap_id = ] data_tap_id
  The unique identifier for the data tap that is created by using the catalog.add_data_tap stored procedure. The *data_tap_id* is **bigint**.  
 
 ## Remarks  
- When a package contains more than one data flow tasks that have the same name, the data tap is added to the first data flow task with the given name.  
+
+- When a package contains more than one data flow tasks that have the same name, the data tap is added to the first data flow task with the given name.  
+  
+- To remove data taps, the instance of the execution must be in the created state (a value of 1 in the **status** column of the [catalog.operations (SSISDB Database)](../../integration-services/system-views/catalog-operations-ssisdb-database.md)view) .  
 
 ## Return Codes  
  0 (success)  
@@ -42,9 +45,6 @@ catalog.remove_data_tap [ @data_tap_id = ] data_tap_id
 ## Result Set  
  None  
 
-## Remarks  
- To remove data taps, the instance of the execution must be in the created state (a value of 1 in the **status** column of the [catalog.operations (SSISDB Database)](../../integration-services/system-views/catalog-operations-ssisdb-database.md)view) .  
-  
 ## Permissions  
  This stored procedure requires one of the following permissions:  
 

docs/integration-services/system-stored-procedures/catalog-revoke-permission-ssisdb-database.md

@@ -62,9 +62,6 @@ catalog.revoke_permission [ @object_type = ] object_type
 ## Result Sets  
  None  
 
-## Remarks  
- None  
-  
 ## Permissions  
  This stored procedure requires one of the following permissions:  
 

docs/integration-services/system-stored-procedures/catalog-set-execution-parameter-value-ssisdb-database.md

@@ -108,15 +108,19 @@ catalog.set_execution_parameter_value [ @execution_id = execution_id
 |*parameter_name*|DUMP_EVENT_CODE|  
 |*parameter_value*|One or more event codes|  
 
-## Example  
+## Examples  
+
+### A. Generate dump files for errors
+
  The following example specifies that the Integration Services server generates dump files when any error occurs during a package execution.  
 
 ```sql
 exec catalog.create_execution  'TR2','Recurring ETL', 'Dim_DCVendor.dtsx',NULL, 0,@execution_id out  
 exec catalog.set_execution_parameter_value  @execution_id, 50, 'DUMP_ON_ERROR',1  
 ```  
 
-## Example  
+### B. Generate dump files for events
+
  The following example specifies that the Integration Services server generates dump files when events occur during a package execution, and specifies the event that causes the server to generate the files.  
 
 ```sql