fix(gen): rename local storage

bene2k1 · bene2k1 · commit 1487b216e741 · 2025-02-27T16:51:22.000+01:00
diff --git a/faq/billing.mdx b/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/).
diff --git a/faq/blockstorage.mdx b/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)                                                                                         |
diff --git a/pages/block-storage/quickstart.mdx b/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.
 
diff --git a/pages/components/docs.mdx b/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:
diff --git a/pages/gpu/how-to/use-scratch-storage-h100-instances.mdx b/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.
 
diff --git a/pages/instances/api-cli/migrating-instances.mdx b/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:
diff --git a/pages/instances/how-to/create-an-instance.mdx b/pages/instances/how-to/create-an-instance.mdx
@@ -181,7 +181,7 @@ Select a tab below for instructions on how to create an Instance via either our
         | commercial-type | The commercial Instance type to create  (string)    | Any valid ID of a Scaleway commercial Instance type, e.g. `"GP1-S"`, `"PRO2-M"`. Use the [List Instance Types](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types) endpoint to get a list of all valid Instance types and their IDs.   |
         | image           | The image to install on the Instance, e.g. a particular OS (string) | Any valid Scaleway image label, e.g. `ubuntu_noble` which is the label for the Ubuntu 24.04 Noble Numbat image. |
         | enable_ipv6     | Whether to enable IPv6 on the Instance (boolean)    | `true` or `false`                   |
-        | volumes         | An object that specifies the storage volumes to attach to the Instance. Must respect the volume constraints of the `commercial_type` (i.e. for each type of Instance, a minimum amount of storage is required, and there is also a maximum that cannot be exceeded. Some Instance types support only Block Storage (`b_ssd`), others also support Local Storage (`l_ssd`) ). These constraints are available at the [List Instance Types](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types) endpoint, via the `volume_constraints` parameter for each type listed in the response | A (dictionary) object with a minimum of one key (`"0"`) whose value is another object containing the parameters `"name"` (a name for the volume), `"size"` (the size for the volume, in bytes), and `"volume_type"` (`"l_ssd"` or `"b_ssd"`). Additional keys for additional volumes should increment by 1 each time (the second volume would have a key of `1`.) Further parameters are available, and it is possible to attach existing volumes rather than creating a new one, or create a volume from a snapshot. For full details see [here](https://www.scaleway.com/en/developers/api/instance/#path-volumes).  |
+        | volumes         | An object that specifies the storage volumes to attach to the Instance. Must respect the volume constraints of the `commercial_type` (i.e. for each type of Instance, a minimum amount of storage is required, and there is also a maximum that cannot be exceeded. Some Instance types support only Block Storage (`b_ssd`), others also support Local NVMe storage (`l_ssd`) ). These constraints are available at the [List Instance Types](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types) endpoint, via the `volume_constraints` parameter for each type listed in the response | A (dictionary) object with a minimum of one key (`"0"`) whose value is another object containing the parameters `"name"` (a name for the volume), `"size"` (the size for the volume, in bytes), and `"volume_type"` (`"l_ssd"` or `"b_ssd"`). Additional keys for additional volumes should increment by 1 each time (the second volume would have a key of `1`.) Further parameters are available, and it is possible to attach existing volumes rather than creating a new one, or create a volume from a snapshot. For full details see [here](https://www.scaleway.com/en/developers/api/instance/#path-volumes).  |
 
     4. Use the following curl command, replacing the payload with the one you specified in step 2, to create your Instance.
 
diff --git a/pages/instances/how-to/create-image-from-snapshot.mdx b/pages/instances/how-to/create-image-from-snapshot.mdx
@@ -51,7 +51,7 @@ scw instance image create snapshot-id="$SCW_VOLUME_ID_1" additional-volumes.0.id
 
 <Message type="note">
   Supported volume IDs include:
-  - Local Storage volumes (`l_ssd`)
+  - Local NVMe storage volumes (`l_ssd`)
   - Block Storage Low Latency volumes (`sbs`)
   - Block Storage legacy (`b_ssd`) volumes (deprecated).
 </Message>
@@ -82,7 +82,7 @@ curl --location "https://api.scaleway.com/instance/v1/zones/$SCW_AVAILABILITY_ZO
 
 <Message type="tip">
   Supported volume IDs include:
-  - Local Storage volumes (`l_ssd`)
+  - Local NVMe storage volumes (`l_ssd`)
   - Block Storage Low Latency volumes (`sbs`)
   - Block Storage legacy (`b_ssd`) volumes (deprecated).
 </Message>
diff --git a/pages/instances/how-to/use-standby-mode.mdx b/pages/instances/how-to/use-standby-mode.mdx
@@ -13,7 +13,7 @@ categories:
   - compute
 ---
 
-[Standby mode](/instances/concepts/#standby-mode) temporarily stops an Instance. The Instance remains allocated to your account and all data remains on the Local Storage of the Instance.
+[Standby mode](/instances/concepts/#standby-mode) temporarily stops an Instance. The Instance remains allocated to your account and all data remains on the Local NVMe storage of the Instance.
 
 <Macro id="requirements" />
 
diff --git a/pages/instances/reference-content/choosing-instance-type.mdx b/pages/instances/reference-content/choosing-instance-type.mdx
@@ -55,7 +55,7 @@ Use this table to help identify the right Instance range for your use case and c
 | **Instance range**    | [Learning](/instances/reference-content/learning/)     | [Cost-Optimized](/instances/reference-content/cost-optimized/)                                   | [Production-Optimized](/instances/reference-content/production-optimized/)                                                 | [Workload-Optimized](/instances/reference-content/workload-optimized/)                                                                                                                                        |
 |-----------------------|----------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | **Use cases**         | Discovering the Scaleway ecosystem<br />Hosting personal projects | Scaling your development and testing environment<br />Hosting CI/CD runners and containerized worker nodes | Hosting production workloads and business-critical applications<br />Ensuring predictable CPU performance in the face of high traffic | Hosting high-demanding analysis, in-memory calculation, big-data processing, high-performance or cache databases<br />Designed for high-performance web-serving, video encoding, machine learning, batch processing, CI/CD |
-| **Supported storage** | Resilient Block Storage or Local Storage                       | Resilient Block Storage or Local Storage, OR  Resilient Block Storage only (depending on Instance type) | Resilient Block Storage                                                                                                            | Resilient Block Storage                                                                                                                                                                                                 |
+| **Supported storage** | Resilient Block Storage or Local NVMe storage                       | Resilient Block Storage or Local NVMe storage, OR  Resilient Block Storage only (depending on Instance type) | Resilient Block Storage                                                                                                            | Resilient Block Storage                                                                                                                                                                                                 |
 | **vCPU**              | 1 core                                                         | From 1 to 32 cores                                                                                       | From 2 to 96 cores                                                                                                                 | From 2 to 64 cores                                                                                                                                                                                                      |
 | **Shared/Dedicated**  | Shared vCPU                                                    | Shared vCPU                                                                                              | Dedicated vCPU                                                                                                                     | Dedicated vCPU                                                                                                                                                                                                          |
 | **RAM**               | 1 GiB                                                          | From 2 GiB to 128 GiB                                                                                    | From 8 GiB to 384 GiB                                                                                                              | From 4 GiB to 512 GiB                                                                                                                                                                                                   |
diff --git a/pages/kubernetes/concepts.mdx b/pages/kubernetes/concepts.mdx
@@ -147,7 +147,7 @@ The system volume is a read-only volume that stores essential files for the Kube
 
 Depending on the type of node selected, we provide one or two types of volume.
 
-  - **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:** your system is remotely stored on a centralized and resilient cluster.
 
 As a general guideline, your system volume disk should have a capacity of at least 20 GB to ensure enough space to store the necessary system files and configurations.
diff --git a/pages/managed-databases-for-postgresql-and-mysql/concepts.mdx b/pages/managed-databases-for-postgresql-and-mysql/concepts.mdx
@@ -92,12 +92,12 @@ The HA standby node is linked to the main node, using synchronous replication. S
   HA standby nodes are not accessible to users unless the main node becomes unavailable and the standby takes over. If you wish to run queries on a read-only node, you can use [Read Replicas](/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica/).
 </Message>
 
-## Local Storage
+## Local NVMe storage
 
 With this type, your storage is fixed and tied to your compute resource.
 
 <Message type="note">
-  Local Storage is only available with first-generation node types.
+  Local NVMe storage is only available with first-generation node types.
 </Message>
 
 ## Logs
@@ -122,7 +122,7 @@ A database type that uses the relational model, which means that it stores and p
 
 ## Volume type
 
-This is the type of storage used on your Database Instances. Three types are available: [Local Storage](#local-storage), [Block Storage Legacy](#block-storage-legacy), and [Block Storage](#block-storage).
+This is the type of storage used on your Database Instances. Three types are available: [Local NVMe storage](#local-storage), [Block Storage Legacy](#block-storage-legacy), and [Block Storage](#block-storage).
 
 <Message type="note">
   New Block Storage volumes are only available with new-generation node types and only in the PAR and AMS regions.
diff --git a/pages/organizations-and-projects/additional-content/organization-quotas.mdx b/pages/organizations-and-projects/additional-content/organization-quotas.mdx
