fix(ins): update wording

Author: bene2k1

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/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/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/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/)