Apply suggestions from code review

Co-authored-by: Alberto Chiusole <1922124+bebosudo@users.noreply.github.com>
Signed-off-by: Gavin <gav.elder@gmail.com>

Author: gavinelder

platform-cloud/docs/enterprise/advanced-topics/firewall-configuration.md

@@ -15,18 +15,6 @@ This endpoint returns a JSON object that can be parsed to dynamically adapt your
 $ python3
 >>> import requests
 >>> requests.get("https://meta.seqera.io").json()
-{
-  "egress": [
-    "18.169.21.18/32",
-    "18.135.7.45/32",
-    "18.171.4.252/32"
-  ],
-  "ingress": [
-    "35.179.197.5/32",
-    "3.11.38.17/32",
-    "18.175.79.222/32"
-  ]
-}
 ```
 
 ### DNS allowlist

platform-enterprise_versioned_docs/version-25.1/enterprise/configuration/networking.md

@@ -16,15 +16,15 @@ Your Seqera Enterprise must be allowed to communicate with licences.seqera.io on
 
 ### Fusion and other Enterprise plugins
 
-[Fusion file system](../../supported_software/fusion/overview.md) and other Seqera Enterprise plugins have built-in licence checking built-in. As such, you must also allow network traffic from the your Seqera compute environment executing Nextflow jobs. 
+[Fusion file system](../../supported_software/fusion/overview.md) and other Seqera Enterprise plugins have built-in license checking. As such, you must also allow network traffic from your Seqera compute environment executing Nextflow jobs. 
 
 ### Studios
 
-See [Studios deployment](../studios.md) for details on the Seqera-hosted URLs, and internal subdomains of your Platform instance host domain, that must be allowed for ingress and egress traffic. 
+See [Studios deployment](../studios.md) for details on the Seqera-hosted URLs and internal subdomains of your Platform instance host domain, which must be allowed for ingress and egress traffic. 
 
 ### Wave
 
-To use Seqera Cloud-hosted [Wave](https://docs.seqera.io/wave) with the Mirror or Freeze functionality, which requires Wave to store built containers within your container registry, you must to ensure that the wave-build VPC is allowed to push to your container registry. For most cloud providers, this requires additional configuration to lock down, but is generally allowed by default.
+To use Seqera Cloud-hosted [Wave](https://docs.seqera.io/wave) with the Mirror or Freeze functionality, which requires Wave to store built containers within your container registry, you must ensure that the wave-build VPC is allowed to push to your container registry. For most cloud providers, this is generally permitted by default; you may contact your network administrators to verify whether additional firewall rules have been defined.
 
 Ensure your Enterprise instance can communicate with the following Seqera-hosted Wave service IP addresses on port 443: