Update compute/instances/how-to/migrate-routed-ips.mdx

Co-authored-by: Fabien Malfoy <[email protected]>

Author: ziirish

compute/instances/how-to/migrate-routed-ips.mdx

@@ -15,7 +15,7 @@ categories:
 
 During deployment, each Instance prior April 2024 used to get a NAT IP from its hosting node, besides its public IP, which is routed to the Instance through a [carrier-grade NAT](/compute/instances/concepts/#carrier-grade-nat-(cgnat)) solution. However, if the underlying hypervisor changes, the NAT IP changes. This can happen when you restart your Instance. The NAT IP lets Instances communicate via an underlying internal network, without public IPs.
 
-Routing a public IP directly to an Instance bypasses NAT IPs, sending traffic to its [routed flexible IP](/compute/instances/concepts/#routed-flexible-ip). The benefit is the IP stays consistent even if the Instance is restarted or moved. Routed IPs also let you assign multiple flexible IPv4s and IPv6s to an Instance, as both IPv4 and IPv6 are supported (more on that bellow).
+Routing a public IP directly to an Instance bypasses NAT IPs, sending traffic to its [routed flexible IP](/compute/instances/concepts/#routed-flexible-ip). The benefit is the IP stays consistent even if the Instance is restarted or moved. Routed IPs also let you assign multiple flexible IPv4s and IPv6s to an Instance, as both IPv4 and IPv6 are supported (see below for details).
 
 Using a routed flexible IP is recommended, as it allows precise control over network configurations. It simplifies troubleshooting, ensures compatibility with more applications, and allows for enhanced security monitoring.