fix lint

Author: yfodil

docs/guides/migration_guide_vpcgw_v2.md

@@ -4,13 +4,13 @@ page_title: "Migrating from Legacy VPC Gateway to v2"
 
 # Migrating from Legacy VPC Gateway to v2
 
-This guide explains how to migrate from the legacy VPC gateway configuration (v1) to the new v2 API. 
-In the legacy setup, DHCP and DHCP reservations are managed with dedicated resources and referenced in the gateway network. 
+This guide explains how to migrate from the legacy VPC gateway configuration (v1) to the new v2 API.
+In the legacy setup, DHCP and DHCP reservations are managed with dedicated resources and referenced in the gateway network.
 In v2, the public gateway is migrated to use IPAM (IP Address Management) mode.
 In 2023, DHCP functionality was moved from Public Gateways to Private Networks, DHCP resources are now no longer needed.
 
 Note:
-During migration, you need to trigger the migration call by setting the `migrate_to_v2` flag on your public gateway resource. 
+During migration, you need to trigger the migration call by setting the `migrate_to_v2` flag on your public gateway resource.
 You can do this via the Terraform configuration or by using the Scaleway CLI/Console.
 
 ## Prerequisites
@@ -111,7 +111,7 @@ After triggering the migration, update your Terraform configuration as follows:
 2. **Update the Gateway Network**
 
     Replace the DHCP related attributes with an `ipam_config` block. For example
-    
+
     ```hcl
     resource "scaleway_vpc_gateway_network" "main" {
       gateway_id         = scaleway_vpc_public_gateway.main.id
@@ -125,7 +125,7 @@ After triggering the migration, update your Terraform configuration as follows:
 
 ### Using the IPAM Datasource and Resource for Reservations
 
-After migrating your public gateway to v2, you no longer manage DHCP reservations with dedicated resources. 
+After migrating your public gateway to v2, you no longer manage DHCP reservations with dedicated resources.
 Instead, you remove the legacy DHCP reservation resource and switch to using IPAM to manage your IPs.
 
 1. **Retrieve an Existing IP with the IPAM Datasource**  
@@ -137,6 +137,7 @@ Instead, you remove the legacy DHCP reservation resource and switch to using IPA
      type        = "ipv4"
    }
    ```
+   
    You can now use data.scaleway_ipam_ip.existing.id in your configuration to reference the reserved IP.
 
 2. **Book New IPs Using the IPAM IP Resource**
@@ -153,8 +154,9 @@ Instead, you remove the legacy DHCP reservation resource and switch to using IPA
 
 3. **Attach the Reserved IP to Your Resources**
 
-    Once you have your IP—whether retrieved via the datasource or booked as a new resource—you can attach it to your server’s private NIC:
-    ```hcl
+   Once you have your IP—whether retrieved via the datasource or booked as a new resource—you can attach it to your server’s private NIC:
+   
+   ```hcl
    resource "scaleway_instance_private_nic" "pnic01" {
      private_network_id = scaleway_vpc_private_network.main.id
      server_id          = scaleway_instance_server.main.id