fix(rdb): vpc routing

Author: ldecarvalho-doc

pages/managed-databases-for-postgresql-and-mysql/how-to/connect-database-private-network.mdx

@@ -22,6 +22,11 @@ This improves performance by reducing the latency between your application and y
 
 You can create new Database Instances to attach to your Private Network, or attach existing ones.
 
+<Message type="note">
+  Managed Databases for PostgreSQL and MySQL is compatible with the [VPC routing](https://www.scaleway.com/en/docs/vpc/concepts/#routing) feature, which allows you to connect one or more Database Instances in Private Network to resources in other Private Networks of the same VPC. Refer to the [How to manage routing](/vpc/how-to/manage-routing/) documentation page for more information.
+</Message>
+
+
 <Macro id="requirements" />
 
 - A Scaleway account logged into the [console](https://console.scaleway.com)
@@ -31,9 +36,9 @@ You can create new Database Instances to attach to your Private Network, or atta
 
 ## How to attach a Database Instance to a Private Network
 
-  <Message type="note">
-      You can only attach your Database Instance to one Private Network at a time.
-  </Message>
+<Message type="note">
+  You can only attach your Database Instance to one Private Network at a time.
+</Message>
 
 1. Click **PostgreSQL and MySQL** under **Databases** on the side menu. A list of your Database Instances displays.
 2. Select the geographical region of the Instance you want to manage from the drop-down.

pages/vpc/reference-content/understanding-routing.mdx

@@ -25,7 +25,7 @@ You can create your own custom routes to send traffic for defined IP ranges towa
 
 Routing is activated by default whenever you create a new VPC, and can be activated on pre-existing VPCs by [following these steps](/vpc/how-to/manage-routing/#how-to-activate-routing). More routing features are planned for the future, such as ACLs and firewalling.
 
-The diagram below shows an example of how routing works across two Private Networks on a VPC. The route table is held on the VPC's virtual router ([VRouter](/vpc/concepts/#vrouter)), and synched to each resource as it joins a Private Network. 
+The diagram below shows an example of how routing works across two Private Networks on a VPC. The route table is held on the VPC's virtual router ([VRouter](/vpc/concepts/#vrouter)), and synched to each resource as it joins a Private Network.
 - An Elastic Metal server on Private Network A can send a packet to the public internet via a Public Gateway also attached to Private Network A.
 - An Instance also on Private Network A can send a packet to an Instance on Private Network B, via the vRouter.
 - The same Instance on Private Network A can send a packet to an IP destination at the other end of the VPN hosted on Instance XYZ on Private Network B, thanks to a custom route.
@@ -39,7 +39,7 @@ The diagram below shows an example of how routing works across two Private Netwo
 Every VPC has an associated **route table**, used to manage and control the routing of traffic within the VPC. The routes within a route table tell the VPC where to send traffic trying to get to a specific destination IP address. One line in the route table corresponds to one route. A route consists of:
 
 - A **destination** IP or IP range. This specifies that the route applies to traffic with a matching destination IP.
-- A **next hop**. This specifies where the VPC should forward traffic that is trying to reach the destination IP. 
+- A **next hop**. This specifies where the VPC should forward traffic that is trying to reach the destination IP.
     - For local subnet routes, the next hop will be the relevant Private Network. Traffic destined for an IP within the CIDR block of the Private Network's subnet will find the attached resource there.
     - For custom routes, the next hop is a defined resource on a defined Private Network.
     - If the destination IP is not known on the VPC (represented by the `0.0.0.0/0` address), its next hop will be a Public Gateway so that it can reach the public internet (as long as a Public Gateway set to advertise the default route has been attached to the Private Network).
@@ -79,5 +79,4 @@ For example, you may use one Private Network for frontend resources and another
 
 ## Limitations
 
-- Managed Databases are not currently compatible with routing. The VPC cannot automatically route between Managed Databases on different Private Networks, or (for example) between a Managed Database on one Private Network and an Instance on a different Private Network.
 - VPC routing does not currently support virtual IPs.