Apply suggestions from code review

Co-authored-by: Jessica <[email protected]>

Author: bene2k1

pages/instances/how-to/use-flexips.mdx

@@ -17,8 +17,8 @@ This page provides guidance on using [flexible IP addresses](/instances/concepts
 
 When creating an Instance, you have options for network connectivity:
 
-- **Flexible Routed IPv4 addresses**: These are public IPv4 addresses routed directly to your Instance.
-- **Flexible Routed IPv6 addresses**: These are public IPv6 prefixes routed directly to your Instance.
+- **Flexible routed IPv4 addresses**: public IPv4 addresses routed directly to your Instance.
+- **Flexible routed IPv6 addresses**: public IPv6 prefixes routed directly to your Instance.
 
 Flexible IP addresses can be managed independently of any Instance. You can attach and detach them from any of your Instances and maintain multiple flexible IP addresses in your account simultaneously. They facilitate [live migration of IP addresses between your Instances](/instances/how-to/migrate-instances/).
 
@@ -86,17 +86,17 @@ When you no longer want one of your existing flexible IP addresses, you can dele
 
 ### About routed IPv6
 
-Since [mid 2023](https://www.scaleway.com/en/blog/ip-mobility-removing-nat/), we built a new network stack for Scaleway Instances to enable new features. One of those is the ability to have Flexible/Reserved IPv6 whose main purpose is to allow to keep the same IPv6 whenever you stop/start your Instance.
+Since [mid 2023](https://www.scaleway.com/en/blog/ip-mobility-removing-nat/), we built a new network stack for Scaleway Instances to enable new features. One of those is the ability to have flexible/reserved IPv6 whose main purpose is to allow to keep the same IPv6 whenever you stop/start your Instance.
 
-Prior to routed IPs, IPv6 addresses were statically routed to the Hypervisors, which means your IP changed depending on which Hypervisor your Instance was running on.
+Before routed IPs, IPv6 addresses were statically routed to the hypervisors, which means your IP changed depending on which hypervisor your Instance was running on.
 
 ### IPv6 prefix and SLAAC
 
-Now let's dive into the routed IPv6. Whenever you book a `routed_ipv6` IP type, you get assigned a full IPv6 prefix of 64bits length. According to the [section 2.4](https://datatracker.ietf.org/doc/html/rfc4291#section-2.4) of the RFC4291, except a few prefixes, anything is a Global Unicast  address type. Today's [best practice](https://www.ripe.net/publications/docs/ripe-690/#4-1-1---64-prefix-from-a-dedicated-pool-of-ipv6-prefixes) is to provide a /64 prefix.
+Now, let's dive into the routed IPv6. Whenever you book a `routed_ipv6` IP type, you get assigned a full IPv6 prefix of 64 bits in length. According to [section 2.4](https://datatracker.ietf.org/doc/html/rfc4291#section-2.4) of the RFC4291, except for a few prefixes, anything is a Global Unicast address type. Today's [best practice](https://www.ripe.net/publications/docs/ripe-690/#4-1-1---64-prefix-from-a-dedicated-pool-of-ipv6-prefixes) is to provide a /64 prefix.
 
 Another reason we decided to provide you with a /64 prefix is to be able to use [SLAAC](https://datatracker.ietf.org/doc/html/rfc4862) as the configuration mechanism. But SLAAC has been designed to work [exclusively with /64 prefixes](https://notes.networklessons.com/ipv6-prefix-length-used-for-slaac).
 
-We chose SLAAC over DHCPv6 because it doesn't require any client-side configuration in most of the cases, allowing the feature to work with old instances too.
+We chose SLAAC over DHCPv6 because it doesn't require any client-side configuration in most cases, allowing the feature to work with old Instances too.
 
 ### Limitations
 
@@ -121,7 +121,7 @@ The first one is that, in order not to break already deployed SDKs, or CLIs, we
         }
 ```
 
-On the other hand, the `/servers/<id>` endpoint provides the `public_ip` (deprecated) field and its replacement `public_ips`. This struct also contain an address field of type IP that doesn't accept a prefix:
+On the other hand, the `/servers/<id>` endpoint provides the `public_ip` (deprecated) field and its replacement `public_ips`. This struct also contains an address field of type IP that does not accept a prefix:
 
 ```
 [
@@ -142,28 +142,27 @@ On the other hand, the `/servers/<id>` endpoint provides the `public_ip` (deprec
 
 Instead, we return the SLAAC address based on the EUI-64 of the interface.
 
-One consequence is that, if you move your `routed_ipv6` **prefix** to another instance (hence, with another MAC address), the `public_ips` list will show you a **different** address because its EUI-64 will differ.
+One consequence is that, if you move your `routed_ipv6` **prefix** to another Instance (hence, with another MAC address), the `public_ips` list will show you a **different** address because its EUI-64 will differ.
 
 ## Workaround
 
-Since the whole /64 prefix is routed to your Instance, it is possible to define a second IPv6 address within the prefix that may be used to reach your instance. However, this requires some custom settings.
+Since the whole /64 prefix is routed to your Instance, it is possible to define a second IPv6 address within the prefix that may be used to reach your Instance. However, this requires some custom settings.
 
 In order to do that, we will use the **cloud-init** mechanism to define the second IPv6 address.
 
 Let's say your prefix is: `2025:bd8:911::/64`
 
-We will use the following /128 address within this range: `2025:bd8:911:a7f1::1/128`
+We will use the following /128 address within this range: `2025:bd8:911:a7f1::1/128`.
 
 The cloud-init configuration can be uploaded with the Scaleway CLI:
 
-
 ```
 scw instance server update <SERVER_UUID> [email protected]
 ```
 
 ### Debian >= 11 and Ubuntu >= 20.04
 
-First of all, create a file with the following content
+First of all, create a file with the following content:
 
 ```
 cat << EOF > ipv6-cloud-init.txt
@@ -187,7 +186,7 @@ This cloud-init configuration file will add the `netplan` definition of a second
 
 ### CentOS Stream 9, AlmaLinux >= 8 and RockyLinux >= 8
 
-For CentOS Stream 9, AlmaLinux >= 8 and RockyLinux >= 8 you need to interact with `NetworkManager` instead of `netplan`.
+For CentOS Stream 9, AlmaLinux >= 8, and RockyLinux >= 8, you must interact with `NetworkManager` instead of `netplan`.
 
 ```
 cat << EOF > ipv6-cloud-init.txt