docs(bls): fix

Author: nerda-codes

faq/blockstorage.mdx

@@ -5,7 +5,7 @@ meta:
 content:
   h1: Block Storage
 dates:
-  validation: 2024-06-14
+  validation: 2025-01-07
 category: storage
 productIcon: BlockStorageProductIcon
 ---
@@ -65,9 +65,9 @@ However, you can use the snapshot export/import feature as a temporary solution
       While this approach allows you to transition to a Block Storage Low Latency volume, it is only a workaround.
     </Message>
 
-1. [Export a snapshot of your Block Storage legacy volume](/compute/instances/api-cli/snapshot-import-export-feature/#exporting-snapshots).
+1. [Export a snapshot of your Block Storage volume](/compute/instances/api-cli/snapshot-import-export-feature/#exporting-snapshots).
 2. [Import the snapshot into a new Low Latency volume](/compute/instances/api-cli/snapshot-import-export-feature/#importing-snapshots).
 
-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.
+Find out how to [migrate your Block Storage volumes and snapshots](/compute/instances/how-to/migrate-volumes-snapshots-to-sbs/) from the Instance API to the Block Storage API.
 
 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.

macros/storage/block-storage-migration.mdx

@@ -5,5 +5,5 @@ macro: block-storage-migration
 <Message type="important">
  - 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.
+ - Find out how to [migrate your Block Storage volumes and snapshots](/compute/instances/how-to/migrate-volumes-snapshots-to-sbs/) from the Instance API to the Block Storage API.
 </Message>

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

@@ -307,7 +307,7 @@ An output similar to the following should display:
     13307e4a-c075-4421-b9b5-436732a1c739  vol-admiring-noether          sbs_5k   25 GB
     ```
 
-    Note that the `TYPE` field displays `sbs-15k` or `sbs_5k`, meaning our volumes are managed by the Block Storage API.
+    Note that the `TYPE` field displays `sbs_15k` or `sbs_5k`, meaning our volumes are managed by the Block Storage API.
 
 ## Identifying the API managing snapshots with the CLI
 

storage/block/reference-content/advantages-migrating-to-sbs.mdx

@@ -13,10 +13,10 @@ 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.
+This page explains why **Instance users** 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**.
+  The information displayed on this page **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
@@ -88,7 +88,7 @@ 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, 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 [our documentation on identifying devices on a Scaleway Instance](/compute/instances/reference-content/identify-devices/).
 
 ## How to transition?