Skip to content

Commit 6c4c9c4

Browse files
Apply suggestions from code review
Co-authored-by: Jessica <[email protected]>
1 parent 298654b commit 6c4c9c4

File tree

4 files changed

+4
-4
lines changed

4 files changed

+4
-4
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ This can now be fixed by installing a new version of the OpenVPN scripts, which
2020
You can also avoid this situation altogether by installing the package prior to moving to a routed IP.
2121

2222
<Message type="note">
23-
This guide addresses specific issues related to OpenVPN Instances. For general information on routed IPs and migration procedures, refer to our [main migration guide](/docs/compute/instances/how-to/migrate-routed-ips/) and the [related FAQ](/faq/instances/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature).
23+
This guide addresses specific issues related to OpenVPN Instances. For general information on routed IPs and migration procedures, refer to our [main migration guide](/compute/instances/how-to/migrate-routed-ips/) and the [related FAQ](/faq/instances/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature).
2424
</Message>
2525

2626

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ categories:
1616
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.
1717

1818
<Message type="note">
19-
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](/docs/compute/instances/how-to/migrate-routed-ips/) and the [related FAQ](/faq/instances/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature).
19+
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](/compute/instances/how-to/migrate-routed-ips/) and the [related FAQ](/faq/instances/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature).
2020
</Message>
2121

2222
1. Install the new `debian-stable` PPA.

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ The version of `systemd-networkd` used in Ubuntu Focal does not support the defi
2020
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.
2121

2222
<Message type="note">
23-
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](/docs/compute/instances/how-to/migrate-routed-ips/) and the [related FAQ](/faq/instances/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature).
23+
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](/compute/instances/how-to/migrate-routed-ips/) and the [related FAQ](/faq/instances/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature).
2424
</Message>
2525

2626
## Your Instance has not been rebooted

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ The affected O/S distributions are:
2727
</Message>
2828

2929
<Message type="note">
30-
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](/docs/compute/instances/how-to/migrate-routed-ips/) and the [related FAQ](/faq/instances/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature).
30+
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](/compute/instances/how-to/migrate-routed-ips/) and the [related FAQ](/faq/instances/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature).
3131
</Message>
3232

3333
## Your Instance has not been migrated to routed IP yet

0 commit comments

Comments
 (0)