[ADF] [SEO Work] Short metadata titles (<=99 >=90)

Author: markingmyname

articles/data-factory/connector-amazon-marketplace-web-service.md

@@ -1,21 +1,17 @@
 ---
-title: Copy data from Amazon Marketplace Web Service using Azure Data Factory 
+title: Copy data from Amazon Marketplace Web Service
 description: Learn how to copy data from Amazon Marketplace Web Service to supported sink data stores by using a copy activity in an Azure Data Factory pipeline.
 services: data-factory
-documentationcenter: ''
-author: linda33wj
-manager: craigg
-ms.reviewer: douglasl
-
 ms.service: data-factory
 ms.workload: data-services
-ms.tgt_pltfrm: na
-
 ms.topic: conceptual
-ms.date: 08/01/2018
 ms.author: jingwang
-
+author: linda33wj
+manager: shwang
+ms.reviewer: douglasl
+ms.date: 08/01/2018
 ---
+
 # Copy data from Amazon Marketplace Web Service using Azure Data Factory
 
 This article outlines how to use the Copy Activity in Azure Data Factory to copy data from Amazon Marketplace Web Service. It builds on the [copy activity overview](copy-activity-overview.md) article that presents a general overview of copy activity.

articles/data-factory/enable-aad-authentication-azure-ssis-ir.md

@@ -1,18 +1,18 @@
 ---
-title: Enable Azure Active Directory authentication for Azure-SSIS Integration Runtime 
+title: Enable Azure Active Directory for Azure-SSIS Integration Runtime
 description: This article describes how to enable Azure Active Directory authentication with the managed identity for Azure Data Factory to create Azure-SSIS Integration Runtime.
 services: data-factory
-documentationcenter: ''
 ms.service: data-factory
 ms.workload: data-services
 ms.tgt_pltfrm: 
 ms.devlang: powershell
 ms.topic: conceptual
-ms.date: 5/14/2019
 author: swinarko
 ms.author: sawinark
-manager: craigg
+manager: mflasko
+ms.date: 5/14/2019
 ---
+
 # Enable Azure Active Directory authentication for Azure-SSIS Integration Runtime
 
 This article shows you how to enable Azure Active Directory (Azure AD) authentication with the managed identity for your Azure Data Factory (ADF) and use it instead of conventional authentication methods (like SQL authentication) to:

articles/data-factory/self-hosted-integration-runtime-proxy-ssis.md

@@ -44,7 +44,7 @@ Please create an Azure Blob Storage linked service under the same ADF where your
 ## Configure Azure-SSIS IR with Self-Hosted IR as a proxy
 Having prepared your Self-Hosted IR and Azure Blob Storage linked service for staging, you can now configure your new/existing Azure-SSIS IR with Self-Hosted IR as a proxy on ADF portal/app.  If your existing Azure-SSIS IR is running, please stop it before you do this and then restart it afterwards.
 
-On the **Advanced Settings** page, please check the **Set up Self-Hosted Integration Runtime as a proxy for your Azure-SSIS Integration Runtime** checkbox, select your Self-Hosted IR and Azure Blob Storage linked service for staging, and specify a blob container name for **Staging Path** if you want.
+On the **Advanced Settings** page, please check the **Set-up Self-Hosted Integration Runtime as a proxy for your Azure-SSIS Integration Runtime** checkbox, select your Self-Hosted IR and Azure Blob Storage linked service for staging, and specify a blob container name for **Staging Path** if you want.
 
 ![Configure Azure-SSIS IR with Self-Hosted IR as a proxy](media/self-hosted-integration-runtime-proxy-ssis/shir-advanced-settings-ssisir.png)
 
@@ -55,7 +55,7 @@ When designing new packages containing Data Flow Tasks with OLEDB/Flat File Sour
 
 ![Enable ConnectByProxy property](media/self-hosted-integration-runtime-proxy-ssis/shir-connection-manager-properties.png)
 
-You can also enable this property when running existing packages without having to manually change them one by one.  There are 2 options:
+You can also enable this property when running existing packages without having to manually change them one by one.  There are two options:
 - Opening, rebuilding, and redeploying the project containing those packages with the latest SSDT to run on your Azure-SSIS IR: The property can then be enabled by setting it to **True** for the relevant connection managers that appear on the **Connection Managers** tab of Execute Package pop-up window when running packages from SSMS.
 
   ![Enable ConnectByProxy property2](media/self-hosted-integration-runtime-proxy-ssis/shir-connection-managers-tab-ssms.png)