Add ports for internal communication (#112)

Author: micheleRP

modules/networking/pages/cloud-security-network.adoc

@@ -3,7 +3,7 @@
 :page-aliases: deploy:deployment-option/cloud/security/cloud-security-network.adoc
 
 Redpanda Cloud deploys two different types of networks: one for private Redpanda
-clusters and another for public Redpanda clusters. By default, networks are always
+clusters and one for public Redpanda clusters. By default, networks are always
 laid out across multiple availability zones (AZs) to enable the creation of one or
 many single and multi-AZ Redpanda clusters within them.
 
@@ -32,14 +32,16 @@ image::shared:cloud-private-network.png[Redpanda Cloud Security Architecture]
 
 == Network ports
 
-This section lists the ports on which Redpanda Cloud components communicate. Redpanda manages security group and firewall configurations on your behalf, but if you need to add to your own rule sets, these are the available network ports. 
+This section lists the external ports on which Redpanda Cloud components communicate. Redpanda manages security group and firewall configurations on your behalf, but if you need to add to your own rule sets, these are the available network ports. 
+
+NOTE: Redpanda also uses some ports for internal communication inside the cluster, including ports 80, 8081, 8082, and 9644. 
 
 === North-South
 
 The following table lists the network ports available to external clients within
 each data plane. For private-only Redpanda clusters, access to these ports is
 only possible through Redpanda Cloud network connections such as xref:networking:dedicated/vpc-peering.adoc[VPC peering],
-transit gateway attachments, or private links.
+transit gateway attachments, or Private Links/Private Service Connect.
 
 |===
 | Service | Port