From 4d772424c5ae8049a8a0ccfb2fb802ab0d8eed93 Mon Sep 17 00:00:00 2001 From: Rowena Jones <36301604+RoRoJ@users.noreply.github.com> Date: Tue, 26 Nov 2024 11:48:45 +0100 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Jessica <113192637+jcirinosclwy@users.noreply.github.com> --- network/ipam/reference-content/ipv6.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/network/ipam/reference-content/ipv6.mdx b/network/ipam/reference-content/ipv6.mdx index cb1b4bb626..ad228d266c 100644 --- a/network/ipam/reference-content/ipv6.mdx +++ b/network/ipam/reference-content/ipv6.mdx @@ -64,7 +64,7 @@ Scaleway Elastic Metal servers are compatible with IPv6. You can attach one or multiple public (flexible) IPv6 addresses to your Elastic Metal server, as well as, or instead of, a public IPv4 address. These public addresses are flexible, meaning that you can detach them from an Elastic Metal server, hold them in your account, and attach them to a different Elastic Metal server, if you want. Each flexible IPv6 address is a `/64` IPv6 subnet. Flexible IPv6 addresses can also be used as additional IP addresses to create virtual machines on your Elastic Metal server. -In addition to the possibility of attaching and detaching flexible IP addresses, note that each Elastic Message server also comes with a statically routed public IPv4 address, which cannot be detached, other than manually. +In addition to the possibility of attaching and detaching flexible IP addresses, note that each Elastic Metal server also comes with a statically routed public IPv4 address, which cannot be detached, other than manually. #### Private IPv6 @@ -121,7 +121,7 @@ VPC and Private Networks are compatible with IPv6. ### Serverless Functions and Containers and IPv6 -Serverless Functions and Containers are compatible with public IPv6 traffic. A Function or Container endpoint resolves to both IPv4 and IPv6 addresses (dual stack), ensuring compatibility for clients using either protocol. +Serverless Functions and Containers are compatible with public IPv6 traffic. A function or container endpoint resolves to both IPv4 and IPv6 addresses (dual stack), ensuring compatibility for clients using either protocol. ## Other products and IPv6 @@ -129,7 +129,7 @@ Products other than those listed here do not officially support IPv6. These non- Please open or upvote a [feature request](https://feature-request.scaleway.com/) to register your interest in IPv6 for these resources. -Alternatively, get in touch on the [Scaleway Slack Community](/tutorials/scaleway-slack-community/) if you'd like to find out more about IPv6 compatibility of these or other products. +Alternatively, get in touch on the [Scaleway Slack Community](/tutorials/scaleway-slack-community/) to find out more about IPv6 compatibility of these or other products. ## IPv6 best practices