From 36df3f61a6b7be5e53ebcc5c666a068691530c68 Mon Sep 17 00:00:00 2001 From: Rowena Date: Mon, 23 Jun 2025 13:59:05 +0200 Subject: [PATCH] fix(lb): doc review --- pages/load-balancer/how-to/create-manage-flex-ips.mdx | 6 +++--- .../reference-content/public-private-accessibility.mdx | 4 ++-- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/pages/load-balancer/how-to/create-manage-flex-ips.mdx b/pages/load-balancer/how-to/create-manage-flex-ips.mdx index 6987535565..14e18242d5 100644 --- a/pages/load-balancer/how-to/create-manage-flex-ips.mdx +++ b/pages/load-balancer/how-to/create-manage-flex-ips.mdx @@ -7,7 +7,7 @@ content: paragraph: This page explains how to create and manage flexible IP addresses for your Scaleway Load Balancer tags: load-balancer flexible-ip failover-ip flex-ip ip-address reverse reverse-dns dates: - validation: 2024-12-16 + validation: 2025-06-23 posted: 2023-12-05 categories: - network @@ -22,9 +22,9 @@ This page shows you how to use [Load Balancer flexible IP addresses](/load-balan The following limitations apply to Load Balancer flexible IPs: -- A public Load Balancer must have an IPv4 address, and optionally an IPv6 address as well. It cannot have only an IPv6 address. +- A public Load Balancer must have an IPv4 address, and can optionally have an IPv6 address as well. It cannot have only an IPv6 address. - You cannot currently change the flexible IP address of an existing Load Balancer, that is to say you cannot detach its flexible IP after creation to attach a different one. You can attach a flexible IPv6 to a Load Balancer that does not already have one, but you cannot modify or change this address once attached. -- Flexible IPs are associated with a particular product and cannot be moved to a different type of resource. For example, a flexible IP for Load Balancer can be used with another Load Balancer, but it cannot be used with other resource types like Instances or Elastic Metal servers. +- Flexible IPs are associated with a particular product and cannot be moved to a different type of resource. For example, a flexible IP for Load Balancer can be used with another Load Balancer in the same AZ, but it cannot be used with other resource types like Instances or Elastic Metal servers. diff --git a/pages/load-balancer/reference-content/public-private-accessibility.mdx b/pages/load-balancer/reference-content/public-private-accessibility.mdx index fc71bc69ed..60d36ffa3a 100644 --- a/pages/load-balancer/reference-content/public-private-accessibility.mdx +++ b/pages/load-balancer/reference-content/public-private-accessibility.mdx @@ -1,7 +1,7 @@ --- meta: title: Public vs private Load Balancers - description: Learn how to choose an appropriate accessibility setting for your Scaleway Load Balancer, favouring security and isolating with a private Load Balancer, or public accessibility over the internet with a public Load Balancer. + description: Learn how to choose an appropriate accessibility setting for your Scaleway Load Balancer, favoring security and isolating with a private Load Balancer, or public accessibility over the internet with a public Load Balancer. h1: Public vs private Load Balancers paragraph: Learn how to choose an appropriate accessibility setting for your Scaleway Load Balancer, favoring security and isolating with a private Load Balancer, or public accessibility over the internet with a public Load Balancer. tags: load-balancer public private accessibility @@ -9,7 +9,7 @@ categories: - load-balancer - network dates: - validation: 2024-12-16 + validation: 2025-06-23 posted: 2024-06-14 ---