Rename networking sections for clarity and consistency

Author: aneta-petrova

guides/common/assembly_networking-in-project.adoc renamed to guides/common/assembly_networking-considerations-in-project.adoc

@@ -1,6 +1,6 @@
-include::modules/con_networking-in-project.adoc[]
+include::modules/con_networking-considerations-in-project.adoc[]
 
-include::modules/con_port-and-firewall-considerations-in-project.adoc[leveloffset=+1]
+include::modules/con_smart-proxy-networking.adoc[leveloffset=+1]
 
 include::modules/ref_project-server-port-and-firewall-requirements.adoc[leveloffset=+1]
 

guides/common/modules/con_http-booting-requirements-with-managed-dhcp.adoc

@@ -9,7 +9,7 @@ To provision machines through HTTP booting ensure that you meet the following re
 For HTTP booting to work, ensure that your environment has the following client-side configurations:
 
 * All the network-based firewalls are configured to allow clients on the subnet to access the {SmartProxy}.
-For more information, see xref:common/modules/con_networking-in-project.adoc#networking-in-{project-context}[].
+For more information, see xref:common/modules/con_networking-considerations-in-project.adoc#networking-considerations-in-{project-context}[].
 * Your client has access to the DHCP and DNS servers.
 * Your client has access to the HTTP UEFI Boot {SmartProxy}.
 

guides/common/modules/con_http-booting-requirements-with-unmanaged-dhcp.adoc

@@ -12,7 +12,7 @@ To provision machines through HTTP booting without managed DHCP ensure that you
 * Ensure that your client has access to the DHCP and DNS servers.
 * Ensure that your client has access to the HTTP UEFI Boot {SmartProxy}.
 * Ensure that all the network-based firewalls are configured to allow clients on the subnet to access the {SmartProxy}.
-For more information, see xref:common/modules/con_networking-in-project.adoc#networking-in-{project-context}[].
+For more information, see xref:common/modules/con_networking-considerations-in-project.adoc#networking-considerations-in-{project-context}[].
 
 .Network requirements
 * An unmanaged DHCP server available for clients.

guides/common/modules/con_networking-in-project.adoc renamed to guides/common/modules/con_networking-considerations-in-project.adoc

@@ -1,4 +1,4 @@
-[id="networking-in-{project-context}"]
-= Networking in {Project}
+[id="networking-considerations-in-{project-context}"]
+= Networking considerations in {Project}
 
 For the components of {Project} architecture to communicate, the required network ports must be open and free to enable incoming and outgoing traffic between the components.

guides/common/modules/con_pxe-booting-requirements.adoc

@@ -10,7 +10,7 @@ To provision machines using PXE booting, ensure that you meet the following requ
 
 .Client requirements
 * Ensure that all the network-based firewalls are configured to allow clients on the subnet to access the {SmartProxy}.
-For more information, see xref:common/modules/con_networking-in-project.adoc#networking-in-{project-context}[].
+For more information, see xref:common/modules/con_networking-considerations-in-project.adoc#networking-considerations-in-{project-context}[].
 
 * Ensure that your client has access to the DHCP and TFTP servers.
 

guides/common/modules/con_port-and-firewall-considerations-in-project.adoc renamed to guides/common/modules/con_smart-proxy-networking.adoc

@@ -1,5 +1,5 @@
-[id="port-and-firewall-considerations-in-{project-context}"]
-= Port and firewall considerations in {Project}
+[id="{smart-proxy-context}-networking"]
+= {SmartProxy} networking
 
 The communication between {ProjectServer} and hosts registered to a {SmartProxyServer} is routed through that {SmartProxyServer}.
 {SmartProxyServer} also provides {Project} services to hosts.

guides/common/modules/proc_opening-required-ports.adoc

@@ -77,7 +77,7 @@ endif::[]
 ----
 
 .Additional resources
-* {PlanningDocURL}networking-in-a-{project-context}-deployment[Networking in a {Project} deployment]
+* {PlanningDocURL}networking-considerations-in-a-{project-context}-deployment[Networking considerations in a {Project} deployment]
 ifndef::foreman-deb[]
 * https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/configuring_firewalls_and_packet_filters/using-and-configuring-firewalld_firewall-packet-filters/9/html/configuring_firewalls_and_packet_filters/using-and-configuring-firewalld_firewall-packet-filters[Using and configuring firewalld in _{RHEL}{nbsp}9 Configuring firewalls and packet filters_]
 endif::[]

guides/doc-Planning_for_Project/master.adoc

@@ -29,7 +29,7 @@ ifndef::foreman-deb[]
 include::common/modules/con_security-considerations.adoc[leveloffset=+1]
 endif::[]
 
-include::common/assembly_networking-in-project.adoc[leveloffset=+1]
+include::common/assembly_networking-considerations-in-project.adoc[leveloffset=+1]
 
 include::common/assembly_deployment-path.adoc[leveloffset=+1]