diff --git a/pages/block-storage/quickstart.mdx b/pages/block-storage/quickstart.mdx index 3e0fc4b9c1..0389ea8fb4 100644 --- a/pages/block-storage/quickstart.mdx +++ b/pages/block-storage/quickstart.mdx @@ -41,7 +41,7 @@ Discover the Block Storage interface on the Scaleway console. - Define a volume size. - The volume size must be at least 5GB. + The volume size must be at least 5 GB. - Select an Instance from the drop-down to attach your volume. This step is optional. - Check the estimated cost. diff --git a/pages/cockpit/faq.mdx b/pages/cockpit/faq.mdx index 7b4391c738..362723aec5 100644 --- a/pages/cockpit/faq.mdx +++ b/pages/cockpit/faq.mdx @@ -99,7 +99,7 @@ If you delete your data source or reduce its retention period below the default ## See custom retention pricing examples ### For 10 days of retention - If you ingest an average of **2GB of logs daily** and increase retention to **10 days**. Retention is free for the first **7 days**, so you are only charged for the extra **3 days**: + If you ingest an average of **2 GB of logs daily** and increase retention to **10 days**. Retention is free for the first **7 days**, so you are only charged for the extra **3 days**: **Monthly estimated cost:** `retention_cost` = 2 GB x (10 - 7) x 0.002€ x 30 days = 0.36€/month diff --git a/pages/data-lab/how-to/create-data-lab.mdx b/pages/data-lab/how-to/create-data-lab.mdx index 05ad18f9f7..335efadc4d 100644 --- a/pages/data-lab/how-to/create-data-lab.mdx +++ b/pages/data-lab/how-to/create-data-lab.mdx @@ -36,4 +36,4 @@ Data Lab for Apache Spark™ is a product designed to assist data scientists and - Optionally, add a description and/or tags for your Data Lab. - Verify the estimated cost. -4. Click **Create Data Lab cluster** to finish. You are directed to the Data Lab cluster overview page. +4. Click **Create Data Lab cluster** to finish. You are directed to the Data Lab cluster overview page. \ No newline at end of file diff --git a/pages/dedibox-rpn/reference-content/private-networks-overview.mdx b/pages/dedibox-rpn/reference-content/private-networks-overview.mdx index 15f0519577..b7a58093bd 100644 --- a/pages/dedibox-rpn/reference-content/private-networks-overview.mdx +++ b/pages/dedibox-rpn/reference-content/private-networks-overview.mdx @@ -63,4 +63,4 @@ For example, a Dedibox server could serve as a load balancer, routing traffic vi ### Conclusion -Scaleway provides a range of options for secure networking between Dedibox servers, Scaleway Instances, or both. Explore our [documentation](/instances/how-to/use-private-networks/) to learn more about Dedibox RPNs, Scaleway Private Networks, and VPN solutions. +Scaleway provides a range of options for secure networking between Dedibox servers, Scaleway Instances, or both. Explore our [documentation](/instances/how-to/use-private-networks/) to learn more about Dedibox RPNs, Scaleway Private Networks, and VPN solutions. \ No newline at end of file diff --git a/pages/dedibox-scaleway/how-to/reinstall-dedibox.mdx b/pages/dedibox-scaleway/how-to/reinstall-dedibox.mdx index d63b192ecf..ea7d151e9f 100644 --- a/pages/dedibox-scaleway/how-to/reinstall-dedibox.mdx +++ b/pages/dedibox-scaleway/how-to/reinstall-dedibox.mdx @@ -54,6 +54,4 @@ You can reinstall the operating system running on your Dedibox at any time. This Depending on the OS, the installation can take several minutes to complete. Certain operating systems may require additional reboots for completion. We recommend waiting 45 to 60 minutes before you connect to your server. - - - + \ No newline at end of file diff --git a/pages/dedibox/how-to/use-dedibackup-ftp-backup.mdx b/pages/dedibox/how-to/use-dedibackup-ftp-backup.mdx index 3f025dd53b..4d36f7d12f 100644 --- a/pages/dedibox/how-to/use-dedibackup-ftp-backup.mdx +++ b/pages/dedibox/how-to/use-dedibackup-ftp-backup.mdx @@ -153,5 +153,4 @@ curl -T "path_to_your_file.7z" -u "sd-XXXXX:your_password" ftp://dedibackup-dc3. ``` Replace `dedibackup-dc3` with the actual backup location (`-dc2`, `-dc3`, etc.), as specified in your Dedibox console. - - + \ No newline at end of file diff --git a/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx b/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx index 8448034f0b..35372d7d07 100644 --- a/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx +++ b/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx @@ -68,5 +68,4 @@ In the example below, they are O,065kgCo2e/kwh and 1,16, respectively. Consideri UsageImpact = (0,600 x 0,065) * 100 * 0,6 = 2,34 kgCo2e ``` -In the example, the usage impact of a 600 GB usage for 100 hours is 2,34 kgCo2e. - +In the example, the usage impact of a 600 GB usage for 100 hours is 2,34 kgCo2e. \ No newline at end of file diff --git a/pages/environmental-footprint/additional-content/object-storage-env-footprint.mdx b/pages/environmental-footprint/additional-content/object-storage-env-footprint.mdx index aa6fa9d4e4..8e86525407 100644 --- a/pages/environmental-footprint/additional-content/object-storage-env-footprint.mdx +++ b/pages/environmental-footprint/additional-content/object-storage-env-footprint.mdx @@ -71,5 +71,4 @@ In the example below, the energy mix is O,065kgCo2e/kwh and the PUE is 1.16. Con UsageImpact = 0.600 * 100 * 1.16 * 0.065v* 0.19 = 0.74 kgCo2e ``` -In the example, the usage impact of a 100 GB usage for 100 hours is 0.74 kgCo2e. - +In the example, the usage impact of a 100 GB usage for 100 hours is 0.74 kgCo2e. \ No newline at end of file diff --git a/pages/gpu/reference-content/choosing-gpu-instance-type.mdx b/pages/gpu/reference-content/choosing-gpu-instance-type.mdx index e173a1695e..055fa26550 100644 --- a/pages/gpu/reference-content/choosing-gpu-instance-type.mdx +++ b/pages/gpu/reference-content/choosing-gpu-instance-type.mdx @@ -123,7 +123,7 @@ Remember that there is no one-size-fits-all answer, and the right GPU Instance t | CPU Type | Dual Intel® Xeon® Platinum 8480C Processors (3.8 GHz) | Dual Intel® Xeon® Platinum 8480C Processors (3.8 GHz) | | Total CPU cores | 224 cores (total cluster) | 14,224 cores (total cluster) | | RAM | 4 TB (total cluster) | 254 TB (total cluster) | -| Storage | 64TB of a3i DDN low latency storage | 1.8 PB of a3i DDN low latency storage | +| Storage | 64 TB of a3i DDN low latency storage | 1.8 PB of a3i DDN low latency storage | | [MIG compatibility](/gpu/how-to/use-nvidia-mig-technology/) | Yes | Yes | | Inter-GPU bandwidth | Infiniband 400 Gb/s | Infiniband 400 Gb/s | diff --git a/pages/instances/api-cli/snapshot-import-export-feature.mdx b/pages/instances/api-cli/snapshot-import-export-feature.mdx index 7083bafb81..db38214c5b 100644 --- a/pages/instances/api-cli/snapshot-import-export-feature.mdx +++ b/pages/instances/api-cli/snapshot-import-export-feature.mdx @@ -168,6 +168,4 @@ These features are: The API might raise other errors if it cannot find the provided object, if the object is not a valid QCOW2 image, if the volume is bigger than one terabyte, etc. - - - + \ No newline at end of file diff --git a/pages/kubernetes/how-to/deploy-image-from-container-registry.mdx b/pages/kubernetes/how-to/deploy-image-from-container-registry.mdx index 069454f94a..86ef08ae9a 100644 --- a/pages/kubernetes/how-to/deploy-image-from-container-registry.mdx +++ b/pages/kubernetes/how-to/deploy-image-from-container-registry.mdx @@ -170,6 +170,4 @@ To deploy the previously created container image in a Kapsule cluster, you need As you can see in the output above, the image has been pulled successfully from the registry and two replicas of it are running on the Kapsule cluster. -For more information how to use your Container Registry with Kubernetes, refer to the [official documentation](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/). - - +For more information how to use your Container Registry with Kubernetes, refer to the [official documentation](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/). \ No newline at end of file diff --git a/tutorials/ceph-cluster/index.mdx b/tutorials/ceph-cluster/index.mdx index 9874adbc69..c2ac1bfb1f 100644 --- a/tutorials/ceph-cluster/index.mdx +++ b/tutorials/ceph-cluster/index.mdx @@ -22,7 +22,7 @@ This tutorial guides you through deploying a three-node Ceph cluster with a RADO - A Dedibox account logged into the [console](https://console.online.net) - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - 3 Dedibox servers (Ceph nodes) running Ubuntu 24.04 LTS, each with: - - At least 8GB RAM, 4 CPU cores, and one unused data disk (e.g., /dev/sdb) for OSDs. + - At least 8 GB RAM, 4 CPU cores, and one unused data disk (e.g., /dev/sdb) for OSDs. - Network connectivity between nodes and the admin machine. - An admin machine (Ubuntu 24.04 LTS recommended) with SSH access to Ceph nodes. diff --git a/tutorials/get-started-kubernetes-storage/index.mdx b/tutorials/get-started-kubernetes-storage/index.mdx index b146e75a96..07b8882594 100644 --- a/tutorials/get-started-kubernetes-storage/index.mdx +++ b/tutorials/get-started-kubernetes-storage/index.mdx @@ -144,7 +144,7 @@ Both Deployments and StatefulSets manage the deployment and scaling of a set of storage: 1Gi ``` - Essentially, we are creating a **StatefulSet** object, with **5 replica Pods**, running a lightweight container called **busybox** that will just sleep in the background for an hour. The StatefulSet will create a **PersistentVolumeClaim** for each Pod, creating a 1GB Scaleway **Block Storage volume** for each Pod, mounted at **/data**. For a full explanation of the various fields in the yaml manifest, see below: + Essentially, we are creating a **StatefulSet** object, with **5 replica Pods**, running a lightweight container called **busybox** that will just sleep in the background for an hour. The StatefulSet will create a **PersistentVolumeClaim** for each Pod, creating a 1 GB Scaleway **Block Storage volume** for each Pod, mounted at **/data**. For a full explanation of the various fields in the yaml manifest, see below: - **apiVersion** specifies which version of the Kubernetes API to use to create the object - **kind** specifies the kind of object defined in this YAML file, here a StatefulSet @@ -243,4 +243,4 @@ Try creating [snapshots](/block-storage/how-to/create-a-snapshot/) for your volu You can make snapshots by creating a manifest for a **VolumeSnapshot** object and applying it with kubectl. Refer to the [official Kubernetes documentation](https://kubernetes.io/docs/concepts/storage/volume-snapshots/) for help with this. You can then check the creation of the snapshot in the Storage > Block Storage > Snapshots section of the console. -It is also possible to create volumes from existing snapshots, again full details are available in the [official Kubernetes documentation](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#volume-snapshot-and-restore-volume-from-snapshot-support). +It is also possible to create volumes from existing snapshots, again full details are available in the [official Kubernetes documentation](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#volume-snapshot-and-restore-volume-from-snapshot-support). \ No newline at end of file diff --git a/tutorials/plausible-analytics-ubuntu/index.mdx b/tutorials/plausible-analytics-ubuntu/index.mdx index f8bf8fba03..2dfa276d19 100644 --- a/tutorials/plausible-analytics-ubuntu/index.mdx +++ b/tutorials/plausible-analytics-ubuntu/index.mdx @@ -32,7 +32,7 @@ This tool significantly contributes to the enhancement of site performance, with - An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) - An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Jammy Jellyfish (22.04 LTS) - A CPU that supports SSE 4.2 or NEON instruction sets (required for ClickHouse) -- At least 2GB of RAM for stable performance +- At least 2 GB of RAM for stable performance 1. Log into your Instance using SSH: ``` @@ -86,5 +86,4 @@ This tool significantly contributes to the enhancement of site performance, with docker-compose up -d ``` -For more information about Plausible, refer to the [official Plausible documentation](https://plausible.io/docs). - +For more information about Plausible, refer to the [official Plausible documentation](https://plausible.io/docs). \ No newline at end of file diff --git a/tutorials/run-manage-linux-vm-on-apple-silicon-tart/index.mdx b/tutorials/run-manage-linux-vm-on-apple-silicon-tart/index.mdx index a6b66ded9f..e2abcef8f5 100644 --- a/tutorials/run-manage-linux-vm-on-apple-silicon-tart/index.mdx +++ b/tutorials/run-manage-linux-vm-on-apple-silicon-tart/index.mdx @@ -72,7 +72,7 @@ Currently, Tart supports the following Linux images: * Debian: `ghcr.io/cirruslabs/debian:latest` * Fedora: `ghcr.io/cirruslabs/fedora:latest` -1. Clone the Ubuntu image and resize its disk size to 50GB using the following commands: +1. Clone the Ubuntu image and resize its disk size to 50 GB using the following commands: ```bash tart clone ghcr.io/cirruslabs/ubuntu:latest ubuntu tart set ubuntu --disk-size 50 diff --git a/tutorials/s3cmd/index.mdx b/tutorials/s3cmd/index.mdx index 87d3f18620..210fc4b149 100644 --- a/tutorials/s3cmd/index.mdx +++ b/tutorials/s3cmd/index.mdx @@ -165,7 +165,7 @@ photo1.jpg -> s3://mynewbucket/photo1.jpg [2 of 2] We are currently working to correct this issue. - For large files (>5GB), `s3cmd` supports multipart uploads, which Scaleway’s Object Storage handles with a limit of 1000 chunks. Adjust settings like `--multipart-chunk-size-mb` if needed. + For large files (>5 GB), `s3cmd` supports multipart uploads, which Scaleway’s Object Storage handles with a limit of 1000 chunks. Adjust settings like `--multipart-chunk-size-mb` if needed. ### Listing objects inside a bucket diff --git a/tutorials/setup-minecraft/index.mdx b/tutorials/setup-minecraft/index.mdx index 22cdca174a..de1fbf2399 100644 --- a/tutorials/setup-minecraft/index.mdx +++ b/tutorials/setup-minecraft/index.mdx @@ -61,7 +61,7 @@ The Minecraft server is a Java application and runs perfectly on [Scaleway Insta Deploying your own Minecraft server can be done in a few easy steps on a [Scaleway Development Instance](/instances/reference-content/development/). In case you do not have an Instance yet, start by [deploying your first Instance](/instances/how-to/create-an-instance/). - We recommend you follow this tutorial using a [General Purpose Instance](/instances/reference-content/general-purpose/) with at least 8GB of RAM. + We recommend you follow this tutorial using a [General Purpose Instance](/instances/reference-content/general-purpose/) with at least 8 GB of RAM. 1. Connect to your Instance using [SSH](/instances/how-to/connect-to-instance/).