edit pass: create-self-hosted-integration-runtime

Author: BobbySchmidt2

articles/data-factory/create-self-hosted-integration-runtime.md

@@ -99,7 +99,7 @@ Here are details of the application's parameters and properties:
 | Property                                                    | Description                                                  | Required |
 | ----------------------------------------------------------- | ------------------------------------------------------------ | -------- |
 | **RegisterNewNode** "`<AuthenticationKey>`"                     | Register a self-hosted integration runtime node with the specified authentication key. | No       |
-| **EnableRemoteAccess** "`<port>`" ["`<thumbprint>`"]            | Enable remote access on the current node to set up a high-availability cluster. Or enable setting credentials directly against the self-hosted IR without going through the ADF service. You do the latter by using the **New-AzDataFactoryV2LinkedServiceEncryptedCredential** cmdlet from a remote machine in the same network. | No       |
+| **EnableRemoteAccess** "`<port>`" ["`<thumbprint>`"]            | Enable remote access on the current node to set up a high-availability cluster. Or enable setting credentials directly against the self-hosted IR without going through the Azure Data Factory service. You do the latter by using the **New-AzDataFactoryV2LinkedServiceEncryptedCredential** cmdlet from a remote machine in the same network. | No       |
 | **EnableRemoteAccessInContainer** "`<port>`" ["`<thumbprint>`"] | Enable remote access to the current node when the node runs in a container. | No       |
 | **DisableRemoteAccess**                                         | Disable remote access to the current node. Remote access is needed for multinode setup. The **New-AzDataFactoryV2LinkedServiceEncryptedCredential** PowerShell cmdlet still works even when remote access is disabled. This behavior is true as long as the cmdlet is executed on the same machine as the self-hosted IR node. | No       |
 | **Key** "`<AuthenticationKey>`"                                 | Overwrite or update the previous authentication key. Be careful with this action. Your previous self-hosted IR node can go offline if the key is of a new integration runtime. | No       |
@@ -218,7 +218,7 @@ When processor usage is high and available memory is low on the self-hosted IR,
 
 #### Scale up
 
-When the processor and available RAM aren't well utilized, but the execution of concurrent jobs reaches the limit, scale up by increasing the number of concurrent jobs that a node can run. You might also want to scale up when activities time out because the self-hosted IR is overloaded. As shown in the following image, you can increase the maximum capacity for a node:  
+When the processor and available RAM aren't well utilized, but the execution of concurrent jobs reaches the processor and RAM limits, scale up by increasing the number of concurrent jobs that a node can run. You might also want to scale up when activities time out because the self-hosted IR is overloaded. As shown in the following image, you can increase the maximum capacity for a node:  
 
 ![Increase the number of concurrent jobs that can run on a node](media/create-self-hosted-integration-runtime/scale-up-self-hosted-IR.png)
 
@@ -228,7 +228,7 @@ Here are the requirements for the TLS/SSL certificate that you use to secure com
 
 - The certificate must be a publicly trusted X509 v3 certificate. We recommend that you use certificates that are issued by a public partner certification authority (CA).
 - Each integration runtime node must trust this certificate.
-- We don't recommend Subject Alternative Name (SAN) certificates because only the last SAN item is used. All others are ignored because of current limitations. For example, if you have a SAN certificate whose SANs are **node1.domain.contoso.com** and **node2.domain.contoso.com**, you can use this certificate only on a machine whose fully qualified domain name (FQDN) is **node2.domain.contoso.com**.
+- We don't recommend Subject Alternative Name (SAN) certificates because only the last SAN item is used. All others are SAN items ignored because of current limitations. For example, if you have a SAN certificate whose SANs are **node1.domain.contoso.com** and **node2.domain.contoso.com**, you can use this certificate only on a machine whose fully qualified domain name (FQDN) is **node2.domain.contoso.com**.
 - The certificate can use any key size supported by Windows Server 2012 R2 for SSL certificates.
 - Certificates that use CNG keys aren't supported.  
 
@@ -237,7 +237,7 @@ Here are the requirements for the TLS/SSL certificate that you use to secure com
 >
 > - To encrypt ports on a self-hosted IR node.
 > - For node-to-node communication for state synchronization, which includes credentials synchronization of linked services across nodes.
-> - While using a PowerShell cmdlet for linked-service credential settings from within a local network.
+> - When a PowerShell cmdlet is used for linked-service credential settings from within a local network.
 >
 > We suggest you use this certificate if your private network environment is not secure or if you want to secure the communication between nodes within your private network.
 >
@@ -333,7 +333,7 @@ If your corporate network environment uses a proxy server to access the internet
 
 ![Specify the proxy](media/create-self-hosted-integration-runtime/specify-proxy.png)
 
-When configured, the self-hosted integration runtime uses the proxy server to connect to the cloud service, source/ destination (those using HTTP/ HTTPS protocol). This is Select **Change link** during initial setup. You see the proxy-setting dialog box.
+When configured, the self-hosted integration runtime uses the proxy server to connect to the cloud service's source and destination (which use the HTTP or HTTPS protocol). This is why you select **Change link** during initial setup.
 
 ![Set the proxy](media/create-self-hosted-integration-runtime/set-http-proxy.png)
 
@@ -390,7 +390,7 @@ If you select the **Use system proxy** option for the HTTP proxy, the self-hoste
 	```
 1. Save the configuration file in its original location. Then restart the self-hosted integration runtime host service, which picks up the changes.
 
-   To restart the service, use the services applet from the control panel. Or from Integration Runtime Configuration Manager, select the **Stop Service** button, and then select **Start Service**. 
+   To restart the service, use the services applet from Control Panel. Or from Integration Runtime Configuration Manager, select the **Stop Service** button, and then select **Start Service**.
 
    If the service doesn't start, you likely added incorrect XML tag syntax in the application configuration file that you edited.
 

includes/domain-and-outbound-port-requirements.md

@@ -14,5 +14,5 @@ ms.author: abnarain
 | `*.frontend.clouddatahub.net` | 443            | Required by the self-hosted integration runtime to connect to the Data Factory service. |
 | `download.microsoft.com`    | 443            | Required by the self-hosted integration runtime for downloading the updates. If you have disabled auto-update, you can skip configuring this domain. |
 | `*.core.windows.net`          | 443            | Used by the self-hosted integration runtime to connect to the Azure storage account when you use the [staged copy](https://docs.microsoft.com/azure/data-factory/copy-activity-performance#staged-copy) feature. |
-| `*.database.windows.net`      | 1433           | (Optional) Required when you copy from or to Azure SQL Database or Azure SQL Data Warehouse. Use the staged-copy feature to copy data to SQL Database or SQL Data Warehouse without opening port 1433. |
-| `*.azuredatalakestore.net`<br>`login.microsoftonline.com/<tenant>/oauth2/token`    | 443            | (Optional) Required when you copy from or to Azure Data Lake Store. |
+| `*.database.windows.net`      | 1433           | Required only when you copy from or to Azure SQL Database or Azure SQL Data Warehouse. Otherwise, use of this domain is optional. Use the staged-copy feature to copy data to SQL Database or SQL Data Warehouse without opening port 1433. |
+| `*.azuredatalakestore.net`<br>`login.microsoftonline.com/<tenant>/oauth2/token`    | 443            | Required only when you copy from or to Azure Data Lake Store. Otherwise, use of these domains is optional. |