fix(em): correction (scaleway#4001)

Author: RoRoJ

network/ipam/how-to/reserve-ip.mdx

@@ -18,7 +18,7 @@ categories:
 You can use IPAM to reserve a private IP address from a given Private Network's [CIDR block](/network/vpc/concepts/#cidr-block). When you reserve an IP in this way, it stops it from being potentially auto-allocated to new resources being attached to the Private Network. You can then use the reserved address to attach the specific resource of your choice to the Private Network. If you later detach the resource from the network, the reserved IP will stay reserved, until you either release it back into the general pool, or use it to attach a different resource.
 
 <Message type="note">
-Currently, only **Instances**, **Load Balancers**, and **Public Gateways** are compatible with reserved private IPs. Support for Managed Databases and Elastic Metal servers will be coming soon.
+Currently, only **Instances**, **Elastic Metal servers**, **Load Balancers**, and **Public Gateways** are compatible with reserved private IPs. Support for Managed Databases will be coming soon.
 </Message>
 
 This page sets out the steps necessary to reserve an IP address with IPAM.
@@ -54,7 +54,7 @@ This page sets out the steps necessary to reserve an IP address with IPAM.
 
 ## How to attach a resource to a Private Network using a reserved IP address
 
-You can currently attach **Instances**, **Load Balancers**, and **Public Gateways** to Private Networks using a reserved IP address. Support for Managed Databases and Elastic Metal servers will be coming soon.
+You can currently attach **Instances**, **Elastic Metal servers**, **Load Balancers**, and **Public Gateways** to Private Networks using a reserved IP address. Support for Managed Databases will be coming soon.
 
 The option to use a reserved IP displays when you attach the resource to a Private Network in the console. Follow the instructions below: