fix(ipam): add doc for reserved IPs for EM (#3753)

* fix(ipam): add doc for reserved IPs for EM

* Apply suggestions from code review

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

---------

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

Author: RoRoJ

faq/ipam.mdx

@@ -24,7 +24,7 @@ Management of public (flexible) IP addresses with IPAM is planned for the future
 
 ## Can I use a reserved private IP to attach any kind of resource to a Private Network?
 
-Currently, the Scaleway console only supports attachment with a reserved IP for Instances, Load Balancers and Public Gateways. You can attach Elastic Metal servers to a Private Network using a reserved IP via the [API](https://www.scaleway.com/en/developers/api/elastic-metal/private-network-api/#path-private-networks-add-a-server-to-a-private-network). Support for attachment of reserved IPs for both Elastic Metal servers and Managed Databases in the console will be coming soon.
+Currently, the Scaleway console only supports attachment with a reserved IP for Instances, Load Balancers, Public Gateways, and Elastic Metal servers. Support for Managed Databases will be coming soon.
 
 ## Can I use a reserved private IP with a virtual machine hosted on my Elastic Metal server?
 

network/ipam/concepts.mdx

@@ -20,11 +20,11 @@ When viewing a private IP address in IPAM, it is shown in [CIDR notation](https:
 
 **IP** **A**ddress **M**anager (IPAM) is Scaleway's tool for planning, tracking and managing the IP address space of Scaleway products. It acts as a single source of truth for the IP addresses of Scaleway resources. Managed products, such as Databases and Load Balancer, are fully integrated into IPAM, and Private Networks' [DHCP server](/network/vpc/concepts/#dhcp) uses IPAM to assign private, static IP addresses to attached resources.
 
-The public rollout of IPAM functionality is being carried out gradually. IPAM is now in General Availability, offering several different functionalities in the [Scaleway console](https://console.scaleway.com/ipam/), including viewing, tagging and filtering all your [private IP addresses](#private-ip-address). You can also [reserve](/network/ipam/how-to/reserve-ip/) a private IP on one of your Private Networks and use it to attach an Instance, Load Balancer or Public Gateway to the network.
+The public rollout of IPAM functionality is being carried out gradually. IPAM is now in General Availability, offering several different functionalities in the [Scaleway console](https://console.scaleway.com/ipam/), including viewing, tagging, and filtering all your [private IP addresses](#private-ip-address). You can also [reserve](/network/ipam/how-to/reserve-ip/) a private IP on one of your Private Networks and use it to attach an Instance, Load Balancer, Public Gateway, or Elastic Metal server to the network.
 
 More functionality is planned for the future, including:
 
-- Support for attaching Managed Databases and Elastic Metal servers to a Private Network using a reserved IP address
+- Support for attaching Managed Databases and other resources to a Private Network using a reserved IP address
 - Management of public (flexible) IP addresses
 
 ## IPv4

network/vpc/how-to/attach-resources-to-pn.mdx

@@ -62,9 +62,9 @@ The following resource types can be attached to a Private Network:
 6. Select the type of resource (Instance, Elastic Metal server etc.) that you want to attach. Then select the specific resource to attach. Only resources within the same region (or one of its Availability Zones) as the Private Network will be displayed.
 
     <Message type="tip">
-    When attaching Instances, Load Balancers and Public Gateways, you have the option to either auto-allocate an available IP from the pool of addresses for the Private Network, or to specify an IP that you have already [reserved via IPAM](/network/ipam/how-to/reserve-ip/). For Instances, which support both IPv4 and IPv6 for private IP addresses, you can also choose to auto-allocate or specify a reserved IP for each address type.
+    When attaching Instances, Load Balancers, Public Gateways, and Elastic Metal servers, you have the option to either auto-allocate an available IP from the pool of addresses for the Private Network or specify an IP that you have already [reserved via IPAM](/network/ipam/how-to/reserve-ip/). For Instances, which support both IPv4 and IPv6 for private IP addresses, you can also choose to auto-allocate or specify a reserved IP for each address type.
 
-    Support for using reserved IPs to attach Elastic Metal servers and Managed Databases to Private Networks will be coming soon.
+    Support for using reserved IPs to attach Managed Databases to Private Networks will be coming soon.
     </Message>
 
 7. Click **Attach resource** to finish.