fix(rdb): remove ip assignment mentions in faq (#4102)

Author: ldecarvalho-doc

faq/databases-for-postgresql-and-mysql.mdx

@@ -96,21 +96,17 @@ The idea is to offer the best performance to our users by reducing latency betwe
 
 ## What is the Private Networks feature for Database Instances?
 
-[Private Networks](/network/public-gateways/quickstart/) allows you to configure your own Layer-2 network with IPv4 addresses. You can therefore enhance the security of your system architecture by isolating it from the internet.
+[Private Networks](/network/public-gateways/quickstart/) allow you to enhance the security of your system architecture by isolating it from the internet.
 
 This feature introduces a significant change in the architecture of Scaleway's Databases: when using Private Networks, your application connects directly to your Database nodes, without going through a Load Balancer.
 This improves performance by reducing the latency between your nodes. It also increases the security of your databases, since Instances in your Private Network can connect directly to your Database Instance, without passing through the public internet.
 
-You can create new Database Instances to attach to your Private Network or attach existing Database Instances by adding Private Networks endpoints to them.
+You can create new Database Instances to attach to your Private Network or attach existing Database Instances.
 
 ## How many Private Networks can I attach?
 
 Currently, you can connect one Private Network to each Database Instance.
 
-## Can I use any IP Range for my Private Network?
-
-For now, only the [RFC1918](https://datatracker.ietf.org/doc/html/rfc1918) IP subnets are accepted as Database Instances virtual IPv4.
-
 ## How is the Database's private failover IP managed?
 
 The virtual IPv4 used to expose the Database Instance service is automatically routed to the newly promoted node and announced within 10s to the neighboring Compute Instances.

faq/databases-for-redis.mdx

@@ -37,31 +37,22 @@ You can connect to your Managed Database for Redis™ using the IP address(es) a
 
 ## What is the Private Networks feature for Redis™ Database Instances?
 
-[Private Networks](/network/public-gateways/quickstart/) allow you to configure your Layer-2 network with IPv4 addresses on Managed Database for Redis™ Instances.
+[Private Networks](/network/public-gateways/quickstart/) allow you to increase the security of your databases since Instances in your Private Networks can directly be connected to your Redis™ Database Instance without passing through the public internet.
 
-It also increases the security of your databases since Instances in your Private Networks can directly be connected to your Redis™ Database Instance without passing through the public internet.
 In standalone mode, you can attach Private Networks to your Redis™ Database Instances at the creation level or add a Private Networks endpoint to your existing Redis™ Database Instance from the console.
 
 <Message type="note">
-  When you select cluster mode, Private Networks can only be selected and configured upon creating the Redis™ Database Instance. Once the cluster has been completed, it is impossible to attach it to a Private Network or to edit the configuration of an existing one. If you want to switch to a public network or update your IP addresses, you must create a new Redis™ Database Instance.
+  When you select cluster mode, Private Networks can only be selected and configured upon creating the Redis™ Database Instance. Once the cluster has been completed, it is impossible to attach it to a Private Network or to edit the configuration of an existing one. If you want to switch to a public network you must create a new Redis™ Database Instance.
 </Message>
 
 ## How many Private Networks can I attach?
 
 Currently, you can connect one Private Network to each Redis™ Database Instance in the Scaleway console. For standalone Instances, you can attach multiple Private Networks via the CLI or the API only.
 
-## Can I use any IP Range for my Private Network?
-
-For now, only the [RFC1918](https://datatracker.ietf.org/doc/html/rfc1918) IP subnets are accepted as a Redis™ Database Instance virtual IPv4.
-
 ## How is the Redis™ Database's failover IP managed?
 
 The Redis™ controller knows the cluster topology and automatically routes requests to a healthy node. In case of unavailability of one of the cluster nodes, no downtime is to be expected.
 
-## What should I use as virtual IP? How do I calculate the CIDR netmask?
-
-In a cluster topology, you must [provide a private IPv4 address](/faq/databases-for-postgresql-and-mysql/#what-should-i-use-as-virtual-ip-how-do-i-calculate-the-cidr-netmask) to each node. For instance, if you have a three-node cluster, you must declare 3 IPs on the same L3 network. The 3 IPs must be able to connect to each other.
-
 ## What is the logic behind the cluster mode?
 
 A Redis cluster contains a minimum of 3 nodes and up to 6 nodes. Each node contains a source and a replica.