upd docs

docs/source/examples/ports.rst

@@ -67,5 +67,4 @@ Things You Should Know
 Before you start opening ports, there are a few things you need to bear in mind:
 
 - **Public Accessibility**: Ports you open are exposed to the public internet. It means anyone who knows your VM's IP address and the opened port can try to access your service. Ensure you use security measures, like authentication mechanisms, to protect your services.
-- **Lifecycle Management**: SkyPilot retains the state of all opened ports, even after individual tasks have finished. The rationale behind this is the uncertainty regarding whether tasks, once completed, left behind some backend programs that are still using these ports. Such situations are common when commands like :code:`docker run` or :code:`cmd &` are used, leaving tasks running in the background. To avoid potential disruption or connectivity issues, all previously opened ports remain accessible. The only instance when ports are automatically cleaned up is during cluster shutdown. At this moment, all ports that were opened during the cluster's active lifecycle are conclusively closed. Simultaneously, all corresponding firewall rules and security groups associated with these ports are cleaned up.
-- **Network Costs**: Data transfer costs might be associated with cloud providers when data is sent in and out of your VM. Be aware of the potential costs, especially if you expect high traffic on your opened ports.
+- **Lifecycle Management**: SkyPilot retains the state of all opened ports, even after individual tasks have finished. The only instance when ports are automatically cleaned up is during cluster shutdown. At this moment, all ports that were opened during the cluster's active lifecycle are conclusively closed. Simultaneously, all corresponding firewall rules and security groups associated with these ports are cleaned up.