docs(ins): remove deprecated information

Author: bene2k1

pages/instances/faq.mdx

@@ -334,4 +334,4 @@ Yes, they can communicate with each other using their public IPs.
 
 Currently, additional routed IPv6 addresses do not autoconfigure on CentOS 7, 8, 9, Alma 8, 9, Rocky 8, 9 after migration.
 Additional routed IPv4 and IPv6 addresses are not autoconfigured post-migration on Ubuntu 20.04 Focal. However, the primary IPv6 continues to be configured via SLAAC. These limitations are currently being addressed.
-For detailed migration steps, refer to our [migration guide](/instances/how-to/migrate-routed-ips/). If you encounter connectivity issues with Ubuntu Focal Instances having multiple public IPs, consult our [troubleshooting guide](/instances/troubleshooting/fix-unreachable-focal-with-two-public-ips/).
+If you encounter connectivity issues with Ubuntu Focal Instances having multiple public IPs, consult our [troubleshooting guide](/instances/troubleshooting/fix-unreachable-focal-with-two-public-ips/).

pages/instances/troubleshooting/fix-broken-vpn-when-switching-openvpn-vm-to-routed-ip.mdx

@@ -20,7 +20,7 @@ This can now be fixed by installing a new version of the OpenVPN scripts, which
 You can also avoid this situation altogether by installing the package prior to moving to a routed IP.
 
 <Message type="note">
-  This guide addresses specific issues related to OpenVPN Instances. For general information on routed IPs and migration procedures, refer to our [main migration guide](/instances/how-to/migrate-routed-ips/) and the [related FAQ](/instances/faq/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature).
+  This guide addresses specific issues related to OpenVPN Instances. For general information on routed IPs and migration procedures, refer to the [related FAQ](/instances/faq/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature).
 </Message>
 
 

pages/instances/troubleshooting/fix-lost-ip-connectivity-on-debian-buster.mdx

@@ -16,7 +16,7 @@ categories:
 On older Debian Buster images, the installed custom version of `cloud-init` may interfere with IPv6 connectivity when the Instance transitions to using routed IP. To avoid this, you should install a newer version of `cloud-init` before the migration to routed IP. This procedure also recovers connectivity for an Instance already using routed IP.
 
 <Message type="note">
-  This guide addresses specific issues related to older Debian Buster Instances transitioned to routed IP. For general information on routed IPs and migration procedures, refer to our [main migration guide](/instances/how-to/migrate-routed-ips/) and the [related FAQ](/instances/faq/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature).
+  This guide addresses specific issues related to older Debian Buster Instances transitioned to routed IP. For general information on routed IPs and migration procedures, refer to the [related FAQ](/instances/faq/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature).
 </Message>
 
 1. Install the new `debian-stable` PPA.

pages/instances/troubleshooting/fix-unreachable-focal-with-two-public-ips.mdx

@@ -20,7 +20,7 @@ The version of `systemd-networkd` used in Ubuntu Focal does not support the defi
 A modified `cloud-init` package named `cloud-init_24.2-0ubuntu1~20.04.1+scaleway` has been added to Scaleway's stable PPA to work around this situation.
 
 <Message type="note">
-  This guide addresses specific issues related to Ubuntu Focal Instances with multiple public IPs. For general information on routed IPs and migration procedures, refer to our [main migration guide](/instances/how-to/migrate-routed-ips/) and the [related FAQ](/instances/faq/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature).
+  This guide addresses specific issues related to Ubuntu Focal Instances with multiple public IPs. For general information on routed IPs and migration procedures, refer to the [related FAQ](/instances/faq/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature).
 </Message>
 
 ## Your Instance has not been rebooted

pages/instances/troubleshooting/fix-unreachable-ipv6-rhel-based-instance.mdx

@@ -29,7 +29,7 @@ The affected O/S distributions are:
 </Message>
 
 This guide addresses specific issues related to RHEL-based Instances after transitioning to routed IP.
-For general information on routed IPs and migration procedures, refer to our [main migration guide](/instances/how-to/migrate-routed-ips/) and the [related FAQ](/instances/faq/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature).
+For general information on routed IPs and migration procedures, refer to the [related FAQ](/instances/faq/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature).
 
 ## Cause
 
@@ -103,7 +103,7 @@ Activate the web console with: systemctl enable --now cockpit.socket
 ```
 
 ## Going further
-For general information on routed IPs and migration procedures, refer to our [main migration guide](/instances/how-to/migrate-routed-ips/) and the [related FAQ](/instances/faq/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature). If you still encounter issues, please provide the following information when creating a support ticket:
+For general information on routed IPs and migration procedures, refer to the [related FAQ](/instances/faq/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature). If you still encounter issues, please provide the following information when creating a support ticket:
 - Instance ID
 - Operating System version
 - Current IP configuration