docs(block-storage): feedback

Author: nerda-codes

macros/storage/block-storage-migration.mdx

@@ -3,7 +3,7 @@ macro: block-storage-migration
 ---
 
 <Message type="important">
- - Scaleway is transitioning the management of all Block Storage legacy volumes and snapshots from the [Instance API](https://www.scaleway.com/en/developers/api/instance/) to the [Block Storage API](https://www.scaleway.com/en/developers/api/block/).
- - Find out about the [advantages of migrating the management of your volumes and snapshots](advantages-migrating-to-sbs) from the Instance API to the Block Storage API.
+ - Scaleway is transitioning the management of all block volumes and snapshots from the [Instance API](https://www.scaleway.com/en/developers/api/instance/) to the [Block Storage API](https://www.scaleway.com/en/developers/api/block/).
+ - Find out about the [advantages of migrating the management of your volumes and snapshots](/storage/block/reference-content/advantages-migrating-to-sbs/) from the Instance API to the Block Storage API.
  - Find out how to [migrate your Block Storage legacy volumes and snapshots](/compute/instances/how-to/migrate-volumes-snapshots-to-sbs/) from the Instance API to the Block Storage API.
 </Message>

menu/navigation.json

@@ -4559,10 +4559,6 @@
                     "label": "Create a Block Storage volume from a snapshot",
                     "slug": "create-volume-from-snapshot"
                   },
-                  {
-                    "label": "Identify a volume and snapshot type",
-                    "slug": "identify-volume-snapshot-type"
-                  },
                   {
                     "label": "Detach a volume",
                     "slug": "detach-a-volume"
@@ -4608,7 +4604,7 @@
                     "slug": "differences-between-5kiops-volumes"
                   },
                   {
-                    "label": "Advantages of migrating your Block Storage legacy volumes and snapshots to Block Storage Low Latency",
+                    "label": "Advantages of migrating from the Instance API to the Block Storage API for managing block volumes and snapshots",
                     "slug": "advantages-migrating-to-sbs"
                   }
                 ],

storage/block/api-cli/identifying-volume-snapshot-api.mdx

@@ -6,13 +6,13 @@ content:
   h1: Identifying the API managing Block Storage volumes and snapshots
   paragraph: Determine whether your Block Storage volumes and snapshots are managed by the Instance API or Block Storage API.
 dates:
-  validation: 2025-01-03
-  posted: 2025-01-03
+  validation: 2025-01-07
+  posted: 2025-01-07
 categories:
   - storage
 ---
 
-This page shows you how to identify the API managing your Block Storage volumes and snapshots, using the API and CLI.
+This page shows you how to identify the API managing your Block Storage volumes and snapshots, using the Scaleway API and CLI.
 
 <Macro id="block-storage-migration" />
 

storage/block/how-to/identify-volume-snapshot-type.mdx

@@ -1,29 +1,55 @@
 ---
 meta:
-  title: Advantages of migrating your Block Storage legacy volumes and snapshots to Block Storage Low Latency
-  description: Learn the key advantages of migrating your Block Storage legacy volumes and snapshots to Block Storage Low Latency.
+  title: Advantages of migrating from the Instance API to the Block Storage API for managing block volumes and snapshots
+  description: Learn the key advantages of migrating to the Block Storage API for managing your Block Storage volumes and snapshots.
 content:
-  h1: Advantages of migrating your Block Storage legacy volumes and snapshots to Block Storage Low Latency
-  paragraph: Learn the key advantages of migrating your Block Storage legacy volumes and snapshots to Block Storage Low Latency.
-tags: volumes block-storage 5kiops 10kiops sbs low-latency
+  h1: Advantages of migrating from the Instance API to the Block Storage API for managing block volumes and snapshots
+  paragraph: Learn the key advantages of migrating to the Block Storage API for managing your Block Storage volumes and snapshots.
+tags: volumes block-storage 5kiops 10kiops sbs low-latency migration
 dates:
-  validation: 2025-01-03
-  posted: 2025-01-03
+  validation: 2025-01-07
+  posted: 2025-01-07
 categories:
   - storage
 ---
 
+This page explains why you should migrate from the Instance API to the Block Storage API to create and manage block volumes and snapshots.
+
+<Message type="important">
+  The information displayed on this page **only applies to Instance users with block volumes**. It **does not apply to Kapsule users with block persistent volumes**.
+</Message>
+
 ## Transitioning from the Instance API to the Block Storage API for volume and snapshot management
 
-Scaleway is transitioning the management of all Block Storage legacy volumes and snapshots from the [Instance API](https://www.scaleway.com/en/developers/api/instance/) to the [Block Storage API](https://www.scaleway.com/en/developers/api/block/). All Block Storage volumes and snapshots created via the [Scaleway console](https://console.scaleway.com) will no longer be available from the [Compute section](https://console.scaleway.com/instance/) but from the [Storage section](https://console.scaleway.com/block-storage).
+Scaleway is transitioning the management of all Block Storage volumes and snapshots from the [Instance API](https://www.scaleway.com/en/developers/api/instance/) to the [Block Storage API](https://www.scaleway.com/en/developers/api/block/). All Block Storage volumes and snapshots created via the [Scaleway console](https://console.scaleway.com) will no longer be available from the [Compute section](https://console.scaleway.com/instance/) but from the [Storage section](https://console.scaleway.com/block-storage).
 
-This change streamlines how storage resources are managed by consolidating them under the Block Storage API, providing enhanced management features and clearer storage class distinctions. If you have created volumes and snapshots via the Instance API, we **strongly recommend transitioning to the Block Storage API** to align with the latest management practices.
+This change streamlines how storage resources are managed by consolidating them under the Block Storage API, providing enhanced management features and clearer storage class distinctions.
 
 Local volumes will remain exclusively supported by the Instance API.
 
+## What is required from you in the context of the migration?
+
+If you have created volumes and snapshots via the Instance API, you **must transition to the Block Storage API** to align with the latest management practices.
+
+This entails [migrating your existing volumes and snapshots to the Block Storage API](/compute/instances/how-to/migrate-volumes-snapshots-to-sbs/), and **switching to using only the Block Storage API for Block Storage volumes and snapshots creation and management**.
+
+<Message type="important">
+  Unified volume creation and management will no longer be available via the Block Storage API and will no longer be supported by the Instance API at the end of the migration. For this reason, it is also necessary to convert your existing unified volumes and snapshots to either local or block volumes.
+</Message>
+
+## What will happen at the end of the migration?
+
+From **April 30th 2025, block volumes and snapshots will no longer be available for creation/management through the Instance API**.
+
+From **June 2nd, 2025, all block volumes and snapshots that you have not migrated manually will be automatically switched behind the Block Storage API**.
+
+What's more, creating and managing block volumes and snapshots through the Instance API will no longer be possible. The Instance API will only allow you to create and manage local volumes and snapshots.
+
+Creating and managing block volumes and snapshots will **only be available via the Block Storage API**.
+
 ## Differences between the Instance API and the Block Storage API
 
-The key differences between the Instance API and the Block Storage API lie in the storage classes they manage, rather than just the APIs themselves. This distinction influences the underlying hardware and performance characteristics of the volumes.
+The key differences between the Instance API and the Block Storage API lie in the storage classes they manage, rather than just the APIs themselves. The [Block Storage API](https://www.scaleway.com/en/developers/api/block/) is the only API to use to create and manage all types of volumes, including high performance ones.
 
 ### Storage classes
 
@@ -62,11 +88,11 @@ By transitioning to the Block Storage API, you align with Scaleway's consolidate
 
 ## Impact on volume names in virtual machines
 
-When transitioning to the Block Storage API, you may notice changes in how volumes are identified in your virtual machines (VMs). For more details on how devices are named and identified, please refer to [this documentation](/compute/instances/reference-content/identify-devices/).
+When transitioning to the Block Storage API, you may notice changes in how volumes are identified in your virtual machines (VMs). For more details on how devices are named and identified, refer to [this documentation](/compute/instances/reference-content/identify-devices/).
 
-## How to transition
+## How to transition?
 
-For a step-by-step guide to transitioning your Block Storage legacy volumes to the Block Storage API, refer to [our migration documentation](/compute/instances/how-to/migrate-volumes-snapshots-to-sbs/).
+For a step-by-step guide to transitioning your block volumes and snapshots from the Instance API to the Block Storage API, refer to [our migration documentation](/compute/instances/how-to/migrate-volumes-snapshots-to-sbs/).
 
 ---