docs(gen): file system harmonization and general clean up (#4015)

* docs(gen): file system harmonization and general clean up

* Update containers/kubernetes/api-cli/cluster-monitoring.mdx

Co-authored-by: Rowena Jones <[email protected]>

---------

Co-authored-by: Rowena Jones <[email protected]>

Author: jcirinosclwy

ai-data/managed-inference/quickstart.mdx

@@ -38,7 +38,7 @@ Here are some of the key features of Scaleway Managed Inference:
 1. Navigate to the **AI & Data** section of the [Scaleway console](https://console.scaleway.com/), and select **Managed Inference** from the side menu to access the Managed Inference dashboard.
 2. Click **Create deployment** to launch the deployment creation wizard.
 3. Provide the necessary information:
-    - Select the desired model and the quantization to use for your deployment [from the available options](https://www.scaleway.com/en/docs/ai-data/managed-inference/reference-content/)
+    - Select the desired model and the quantization to use for your deployment [from the available options](/ai-data/managed-inference/reference-content/)
         <Message type="note">
           Some models may require acceptance of an end-user license agreement. If prompted, review the terms and conditions and accept the license accordingly.
         </Message>
@@ -83,8 +83,8 @@ Managed Inference deployments have authentication enabled by default. As such, y
 2. Choose a deployment either by clicking its name or selecting **More info** from the drop-down menu represented by the icon <Icon name="more" /> to access the deployment dashboard.
 3. Click the **Settings** tab of your deployment to display additional settings.
 4. Click **Delete deployment**.
-5. Type **DELETE** to confirm and click **Delete deployment** to delete your deployment. 
+5. Type **DELETE** to confirm and click **Delete deployment** to delete your deployment.
 
 <Message type="important">
   Deleting a deployment is a permanent action, and will erase all its associated configuration and resources.
-</Message>
+</Message>

bare-metal/elastic-metal/how-to/configure-disk-partitions.mdx

@@ -40,7 +40,7 @@ Below is an example of how to define a partitioning schema with RAID and NVMe di
 </Message>
 
 <Message type="tip">
-    Refer to the Elastic Metal API documentation for a complete overview of the expected values for filesystem types, RAID configurations, and other related parameters required for partitioning. For more details, visit the [Scaleway Elastic Metal API Documentation – Default Partitioning Schema](https://www.scaleway.com/en/developers/api/elastic-metal/#path-partitioning-schemas-get-default-partitioning-schema).
+    Refer to the Elastic Metal API documentation for a complete overview of the expected values for file system types, RAID configurations, and other related parameters required for partitioning. For more details, visit the [Scaleway Elastic Metal API Documentation – Default Partitioning Schema](https://www.scaleway.com/en/developers/api/elastic-metal/#path-partitioning-schemas-get-default-partitioning-schema).
 </Message>
 
 ```json
@@ -170,8 +170,8 @@ Below is an example of how to define a partitioning schema with RAID and NVMe di
     - If RAID is required, declare the disks and the desired RAID level. In this example, we are configuring two RAID-1 arrays, one for the boot partition and one for the root partition.
     - Devices participating in each RAID array are specified by their partition paths (e.g., `/dev/nvme0n1p3` for partition 3 of the first NVMe disk).
 
-- Filesystems:
-    - Each partition is assigned a filesystem type and a mount point.
+- File systems:
+    - Each partition is assigned a file system type and a mount point.
     - For example, the `/boot/efi` partition is formatted with `fat32`, while `/boot` and `/` are formatted with `ext4`.
 
 - ZFS (Optional):
@@ -180,7 +180,7 @@ Below is an example of how to define a partitioning schema with RAID and NVMe di
 
 ### Simple configuration (No RAID or ZFS)
 
-If you prefer a simpler configuration without RAID or ZFS, you can remove the `raids` and `zfs` sections. For example, if you only need a single disk setup with no RAID, declare just one disk with the partitions and filesystems as shown below:
+If you prefer a simpler configuration without RAID or ZFS, you can remove the `raids` and `zfs` sections. For example, if you only need a single disk setup with no RAID, declare just one disk with the partitions and file systems as shown below:
 
 ```json
 {

bare-metal/elastic-metal/how-to/kubernetes-on-riscv.mdx

@@ -17,7 +17,7 @@ categories:
 
  - A Scaleway account logged into the [console](https://console.scaleway.com)
  - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization
- - [Created a Kosmos cluster](https://www.scaleway.com/en/docs/containers/kubernetes/how-to/create-kosmos-cluster/) on which you have [configured a pool of external nodes](/containers/kubernetes/how-to/edit-kosmos-cluster/#how-to-configure-external-nodes-to-join-the-cluster)
+ - [Created a Kosmos cluster](/containers/kubernetes/how-to/create-kosmos-cluster/) on which you have [configured a pool of external nodes](/containers/kubernetes/how-to/edit-kosmos-cluster/#how-to-configure-external-nodes-to-join-the-cluster)
  - [Created an Elastic Metal RV1 server](/bare-metal/elastic-metal/how-to/create-server/)
  - [Created an API key](/identity-and-access-management/iam/how-to/create-api-keys/) with the `KubernetesExternalNodeRegister` permission set.
  - An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/)
@@ -44,4 +44,4 @@ With Scaleway Kosmos and our Elastic Metal RV1, you can follow this guide to lau
     ```
     sudo -E ./node-agent_linux_riscv64 -loglevel 0 -no-controller && sleep 10
 
-7. **Restart** your server.
+7. **Restart** your server.

compute/instances/reference-content/identify-devices.mdx

@@ -15,13 +15,13 @@ categories:
 
 An Instance is composed of a multitude of devices. Some of them can be configured, such as network interfaces and block devices, for example by attaching an SBS volume to the Instance or attaching the Instance to a Private Network.
 
-On a Linux host, devices are named by the kernel in the order they are discovered. The order in which devices are discovered is dependent on things such as the topology of the PCI hierarchy which are *not* guaranteed to be stable across poweroff/poweron/reboot actions.
+On a Linux host, devices are named by the kernel in the order they are discovered. The order in which devices are discovered is dependent on things such as the topology of the PCI hierarchy which are *not* guaranteed to be stable across power off/power on/reboot actions.
 
 This guide aims to provide tips to help you identify devices in a stable manner on a Linux host.
 
 # Identifying Instance Block Storage volumes (b_ssd)
 
-Instance Block Storage (`b_ssd`) volumes are connected to the Instance as SCSI disks. They will therefore appear as devices handled by the sd driver in the dev filesystem, i.e. as `/dev/sd{a,b,c...}` devices.
+Instance Block Storage (`b_ssd`) volumes are connected to the Instance as SCSI disks. They will therefore appear as devices handled by the sd driver in the dev file system, i.e. as `/dev/sd{a,b,c...}` devices.
 
 SCSI disks have multiple attributes, such as vendor and product/model. They also have a serial. Instance Block Storage (`b_ssd`) volumes have the vendor name `SCW`, the model/product name `b_ssd`, and a serial set to `volume-<uuid>` where `<uuid>` is the ID of the volume.
 
@@ -60,7 +60,7 @@ ID_SERIAL=0SCW_b_ssd_volume-f7a6f113-aaf6-4540-ac5a-9e18d7f61478
 ID_SERIAL_SHORT=volume-f7a6f113-aaf6-4540-ac5a-9e18d7f61478
 ```
 
-The third and fourth rules create the symlinks proper, using these attributes. This will result in the following symlinks being created:
+The third and fourth rules create the symlinks properly, using these attributes. This will result in the following symlinks being created:
 
 ```sh
 root@test-instance:~# ls -l /dev/disk/by-id/
@@ -102,7 +102,7 @@ Block Storage devices are similar to Instance Block Storage devices. They are al
 
 The only difference is the SCSI model attribute. Instead of being fixed to the value `b_ssd`, its value depends on the class of the Block Storage volume.
 
-Two Block Storage volumes classes currently exist: `bssd`, and `sbs`. Block Storage volumes migrated from Instance Block Storage (`b_ssd`) volumes have class `bssd`.
+Two Block Storage volume classes currently exist: `bssd`, and `sbs`. Block Storage volumes migrated from Instance Block Storage (`b_ssd`) volumes have class `bssd`.
 
 Block Storage volumes with class `bssd` have a SCSI model of `b_ssd`, so migrated volumes won't change characteristics. Otherwise, Block Storage volumes have a SCSI model equal to the volume's class. 
 

compute/instances/reference-content/instances-bandwidth-overview.mdx

@@ -27,7 +27,7 @@ Bandwidth impacts how your applications perform and interact with other systems.
 </Message>
 
 <Message type="tip">
-  To maximize compatibility with [Block Storage Low Latency 15k](https://www.scaleway.com/en/docs/storage/block/), select an Instance with **at least 3 GiB/s** of Block bandwidth.
+  To maximize compatibility with [Block Storage Low Latency 15k](/storage/block/), select an Instance with **at least 3 GiB/s** of Block bandwidth.
 </Message>
 
 ## COPARM Range
@@ -116,4 +116,4 @@ Bandwidth impacts how your applications perform and interact with other systems.
 |   Instance Type      |   Internet Bandwidth   |   Block Bandwidth   |
 |-----------------------|-------------------------|---------------------|
 | POP2-HN-3            | 3  Gbit/s            | 400 MiB/s       |
-| POP2-HN-10           | 10  Gbit/s           | 800 MiB/s       |
+| POP2-HN-10           | 10  Gbit/s           | 800 MiB/s       |

compute/instances/troubleshooting/fix-unreachable-focal-with-two-public-ips.mdx

@@ -43,7 +43,7 @@ From this point on, your Instance may be safely rebooted and you will no longer
 
 [Rescue mode](/compute/instances/concepts/#rescue-mode) allows you to boot your Instance into a temporary operating system, running from the Instance's RAM. Rescue mode is often used to diagnose and resolve issues such as faulty kernel configurations, networking issues, firewall configurations, and more.
 
-1. Switch the Instance's `boot-type` to `rescue` and reboot your Instance into rescue mode using the [CLI](https://www.scaleway.com/en/docs/developer-tools/scaleway-cli/quickstart/):
+1. Switch the Instance's `boot-type` to `rescue` and reboot your Instance into rescue mode using the [CLI](/developer-tools/scaleway-cli/quickstart/):
 ```
 scw instance server stop <Instance_ID>
 # Wait for the instance to be stopped.
@@ -87,16 +87,16 @@ chroot /mnt
 rm -f /etc/resolv.conf
 ln -s /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
 ```
-4. Once in the `chroot` install the modified cloud-init package
+4. Once in the `chroot` install the modified cloud-init package:
 ```
 add-apt-repository ppa:scaleway/stable
 apt -y install cloud-init
 ```
-5. Re-initialize cloud-init to fix the netplan profile
+5. Re-initialize cloud-init to fix the netplan profile:
 ```sh
 cloud-init clean && cloud-init init --local && cloud-init init
 ```
-6. Get out of the `chroot` and remove the mounts
+6. Get out of the `chroot` and remove the mounts:
 ```sh
 umount /mnt/sys /mnt/proc /mnt/dev /mnt/run /mnt
 ```
@@ -110,11 +110,11 @@ scw instance server start <Instance_ID>
 Once rebooted, your Instance will be reachable again.
 
 <Message type="important">
-   This modification will be valid for up until Ubuntu publishes a new version, i.e. cloud-init 24.3. You can use the following commands to hold the newly installed version so it does not get updated when the new version comes in.
+   This modification will be valid until Ubuntu publishes a new version, i.e. cloud-init 24.3. You can use the following commands to hold the newly installed version so it does not get updated when the new version comes in.
 </Message>
 
-8. Put a hold on the newly installed cloud-init
+8. Put a hold on the newly installed cloud-init:
 ```sh
 apt-mark hold cloud-init
 cloud-init set on hold.
-```
+```

compute/instances/troubleshooting/fix-unreachable-noble-after-reboot.mdx

@@ -19,7 +19,7 @@ Instances created after June 11th 2024 will not encounter this problem.
 
 ## Your Instance has not been rebooted
 
-You can avoid this situation by increasing the dhcpcd timeout in its configuration file
+You can avoid this situation by increasing the dhcpcd timeout in its configuration file:
 ```
 sed -i 's/timeout 5/timeout 10/' /etc/dhcpcd.conf
 
@@ -40,7 +40,7 @@ timeout 10
 
 [Rescue mode](/compute/instances/concepts/#rescue-mode) allows you to boot your Instance into a temporary operating system, running from the Instance's RAM. Rescue mode is often used to diagnose and resolve issues such as faulty kernel configurations, networking issues, firewall configurations, and more.
 
-1. Switch the Instance's `boot-type` to `rescue` and reboot your Instance into rescue mode using the [CLI](https://www.scaleway.com/en/docs/developer-tools/scaleway-cli/quickstart/):
+1. Switch the Instance's `boot-type` to `rescue` and reboot your Instance into rescue mode using the [CLI](/developer-tools/scaleway-cli/quickstart/):
     ```
     scw instance server stop <Instance_ID>
     scw instance server update <Instance_ID> boot-type=rescue
@@ -63,7 +63,7 @@ timeout 10
     ```
     mount /dev/sda1 /mnt
     ```
-3. Once mounted, use the `chroot` command to get into your Instance's root filesystem. You can then change the timeout value for dhcpcd as shown above :
+3. Once mounted, use the `chroot` command to get into your Instance's root file system. You can then change the timeout value for dhcpcd as shown above:
     ```
     chroot /mnt
     sed -i 's/timeout 5/timeout 10/' /etc/dhcpcd.conf
@@ -89,5 +89,4 @@ timeout 10
     scw instance server update <Instance_ID> boot-type=local
     scw instance server start <Instance_ID>
     ```
-    Once rebooted, your Instance will be reachable again.
-
+    Once rebooted, your Instance will be reachable again.

compute/instances/troubleshooting/reboot-from-faulty-kernel.mdx

@@ -22,7 +22,7 @@ categories:
 - Installed and configured the Scaleway [CLI](/compute/instances/api-cli/creating-managing-instances-with-cliv2) on your local computer
 
 
-1. Switch the Instance's `boot-type` to `rescue` and reboot your Instance into rescue mode using the CLI-Tools: 
+1. Switch the Instance's `boot-type` to `rescue` and reboot your Instance into rescue mode using the CLI-Tools:
     ```
     scw instance server update {Instance_ID} boot-type=rescue
     scw instance server reboot {Instance_ID}
@@ -48,7 +48,7 @@ categories:
     mount -o bind /proc /mnt/proc
     mount -o bind /dev /mnt/dev
     ```
-3. Once mounted, use the `chroot` command to get into your Instances' root filesystem. You can then change the `GRUB_DEFAULT` value to boot using the previous kernel:
+3. Once mounted, use the `chroot` command to get into your Instances' root file system. You can then change the `GRUB_DEFAULT` value to boot using the previous kernel:
     ```sh
     chroot /mnt
     nano /etc/default/grub
@@ -71,7 +71,7 @@ categories:
     GRUB_CMDLINE_LINUX="console=tty0 console=ttyS0,115200 earlyprintk=ttyS0,115200 consoleblank=0"
     ```
     Save the file and exit the text editor.
-4. Update the `grub` boatloader` to apply the kernel's update
+4. Update the `grub` boatloader` to apply the kernel's update:
     ```
     # update-grub
     Generating grub configuration file ...
@@ -92,7 +92,7 @@ categories:
 
  ### Examples of failed boots
 
-* In the following example, the Instance may only boot with the root filesystem in `read-only` mode:
+* In the following example, the Instance may only boot with the root file system in `read-only` mode:
     ```sh
     [  OK  ] Finished Remove Stale Onli…ext4 Metadata Check Snapshots.
     [    4.219158] cloud-init[542]: Traceback (most recent call last):
@@ -112,4 +112,4 @@ categories:
     [    4.235672] cloud-init[542]:     os.chmod(path, real_mode)
     [    4.236227] cloud-init[542]: OSError: [Errno 30] Read-only file system: '/var/lib/cloud/data'
     [FAILED] Failed to start Apply the …ngs specified in cloud-config.
-    ```
+    ```

console/account/how-to/resolve-abuse.mdx

@@ -29,7 +29,7 @@ If you encounter any issue with the resolution of an abuse, ensure that you cont
 2. Click the **case ID** to view the specifics of the complaint.
 3. Take note of the details provided and proceed with the necessary steps to address and resolve the issue.
     <Message type="tip">
-    If you need guidance on resolving outgoing DDoS attacks from your server, refer to our documentation on [how to prevent outgoing DDoS](https://www.scaleway.com/en/docs/compute/instances/reference-content/preventing-outgoing-ddos/).
+    If you need guidance on resolving outgoing DDoS attacks from your server, refer to our documentation on [how to prevent outgoing DDoS](/compute/instances/reference-content/preventing-outgoing-ddos/).
     </Message>
     If you are the subject of an abuse report for hosting illegal content (including copyright), we urge you to delete the content from the Scaleway infrastructure promptly.
     * For other types of abuse, here are some suggestions to help you to correct them:
@@ -47,13 +47,13 @@ If you encounter any issue with the resolution of an abuse, ensure that you cont
     If you do not know how to solve the problem, you can contact our [outsourcing partners](https://www.scaleway.com/en/dedibox/outsourcing/) or reach out to Scaleway’s abuse team by opening a ticket directly from your Scaleway console account.
 
 4. The case will be closed at the end of its lifetime by Scaleway’s abuse team, and so will the abuse tickets forming the case.
-    If you receive more abuse reports on the same resource within the case lifetime, it means that you did not take the appropriate measures to prevent further abuse from happening. 
-    Therefore, we recommend you take additional actions and contact our support team if you need assistance. Failure to take appropriate measures to solve the case may result in the locking of your service as per our [Terms of Services](https://www.scaleway.com/en/contracts/) and the legal framework in force. 
+    If you receive more abuse reports on the same resource within the case lifetime, it means that you did not take the appropriate measures to prevent further abuse from happening.
+    Therefore, we recommend you take additional actions and contact our support team if you need assistance. Failure to take appropriate measures to solve the case may result in the locking of your service as per our [Terms of Services](https://www.scaleway.com/en/contracts/) and the legal framework in force.
 
 In specific instances, the case will be closed automatically:
 * abuse reports submitted by Scaleway’s abuse partners may be closed automatically after the automated locking of your services, if several complaints were received within the same case, or if Scaleway considers that the type of abuse reported requires immediate locking of your services.
 * cases regarding security holes will be closed automatically. Refer to the description of the abuse to find more details on patches and updates available.
 
 <Message type="note">
 Refer to our [abuse notice](https://www.scaleway.com/en/abuse-notice/) for further information about Scaleway’s abuse policy.
-</Message>
+</Message>