fix(vpc): fix default info (#5113)

* fix(vpc): fix default info

* fix(vpc): delete

Author: RoRoJ

pages/elastic-metal/how-to/use-private-networks.mdx

@@ -65,7 +65,7 @@ You can also attach custom resources, such as virtual machines hosted on your El
     - Select **Attach to a new Private Network**, and enter a name for the new Private Network you wish to create.
     <Message type="note">
     The Private Network will have default settings, meaning:
-      - It is created in your [default VPC](/vpc/concepts/#default-vpc) for the region. If you do not have an existing VPC for the appropriate region, one will be auto-created for you
+      - It is created in your [default VPC](/vpc/concepts/#default-vpc) for the region, if you have one. If you do not have an existing VPC for the appropriate region, you must [create one](/vpc/how-to/create-vpc/#how-to-create-a-vpc) first.
       - It has an auto-generated [CIDR block](/vpc/concepts/#cidr-block) used to allocate private IP addresses to servers attached to the network. Each attached Elastic Metal server will get an IPv4 and an IPv6 address on the Private Network.
     </Message>
 6. Choose whether to **auto-allocate an available IP from the pool** (the [CIDR block](/vpc/concepts/#cidr-block) defined at the time of creating the Private Network), or use a [reserved IP address](/ipam/concepts/#reserved-ip-address) for the attachment. You must make this choice for both the IPv4 and IPv6 address that the Elastic Metal server will have on this Private Network.

pages/instances/how-to/use-private-networks.mdx

@@ -37,7 +37,7 @@ If you want to create a Private Network without immediately attaching any resour
 6. Enter a **Name** for your Private Network, or leave the randomly-generated name in place.
 7. Click **Attach to a Private Network** to finish.
 
-    Your Private Network is created in your [default VPC](/vpc/concepts/#default-vpc) for the region, if one exists. If you do not have an existing VPC for the appropriate region, one will be auto-created for you. The Private Network will have default settings, meaning an auto-generated [CIDR block](/vpc/concepts/#cidr-block).
+    Your Private Network is created in your [default VPC](/vpc/concepts/#default-vpc) for the region, if one exists. If you do not have an existing VPC for the appropriate region, you must [create one](/vpc/how-to/create-vpc/#how-to-create-a-vpc) first. The Private Network will have default settings, meaning an auto-generated [CIDR block](/vpc/concepts/#cidr-block).
 
     You are taken back to the Private Networks tab, where your new Private Network is now displayed in the list and you can see the IP address for your Instance on the network. For more information about resources' private IP addresses on a Private Network, see our [dedicated documentation](/vpc/how-to/attach-resources-to-pn/#how-to-view-the-resources-ip-address).
 

pages/public-gateways/how-to/configure-a-public-gateway.mdx

@@ -36,7 +36,7 @@ This page shows you how to attach a [Public Gateway](/public-gateways/concepts/#
       <Message type="note">
         Only Private Networks which are in the same region as the Public Gateway are displayed in this list.
       </Message>
-    - If you want to create and attach a new Private Network, select **Attach to a new Private Network**. The Private Network will be created with default configuration (a [CIDR block](/vpc/concepts#cidr-block) will be automatically defined), in your default VPC for the region, if one exists. If you do not have an existing VPC for the appropriate region, one will be auto-created for you. A name for the Private Network will be suggested, but feel free to overwrite this with a new name of your choice. Dynamic NAT will be automatically activated on the Public Gateway for the Private Network.
+    - If you want to create and attach a new Private Network, select **Attach to a new Private Network**. The Private Network will be created with default configuration (a [CIDR block](/vpc/concepts#cidr-block) will be automatically defined), in your default VPC for the region, if one exists. If you do not have an existing VPC for the appropriate region, you must [create one](/vpc/how-to/create-vpc/#how-to-create-a-vpc) first. A name for the Private Network will be suggested, but feel free to overwrite this with a new name of your choice. Dynamic NAT will be automatically activated on the Public Gateway for the Private Network.
 6. Choose whether to **auto-allocate an available IP from the pool** (the [CIDR block](/vpc/concepts/#cidr-block) defined at the time of creating the Private Network), or use a **[reserved IP address](/ipam/concepts/#reserved-ip-address)** for the attachment.
 7. Use the toggle to select whether to **Advertise the default route**. Find out more about this setting in our [concepts documentation](/public-gateways/concepts/#default-route).
 8. Click **Attach to Private Network** to finish. You are taken back to the Private Networks tab, where the network you attached now appears, along with the services configured and the IP address of the Public Gateway.

pages/vpc/concepts.mdx

@@ -24,9 +24,26 @@ An IPv4 CIDR block and an IPv6 CIDR block are defined for each Scaleway Private
 
 ## Default VPC
 
-If you created your Scaleway [Project](/organizations-and-projects/concepts/#project) before 13 May 2025, one **default VPC** was automatically created in it for each region (Paris, Amsterdam and Warsaw). Any new Private Networks that you create will be added to the default VPC for their region, unless you override this by specifying a different VPC.
-
-If you created your Scaleway Project after 13 May 2025, default VPCs are no longer pre-created for you. The first VPC that you create in each region is designated as its default VPC.
+#### Projects created before 13 May 2025
+<br/>
+- One default VPC was automatically created for each region (Paris, Amsterdam and Warsaw).
+- New Private Networks that you create without specifying a VPC are added to the default VPC for their region.
+
+
+#### Projects created after 13 May 2025
+
+- Default VPCs are no longer automatically created for you.
+
+    - **Console**: 
+        - The concept of default VPCs is no longer needed or relevant.
+        - You must create a VPC for a given region before you can create a Private Network in that region.
+        - You are prompted to specify a VPC every time you create a Private Network.
+    - **API**:
+        - The `is_default` field continues to exist, and as before, it cannot be updated or set by the user.
+        - If you create your own VPCs, and always specify one of them when creating a Private Network, none of your VPCs will be flagged as `is_default`.
+        - When you create a Private Network in a given Project/region **without specifying a pre-existing VPC** for the first time, a VPC is auto-created for you and designated as default for the Project/region via the `is_default` flag.
+        - Any further Private Networks that you create in that Project/region without specifying a VPC will be added to the auto-created `is_default` VPC.
+        - User-created VPCs cannot be set as default. 
 
 ## DHCP
 

pages/vpc/faq.mdx

@@ -28,7 +28,7 @@ You cannot delete a default VPC, but you can rename it, and/or create other VPCs
 Default VPCs do not prevent you from deleting an otherwise empty Project.
 </Message>
 
-If you created your Scaleway Project after 13 May 2025, default VPCs are no longer pre-created for the Project. The first VPC that you create in each region is designated as its default VPC. If you try to create a Private Network without having an existing VPC for the appropriate region, a VPC will be auto-created for you.
+If you created your Scaleway Project after 13 May 2025, default VPCs are no longer pre-created for the Project. Find out more in our [dedicated documentation](/vpc/concepts/#default-vpc).
 
 ## VPC routing
 

pages/vpc/how-to/create-vpc.mdx

@@ -24,7 +24,7 @@ VPC allows you to build your own **V**irtual **P**rivate **C**loud on top of Sca
 
 ### Before 13 May 2025
 
-If you created your Scaleway [Project](/organizations-and-projects/concepts/#project) before 13 May 2025, one **default VPC** was automatically created in it for each region (Paris, Amsterdam and Warsaw). Any new Private Networks that you create will be added to the default VPC for their region, unless you override this by specifying a different VPC.
+If you created your Scaleway [Project](/organizations-and-projects/concepts/#project) before 13 May 2025, one **default VPC** was automatically created in it for each region (Paris, Amsterdam and Warsaw). Any new Private Networks that you create without specifying a VPC will be added to the default VPC for their region.
 
 Click **VPC** in the **Network** section of the Scaleway console side menu. Your VPC [dashboard](https://console.scaleway.com/vpc/vpc) displays:
 
@@ -42,12 +42,10 @@ It is currently not possible to change the default VPC for a region, nor to dele
 
 ### After 13 May 2025
 
-If you created your Scaleway Project after 13 May 2025, default VPCs are no longer pre-created for you. The first VPC that you create in each region is designated as its default VPC.
+If you created your Scaleway Project after 13 May 2025, default VPCs are no longer pre-created for you. You must create a VPC before you can create a Private Network.
 
 ## How to create a VPC
 
-If you want to create more VPCs beyond the default ones created for you, you can do so via the following steps:
-
 1. Click **VPC** in the **Network** section of the Scaleway console side menu.
 
 2. Click <Icon name="plus" /> **Create a VPC**. The VPC creation wizard displays.

pages/vpc/how-to/delete-vpc.mdx

@@ -20,7 +20,7 @@ categories:
 ## How to delete a VPC
 
 You can only delete VPCs that:
-- Do not contain any Private Networks
+- Do not contain any Private Networks or IPAM reserved IPs
 - Are not the [default VPC](/vpc/concepts/#default-vpc) for their region
 
 1. Click **VPC** in the **Network** section of the Scaleway console side menu. The list of your VPCs displays: