feat(ins): rename local storage to "Local NVMe storage"

faq/billing.mdx

@@ -23,7 +23,7 @@ Your monthly invoice is calculated at the end of each month and based on your ho
 For example:
 The Stardust1-s indicated at €0,0025 excl/hour can be split up as follows:
 - €0.00198/hour for the IP
-- €0.0004/hour for the 10 GB of Local Storage
+- €0.0004/hour for the 10 GB of Local NVMe storage
 - €0.00012/hour for the instance
 
 For more information, refer to our dedicated [pricing page](https://www.scaleway.com/en/pricing/).

faq/blockstorage.mdx

@@ -1,7 +1,7 @@
 ---
 meta:
   title: Block Storage FAQ
-  description: Explore Scaleway Block Storage with our comprehensive FAQ covering performance, persistence, and more. Learn how Block Storage compares to Local Storage and its compatibility with Scaleway resources.
+  description: Explore Scaleway Block Storage with our comprehensive FAQ covering performance, persistence, and more. Learn how Block Storage compares to Local NVMe storage and its compatibility with Scaleway resources.
 content:
   h1: Block Storage
 dates:
@@ -10,13 +10,13 @@ category: storage
 productIcon: BlockStorageProductIcon
 ---
 
-## Why should I use Block Storage instead of Local Storage?
+## Why should I use Block Storage instead of Local NVMe storage?
 
-The size of Local Storage depends on your Instance type. With today's configurations, the maximum Local Storage available is 600 GB.
+The size of Local NVMe storage depends on your Instance type. With today's configurations, the maximum Local NVMe storage available is 600 GB.
 
 Block Storage allows you to create bigger volumes and those volumes are persistent which means that they can live without being attached to an Instance.
 
-|                    |         **Block Storage**         |           **Local Storage**                                                                                    |
+|                    |         **Block Storage**         |           **Local NVMe storage**                                                                                    |
 |--------------------|:---------------------------------:|:--------------------------------------------------------------------------------------------------------------:|
 | **Availability**   | High                              | HV dependant (needs physical intervention to retrieve storage and data if HV dies)                             |
 | **Redundancy**     | High (replica 3)                  | Low (RAID 5 - 5 disks)                                                                                         |

faq/instances.mdx

@@ -172,7 +172,7 @@ You can change the storage type and flexible IP after the Instance creation, whi
 
 | Product           | All regions*           | PAR3              |
 |-------------------|------------------------|-------------------|
-| Local Storage     | €0.000044 GB/hour      | Not available     |
+| Local NVMe storage | €0.000044 GB/hour      | Not available     |
 | Local snapshot    | €0.000044 GB/hour      | Not available     |
 | Block Storage     | €0.000118 GB/hour      | €0.000177 GB/hour |
 | Block snapshot    | €0.000044 GB/hour      | €0.000066 GB/hour |
@@ -203,10 +203,10 @@ Dedicated Resources give you a more stable experience for compute-demanding work
 ### Which options are available to power off my Instance?
 
 You can choose between four options when powering off your Instance:
-* **Hard reboot**: Your Instance performs an electrical reboot and its data is kept on the Local Storage. We recommend always rebooting your Instance from the OS to avoid data corruption.
+* **Hard reboot**: Your Instance performs an electrical reboot and its data is kept on the Local NVMe storage. We recommend always rebooting your Instance from the OS to avoid data corruption.
 * **Power off**: All local volume data is transferred to a volume store, and your physical node is released back to the pool of available machines. The process duration depends on the amount of data archived.
 * **Terminate**: Your Instance and its volumes are permanently deleted, but the attached flexible IP is preserved.
-* **Standby**: Your Instance is stopped, but its data remains in the Local Storage. The Instance is still allocated to your account and can be restarted anytime.
+* **Standby**: Your Instance is stopped, but its data remains in the Local NVMe storage. The Instance is still allocated to your account and can be restarted anytime.
 
 <Message type="important">
   The **standby mode** is charged as a running Instance. To avoid being billed for an unused Instance, power it off and ensure no IPs or allocated storage are left in use.

faq/kubernetes.mdx

@@ -83,7 +83,7 @@ For more information, refer to the Kubernetes Kapsule product documentation on [
 To ensure sufficient space for storing default system files and configurations, we recommend a system volume disk capacity of at least 20 GB. While this amount is generally sufficient for small workloads, it is advisable to have a capacity of 100 GB to comfortably store images and system logs in many cases.
 If you run out of space on your immutable system volume disk, you can create another pool and use the **Advanced Options** button to set your desired system volume type and size.
 Depending on the type of node selected for your pool, one or two types of volume are available:
-* **Local Storage**: Your system is stored locally on the hypervisor of your node.
+* **Local NVMe storage**: Your system is stored locally on the hypervisor of your node.
 * **Block Storage**: A remote storage option where your system is stored on a centralized and resilient cluster.
 
 ### What is the service 'kapsule-agent' running on my nodes?

pages/block-storage/quickstart.mdx

@@ -14,7 +14,7 @@ categories:
   - storage
 ---
 
-Scaleway [Block Storage](/block-storage/concepts/#block-device) provides network-attached storage that can be plugged in and out of [Instances](/instances/concepts/#instance) like a virtual hard-drive. Block Storage devices are independent of the Local Storage of Instances, and the fact that they are accessed over a network connection makes it easy to move them between Instances in the same [Availability Zone](/instances/concepts/#availability-zone).
+Scaleway [Block Storage](/block-storage/concepts/#block-device) provides network-attached storage that can be plugged in and out of [Instances](/instances/concepts/#instance) like a virtual hard-drive. Block Storage devices are independent of the Local NVMe storage of Instances, and the fact that they are accessed over a network connection makes it easy to move them between Instances in the same [Availability Zone](/instances/concepts/#availability-zone).
 
 From the user's point of view, once [mounted](/block-storage/api-cli/managing-a-volume/#mounting-and-using-a-block-storage-volume), the block device behaves like a regular disk.
 

pages/block-storage/reference-content/differences-between-5kiops-volumes.mdx

@@ -13,11 +13,11 @@ categories:
   - storage
 ---
 
-When creating volumes from the Scaleway console, you are prompted to choose between [Block Storage Low Latency](/block-storage/) volumes, [block volumes (Block Storage)](/instances/concepts/#block-volumes), and [local volumes (Local Storage)](/instances/concepts/#volumes).
+When creating volumes from the Scaleway console, you are prompted to choose between [Block Storage Low Latency](/block-storage/) volumes, [block volumes (Block Storage)](/instances/concepts/#block-volumes), and [local volumes (Local NVMe storage)](/instances/concepts/#volumes).
 
 This page provides information about the differences between Block Storage and Block Storage Low Latency 5K [IOPS](/block-storage/concepts/#iops) volumes.
 
-Refer to the [dedicated documentation](/instances/concepts/#volumes) to learn about the differences between Block Storage and Local Storage volumes.
+Refer to the [dedicated documentation](/instances/concepts/#volumes) to learn about the differences between Block Storage and Local NVMe storage volumes.
 
 ## Underlying hardware
 

pages/components/docs.mdx

@@ -750,7 +750,7 @@ The above text come from a macro!
         </Message>
         - Choose an **Instance type**. Different Instance types have different prices, processing power, memory, storage options and bandwidth.
         - Add **Volumes**. Volumes are storage spaces used by your Instances.
-          - For **GP1 Instances** you can leave the default settings of a maximum local storage, or choose how much [local](/instances/concepts#local-volumes) and/or [block](/instances/concepts#block-volumes) storage you want. Your **system volume** is the volume on which your Instance will boot. The system volume can be either a local or a block volume.
+          - For **GP1 Instances** you can leave the default settings of a maximum Local NVMe storage, or choose how much [local](/instances/concepts#local-volumes) and/or [block](/instances/concepts#block-volumes) storage you want. Your **system volume** is the volume on which your Instance will boot. The system volume can be either a local or a block volume.
           - **PRO2** and **Enterprise** Instances boot directly [on block volumes](/instances/concepts/#boot-on-block). You can add several block volumes and define how much storage you want for each.
             <Message type="important">
               Please note that:

pages/gpu/how-to/create-manage-gpu-instance.mdx

@@ -35,7 +35,7 @@ When you have completed your calculations using the GPU Instance, [deletion can
     - **Availability Zone**: Choose the geographical region, represented by the Availability Zone, where your Instance will be deployed.
     - **Instance Type (GPU)**: Select the desired GPU Instance type, considering factors such as processing power, memory, storage options, and bandwidth. Refer to our guide on [choosing the right GPU Instance type](/gpu/reference-content/choosing-gpu-instance-type/) for more information.
     - **Image**: Pick an operating system image suitable for your GPU Instance. For example, select **Ubuntu Jammy GPU OS 12**, which comes with preinstalled NVIDIA drivers and an NVIDIA Docker environment. You have the flexibility to customize your working environment using Docker with our provided Docker images or your own containers.
-    - **Volumes**: Optionally, add storage volumes for your Instance. You can adjust settings such as Block and Local Storage volumes according to your requirements.
+    - **Volumes**: Optionally, add storage volumes for your Instance. You can adjust settings such as Block and Local NVMe storage volumes according to your requirements.
         <Message type="note">
           * The recommended minimum volume size for GPU OS images is 125 GB.
           * If your GPU Instance supports scratch storage, the scratch volume displays but can not be edited. [Learn more about scratch storage.](/gpu/how-to/use-scratch-storage-h100-instances/)

pages/gpu/how-to/use-gpu-with-docker.mdx

@@ -47,7 +47,7 @@ We recommend that you map volumes from your GPU Instance to your Docker containe
 
 ### How to map local volumes
 
-You can map directories from your GPU Instance's Local Storage to your Docker container, using the `-v <local_storage>:<container_mountpoint>` flag. See the example command below:
+You can map directories from your GPU Instance's Local NVMe storage to your Docker container, using the `-v <local_storage>:<container_mountpoint>` flag. See the example command below:
 
 ```bash
 docker run -it --rm -v /root/mydata/:/workspace nvidia/cuda:11.2.1-runtime-ubuntu20.04
@@ -101,7 +101,7 @@ Below is a list of the most common commands you use when dealing with Docker con
 | **docker push**   | `docker push <registry_user/docker_image>`                   | This command is used to push a local image to a remote repository.                                                                                       |
 | **docker images** | `docker images`                                              | This command is used to list all available Docker images on the local system.                                                                            |
 | **docker rm**     | `docker rm <container_id>`                                   | This command is used to remove a stopped container from the local system.                                                                                |
-| **docker rmi**    | `docker rmi <image_id>`                                      | This command is used to delete an image from the Local Storage.                                                                                          |
+| **docker rmi**    | `docker rmi <image_id>`                                      | This command is used to delete an image from the Local NVMe storage.                                                                                          |
 | docker version| `docker --version`                                           | This command is used to display information about the currently installed version of Docker.                                                             |
 
 For more information regarding the `docker run` command, refer to the [official documentation](https://docs.docker.com/engine/reference/run/).

pages/gpu/how-to/use-scratch-storage-h100-instances.mdx

@@ -13,7 +13,7 @@ categories:
   - compute
 ---
 
-Scaleway H100 and L40S GPU Instances are equipped with additional scratch storage. This form of temporary Local Storage operates differently from our regular Local Storage.
+Scaleway H100 and L40S GPU Instances are equipped with additional scratch storage. This form of temporary Local NVMe storage operates differently from our regular Local NVMe storage.
 
 Scratch storage temporarily accommodates data during computational or data processing tasks. It is commonly used for storing intermediate results, processing input data, or holding output data before that data is moved to more permanent storage.
 

pages/gpu/quickstart.mdx

@@ -27,7 +27,7 @@ In addition to this, GPU Instances have all the features of our regular Instance
     - **Availability Zone**: Choose the geographical region, represented by the Availability Zone, where your Instance will be deployed.
     - **Instance Type (GPU)**: Select the desired GPU Instance type, considering factors such as processing power, memory, storage options, and bandwidth. Refer to our guide on [choosing the right GPU Instance type](/gpu/reference-content/choosing-gpu-instance-type/) for more information.
     - **Image**: Pick an operating system image suitable for your GPU Instance. For example, select **Ubuntu Jammy GPU OS 12**, which comes with preinstalled Nvidia drivers and an Nvidia Docker environment. You can customize your working environment using Docker with our provided Docker images or your own containers.
-    - **Volumes**: Optionally, add storage volumes for your Instance. You can adjust settings such as Block and Local Storage volumes according to your requirements.
+    - **Volumes**: Optionally, add storage volumes for your Instance. You can adjust settings such as Block and Local NVMe storage volumes according to your requirements.
         <Message type="note">
           * The recommended minimum volume size for GPU OS images is 125 GB.
           * If your GPU Instance supports scratch storage, the scratch volume displays but can not be edited. [Learn more about scratch storage.](/gpu/how-to/use-scratch-storage-h100-instances/)

pages/instances/api-cli/migrating-instances.mdx

@@ -47,7 +47,7 @@ To do so, you need the Instance’s ID and a valid API key.
           You can retrieve a list of all available Instance types using the command `scw instance server-type list`.
         </Message>
         <Message type="important">
-          Ensure that Local Storage constraints are respected. For example, downgrading from a larger Instance type to a smaller one may not be possible if the smaller Instance type cannot support the existing Local Storage. Check the Scaleway documentation for specific constraints.
+          Ensure that Local NVMe storage constraints are respected. For example, downgrading from a larger Instance type to a smaller one may not be possible if the smaller Instance type cannot support the existing Local NVMe storage. Check the Scaleway documentation for specific constraints.
         </Message>
 
     3. Power on the Instance.
@@ -86,7 +86,7 @@ To do so, you need the Instance’s ID and a valid API key.
         curl -X PATCH -H "X-Auth-Token: $SCW_SECRET_KEY" -H "Content-Type: application/json" -d '{"commercial_type" : "<NEW_INSTANCE_TYPE>"}' "https://api.scaleway.com/instance/v1/zones/{zone}/servers/{server_id}"
         ```
         <Message type="important">
-            Local Storage constraints must be respected. For example, downgrading a DEV1-L Instance with 80 GB of local SSD storage to a DEV1-S Instance is not possible because the DEV1-S offer only supports a maximum of 20 GB. However, if the DEV1-L Instance is only using Block Storage (`b_ssd`) without relying on local SSD storage, the downgrade can be performed without any issues.
+            Local NVMe storage constraints must be respected. For example, downgrading a DEV1-L Instance with 80 GB of local SSD storage to a DEV1-S Instance is not possible because the DEV1-S offer only supports a maximum of 20 GB. However, if the DEV1-L Instance is only using Block Storage (`b_ssd`) without relying on local SSD storage, the downgrade can be performed without any issues.
         </Message>
 
         Output: