Address review feedback and tweak few minor connector properties

linda33wj · linda33wj · commit 5a4cf4b7b1c1 · 2018-05-22T07:13:12.000+08:00
diff --git a/articles/data-factory/connector-azure-cosmos-db.md b/articles/data-factory/connector-azure-cosmos-db.md
@@ -108,8 +108,8 @@ To copy data from/to Azure Cosmos DB, set the type property of the dataset to **
 
 For schema-free data stores such as Azure Cosmos DB, copy activity infers the schema in one of the following ways. Therefore, unless you want to [import/export JSON documents as-is](#importexport-json-documents), the best practice is to specify the structure of data in the **structure** section.
 
-1. If you specify the structure of data by using the **structure** property in the dataset definition, the Data Factory service honors this structure as the schema. In this case, if a row does not contain a value for a column, a null value will be provided for it.
-2. If you do not specify the structure of data by using the **structure** property in the dataset definition, the Data Factory service infers the schema by using the first row in the data. In this case, if the first row does not contain the full schema, some columns will be missing in the result of copy operation.
+*. If you specify the structure of data by using the **structure** property in the dataset definition, the Data Factory service honors this structure as the schema. In this case, if a row does not contain a value for a column, a null value will be provided for it.
+*. If you do not specify the structure of data by using the **structure** property in the dataset definition, the Data Factory service infers the schema by using the first row in the data. In this case, if the first row does not contain the full schema, some columns will be missing in the result of copy operation.
 
 ## Copy activity properties
 
diff --git a/articles/data-factory/connector-http.md b/articles/data-factory/connector-http.md
@@ -12,7 +12,7 @@ ms.workload: data-services
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
-ms.date: 02/07/2018
+ms.date: 05/22/2018
 ms.author: jingwang
 
 ---
@@ -55,7 +55,7 @@ The following properties are supported for HTTP linked service:
 |:--- |:--- |:--- |
 | type | The type property must be set to: **HttpServer**. | Yes |
 | url | Base URL to the Web Server | Yes |
-| enableServerCertificateValidation | Specify whether to enable server SSL certificate validation when connecting to HTTP endpoint. | No, default is true |
+| enableServerCertificateValidation | Specify whether to enable server SSL certificate validation when connecting to HTTP endpoint. When your HTTPS server is using self-signed certificate, set this to false. | No, default is true |
 | authenticationType | Specifies the authentication type. Allowed values are: **Anonymous**, **Basic**, **Digest**, **Windows**, **ClientCertificate**. <br><br> Refer to sections below this table on more properties and JSON samples for those authentication types respectively. | Yes |
 | connectVia | The [Integration Runtime](concepts-integration-runtime.md) to be used to connect to the data store. You can use Azure Integration Runtime or Self-hosted Integration Runtime (if your data store is located in private network). If not specified, it uses the default Azure Integration Runtime. |No |
 
diff --git a/articles/data-factory/connector-netezza.md b/articles/data-factory/connector-netezza.md
@@ -53,7 +53,7 @@ A typical connection string is `Server=<server>;Port=<port>;Database=<database>;
 | Property | Description | Required |
 |:--- |:--- |:--- |:--- |
 | SecurityLevel | The level of security (SSL/TLS) that the driver uses for the connection to the data store. E.g. `SecurityLevel=preferredSecured`. Supported values are:<br/>- Only Unsecured (**onlyUnSecured**): The driver does not use SSL.<br/>- **Preferred Unsecured (preferredUnSecured) (default)**: If the server provides a choice, the driver does not use SSL. <br/>- **Preferred Secured (preferredSecured)**: If the server provides a choice, the driver uses SSL. <br/>- **Only Secured (onlySecured)**: The driver does not connect unless an SSL connection is available | No |
-| CaCertFile | The full path to the SSL certificate that is used by the server. E.g. `UseSystemTrustStore=<cert path>;`| Yes, if SSL is enabled |
+| CaCertFile | The full path to the SSL certificate that is used by the server. E.g. `CaCertFile=<cert path>;`| Yes, if SSL is enabled |
 
 **Example:**
 
diff --git a/articles/data-factory/connector-odata.md b/articles/data-factory/connector-odata.md
@@ -12,7 +12,7 @@ ms.workload: data-services
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
-ms.date: 02/07/2018
+ms.date: 05/22/2018
 ms.author: jingwang
 
 ---
@@ -130,7 +130,7 @@ To copy data from OData, set the type property of the dataset to **ODataResource
 | Property | Description | Required |
 |:--- |:--- |:--- |
 | type | The type property of the dataset must be set to: **ODataResource** | Yes |
-| path | Path to the OData resource. | No |
+| path | Path to the OData resource. | Yes |
 
 **Example**
 
diff --git a/articles/data-factory/connector-oracle.md b/articles/data-factory/connector-oracle.md
@@ -38,7 +38,8 @@ Specifically, this Oracle connector supports the following versions of an Oracle
 - Oracle 9i R1, R2 (9.0.1, 9.2)
 - Oracle 8i R3 (8.1.7)
 
-Note Oracle proxy server is not supported.
+> [!Note]
+> Oracle proxy server is not supported.
 
 ## Prerequisites
 
diff --git a/articles/data-factory/v1/data-factory-http-connector.md b/articles/data-factory/v1/data-factory-http-connector.md
@@ -12,7 +12,7 @@ ms.workload: data-services
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
-ms.date: 01/10/2018
+ms.date: 05/22/2018
 ms.author: jingwang
 
 robots: noindex
@@ -50,7 +50,7 @@ The following table provides description for JSON elements specific to HTTP link
 | type | The type property must be set to: `Http`. | Yes |
 | url | Base URL to the Web Server | Yes |
 | authenticationType | Specifies the authentication type. Allowed values are: **Anonymous**, **Basic**, **Digest**, **Windows**, **ClientCertificate**. <br><br> Refer to sections below this table on more properties and JSON samples for those authentication types respectively. | Yes |
-| enableServerCertificateValidation | Specify whether to enable server SSL certificate validation if source is HTTPS Web Server | No, default is true |
+| enableServerCertificateValidation | Specify whether to enable server SSL certificate validation if source is HTTPS Web Server. When your HTTPS server is using self-signed certificate, set this to false. | No, default is true |
 | gatewayName | Name of the Data Management Gateway to connect to an on-premises HTTP source. | Yes if copying data from an on-premises HTTP source. |
 | encryptedCredential | Encrypted credential to access the HTTP endpoint. Auto-generated when you configure the authentication information in copy wizard or the ClickOnce popup dialog. | No. Apply only when copying data from an on-premises HTTP server. |
 
diff --git a/articles/data-factory/v1/data-factory-onprem-oracle-connector.md b/articles/data-factory/v1/data-factory-onprem-oracle-connector.md
@@ -56,7 +56,8 @@ This Oracle connector support two versions of drivers:
     - Oracle 9i R1, R2 (9.0.1, 9.2)
     - Oracle 8i R3 (8.1.7)
 
-Note Oracle proxy server is not supported.
+> [!NOTE]
+> Oracle proxy server is not supported.
 
 > [!IMPORTANT]
 > Currently Microsoft driver for Oracle only supports copying data from Oracle but not writing to Oracle. And note the test connection capability in Data Management Gateway Diagnostics tab does not support this driver. Alternatively, you can use the copy wizard to validate the connectivity.
