MicrosoftDocs · MightyPen · Jul 9, 2019 · Jul 8, 2019
diff --git a/.../monitor-sql-server-machine-learning-services-using-dynamic-management-views.md b/.../monitor-sql-server-machine-learning-services-using-dynamic-management-views.md
@@ -191,7 +191,7 @@ The query returns the following columns:
 |--------|-------------|
 | physical_memory_kb | The total amount of physical memory on the machine. |
 | committed_kb | The committed memory in kilobytes (KB) in the memory manager. Does not include reserved memory in the memory manager. |
-| external_pool_peak_memory_kb | The sum of the The maximum amount of memory used, in kilobytes, for all external resource pools. |
+| external_pool_peak_memory_kb | The sum of the maximum amount of memory used, in kilobytes, for all external resource pools. |
 
 ## Memory configuration
 

diff --git a/docs/azure-data-studio/sql-server-2019-extension.md b/docs/azure-data-studio/sql-server-2019-extension.md
@@ -45,7 +45,7 @@ To install the SQL Server 2019 extension (preview), download and install the ass
 
 * The **SQL Server big data cluster** connection type has been removed in this release. All functionality previously available from the SQL Server big data cluster connection is now available in the SQL Server connection.
 * HDFS browsing can be found under the **Data Services** folder
-* For notebooks the the PySpark and other big data kernels work when connected to the SQL Server master instance in your SQL Server big data cluster.
+* For notebooks the PySpark and other big data kernels work when connected to the SQL Server master instance in your SQL Server big data cluster.
 * Create External Table wizard:
   * Support for creating External Table using existing External Data Source.
   * Performance improvements across the wizard.

diff --git a/...ailability-groups/windows/administration-of-an-availability-group-sql-server.md b/...ailability-groups/windows/administration-of-an-availability-group-sql-server.md
@@ -1,6 +1,6 @@
 ---
 title: "A reference for the administration of an availability Group"
-description: "A reference page linking you to the the basics of administering an Always On availability group, such as altering properties, adding or removing replicas, adding or removing databases, failing over, configuring the listener, etc."
+description: "A reference page linking you to the basics of administering an Always On availability group, such as altering properties, adding or removing replicas, adding or removing databases, failing over, configuring the listener, etc."
 ms.custom: "seodec18"
 ms.date: "05/17/2016"
 ms.prod: sql

diff --git a/docs/dma/dma-consolidatereports.md b/docs/dma/dma-consolidatereports.md
@@ -176,7 +176,7 @@ You can also use the LoadWarehouse script to provide the basic TSQL statements f
    ![DMAWarehouse report view](../dma/media//dma-consolidatereports/dma-DMAWarehouse-report1.png)
 
    > [!TIP]
-   > If you do not see the data you were expecting, try changing the active bookmark.  For more information, see the the detail in the following section.
+   > If you do not see the data you were expecting, try changing the active bookmark.  For more information, see the detail in the following section.
 
 ## Working with DMA reports
 

diff --git a/...atabases/native-client/odbc/performing-transactions-distributed-transactions.md b/...atabases/native-client/odbc/performing-transactions-distributed-transactions.md
@@ -47,7 +47,7 @@ MSDTC is called by the SQL Server Native Client driver for Open Database Connect
 3. The application updates some data on SQL Server Y on computer B.
     - If an update on SQL Server Y fails, all the uncommitted updates on both SQL Server instances are rolled back.
 
-4. Finally, the the application ends the transaction by calling [SQLEndTran _(1)_](../../../relational-databases/native-client-odbc-api/sqlendtran.md), with either the SQL_COMMIT or SQL_ROLLBACK option.
+4. Finally, the application ends the transaction by calling [SQLEndTran _(1)_](../../../relational-databases/native-client-odbc-api/sqlendtran.md), with either the SQL_COMMIT or SQL_ROLLBACK option.
 
 [!INCLUDE[freshInclude](../../../includes/paragraph-content/fresh-note-steps-feedback.md)]
 

diff --git a/...mple-reporting-services-rs-exe-script-to-copy-content-between-report-servers.md b/...mple-reporting-services-rs-exe-script-to-copy-content-between-report-servers.md
@@ -45,7 +45,7 @@ The script can be used to copy content between report servers of the same mode o
 |Item|Migrated|SharePoint|Description|  
 |----------|--------------|----------------|-----------------|  
 |Passwords|**No**|**No**|Passwords are **NOT** migrated. After content items are migrated, update the credential information on the destination server. For example, data sources with stored credentials.|  
-|My Reports|**No**|**No**|The Native mode "My Reports" feature is based on individual user sign-ins therefore the scripting service does not have access to content in "My Reports" folders for users other than the **-u** parameter used to run the rss script. Also, "My Reports" isn't a feature of [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] SharePoint mode and items in the folders cannot be copied to a SharePoint environment. Therefore, the script does not copy report items that are in the "My Reports" folders on a source native mode report server<br /><br /> To migrate the content in "My Reports" folders with this script, complete the following steps:<br /><br /> 1.  Create new folder(s) in the web portal. Optionally, you can create folders or subfolders for each user.<br />2.  Sign in as one of the users with "My Reports" content.<br />3.  In the web portal, select the **My Reports** folder.<br />4.  Select the **Details** view for the folder.<br />5.  Select each report that you want to copy.<br />6.  Select **Move** in the the web portal toolbar.<br />7.  Select the desired destination folder.<br />8.  Repeat steps 2-7 for each user.<br />9. Run the script.|  
+|My Reports|**No**|**No**|The Native mode "My Reports" feature is based on individual user sign-ins therefore the scripting service does not have access to content in "My Reports" folders for users other than the **-u** parameter used to run the rss script. Also, "My Reports" isn't a feature of [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] SharePoint mode and items in the folders cannot be copied to a SharePoint environment. Therefore, the script does not copy report items that are in the "My Reports" folders on a source native mode report server<br /><br /> To migrate the content in "My Reports" folders with this script, complete the following steps:<br /><br /> 1.  Create new folder(s) in the web portal. Optionally, you can create folders or subfolders for each user.<br />2.  Sign in as one of the users with "My Reports" content.<br />3.  In the web portal, select the **My Reports** folder.<br />4.  Select the **Details** view for the folder.<br />5.  Select each report that you want to copy.<br />6.  Select **Move** in the web portal toolbar.<br />7.  Select the desired destination folder.<br />8.  Repeat steps 2-7 for each user.<br />9. Run the script.|  
 |History|**No**|**No**||  
 |History settings|Yes|Yes|The history settings are migrated however the history details are NOT migrated.|  
 |Schedules|Yes|Yes|To migrate schedules, it is required that SQL Server Agent is running on the target server. If SQL Server Agent isn't running on the target, you will see an error message similar to this one:<br /><br /> `Migrating schedules: 1 items found. Migrating schedule: theMondaySchedule ... FAILURE:  The SQL Agent service isn't running. This operation requires the SQL Agent service. ---> Microsoft.ReportingServices.Diagnostics.Utilities.SchedulerNotResponding Exception: The SQL Agent service isn't running. This operation requires the SQL Agent service.`|