simplify a little bit

docs/docs/advanced-concepts/public-and-private-ips-and-ports.md

@@ -45,6 +45,4 @@ The combination of public IP + port _will_ allow you to connect to a container f
 
 ### Gotchas
 
-When exposing a port on a `ServiceConfig` via the `ports` field, the container responsible for managing the enclave, APIContainer (APIC), will perform an availability check (`nc -vz <service ip> <port>`) to ensure the port is exposed.
-Some services by default expose ports on `localhost:<port num>` or `127.0.0.1:<port num>`. This would cause the availability check (eg. `nc -vz 172.0.0.3 9612`) to fail as the APIC communicates with the service on a subnetwork created by Kurtosis for that enclave,
-whilst the port is only exposed on the localhost network interface. The workaround is to expose the port on all network interfaces via `0.0.0.0` eg. `--rpc.laddr tcp://0.0.0.0:36657`.
+When you expose a port on a `ServiceConfig` via the `ports` field, the container responsible for managing the enclave, APIContainer (APIC), will perform an availability check (`nc -vz <service ip> <port>`) on the port. Some services default to exposing ports on `localhost:<port num>` or `127.0.0.1:<port num>`. This causes the availability check (eg. `nc -vz 172.0.0.3 9612`) to fail, as the APIC communicates with the service on a subnetwork created by Kurtosis for that enclave, whilst the port is only exposed on the localhost network interface. The workaround is to expose the port on all network interfaces via `0.0.0.0` eg. `--rpc.laddr tcp://0.0.0.0:36657`.