Merge pull request #110398 from dagiro/freshness38

freshness38

Author: PRMerger17

articles/hdinsight/hdinsight-hadoop-port-settings-for-services.md

@@ -5,9 +5,9 @@ author: hrasheed-msft
 ms.author: hrasheed
 ms.reviewer: jasonh
 ms.service: hdinsight
-ms.custom: hdinsightactive
 ms.topic: conceptual
-ms.date: 10/15/2019
+ms.custom: hdinsightactive
+ms.date: 04/06/2020
 ---
 
 # Ports used by Apache Hadoop services on HDInsight
@@ -16,9 +16,9 @@ This document provides a list of the ports used by Apache Hadoop services runnin
 
 ## Public ports vs. non-public ports
 
-Linux-based HDInsight clusters only expose three ports publicly on the internet; 22, 23, and 443. These ports are used to securely access the cluster using SSH and services exposed over the secure HTTPS protocol.
+Linux-based HDInsight clusters only expose three ports publicly on the internet: 22, 23, and 443. These ports secure cluster access using SSH and services exposed over the secure HTTPS protocol.
 
-Internally, HDInsight is implemented by several Azure Virtual Machines (the nodes within the cluster) running on an Azure Virtual Network. From within the virtual network, you can access ports not exposed over the internet. For example, if you connect to one of the head nodes using SSH, from the head node you can then directly access services running on the cluster nodes.
+HDInsight is implemented by several Azure Virtual Machines (cluster nodes) running on an Azure Virtual Network. From within the virtual network, you can access ports not exposed over the internet. If you connect via SSH to the head node, you can directly access services running on the cluster nodes.
 
 > [!IMPORTANT]  
 > If you do not specify an Azure Virtual Network as a configuration option for HDInsight, one is created automatically. However, you can't join other machines (such as other Azure Virtual Machines or your client development machine) to this virtual network.
@@ -27,7 +27,7 @@ To join additional machines to the virtual network, you must create the virtual
 
 ## Public ports
 
-All the nodes in an HDInsight cluster are located in an Azure Virtual Network, and can't be directly accessed from the internet. A public gateway provides internet access to the following ports, which are common across all HDInsight cluster types.
+All the nodes in an HDInsight cluster are located in an Azure Virtual Network. The nodes can't be directly accessed from the internet. A public gateway provides internet access to the following ports, which are common across all HDInsight cluster types.
 
 | Service | Port | Protocol | Description |
 | --- | --- | --- | --- |
@@ -44,7 +44,7 @@ The following are available for specific cluster types:
 
 | Service | Port | Protocol | Cluster type | Description |
 | --- | --- | --- | --- | --- |
-| Stargate |443 |HTTPS |HBase |HBase REST API. See [Get started using Apache HBase](hbase/apache-hbase-tutorial-get-started-linux.md) |
+| `Stargate` |443 |HTTPS |HBase |HBase REST API. See [Get started using Apache HBase](hbase/apache-hbase-tutorial-get-started-linux.md) |
 | Livy |443 |HTTPS |Spark |Spark REST API. See [Submit Apache Spark jobs remotely using Apache Livy](spark/apache-spark-livy-rest-interface.md) |
 | Spark Thrift server |443 |HTTPS |Spark |Spark Thrift server used to submit Hive queries. See [Use Beeline with Apache Hive on HDInsight](hadoop/apache-hadoop-use-hive-beeline.md) |
 | Storm |443 |HTTPS |Storm |Storm web UI. See [Deploy and manage Apache Storm topologies on HDInsight](storm/apache-storm-deploy-monitor-topology-linux.md) |
@@ -84,7 +84,7 @@ Examples:
 | --- | --- | --- | --- | --- |
 | NameNode web UI |Head nodes |30070 |HTTPS |Web UI to view status |
 | NameNode metadata service |head nodes |8020 |IPC |File system metadata |
-| DataNode |All worker nodes |30075 |HTTPS |Web UI to view status, logs, etc. |
+| DataNode |All worker nodes |30075 |HTTPS |Web UI to view status, logs, and so on. |
 | DataNode |All worker nodes |30010 |  |Data transfer |
 | DataNode |All worker nodes |30020 |IPC |Metadata operations |
 | Secondary NameNode |Head nodes |50090 |HTTP |Checkpoint for NameNode metadata |
@@ -95,7 +95,7 @@ Examples:
 | --- | --- | --- | --- | --- |
 | Resource Manager web UI |Head nodes |8088 |HTTP |Web UI for Resource Manager |
 | Resource Manager web UI |Head nodes |8090 |HTTPS |Web UI for Resource Manager |
-| Resource Manager admin interface |head nodes |8141 |IPC |For application submissions (Hive, Hive server, Pig, etc.) |
+| Resource Manager admin interface |head nodes |8141 |IPC |For application submissions (Hive, Hive server, Pig, and so on.) |
 | Resource Manager scheduler |head nodes |8030 |HTTP |Administrative interface |
 | Resource Manager application interface |head nodes |8050 |HTTP |Address of the applications manager interface |
 | NodeManager |All worker nodes |30050 |  |The address of the container manager |