Proofreading

Author: Y0Coss

pages/bare_metal_cloud/dedicated_servers/api-os-installation/guide.en-gb.md

@@ -22,7 +22,7 @@ Fully automating OS installation or reinstallation on a [dedicated server](/link
 
 ### OS Compatibility <a name="os-compatibility"></a>
 
-Log in to the [API console](https://api.ovh.com/) and go to the `/dedicated/server`{.action} section.
+Log in to the [API console](/links/api) and go to the `/dedicated/server`{.action} section.
 
 You can list all your [dedicated servers](/links/bare-metal/bare-metal) with the following API call:
 
@@ -309,14 +309,14 @@ You can also monitor the progress of the reinstallation process with the followi
 
 A default efi bootloader path is set when installing from OVHcloud templates but you have the possibility to manage it.
 
-You can retrieve it with the following API call :
+You can retrieve it with the following API call:
 
 > [!api]
 >
 > @api {v1} /dedicated/server GET  /dedicated/server/{serviceName}
 >
 
-You also can set it in the payload of the following API call :
+You also can set it in the payload of the following API call:
 
 > [!api]
 >

pages/bare_metal_cloud/dedicated_servers/api-os-installation/guide.fr-fr.md

@@ -22,7 +22,7 @@ Pour de nombreux cas d'usage, il peut s'avérer intéressant d'automatiser l'ins
 
 ### Compatibilité OS <a name="os-compatibility"></a>
 
-Connectez-vous sur [https://api.ovh.com/](https://api.ovh.com/){.external} puis rendez-vous dans la section `/dedicated/server`{.action}.
+Connectez-vous sur [https://api.ovh.com/](/links/api) puis rendez-vous dans la section `/dedicated/server`{.action}.
 
 Pour lister tous vos [serveurs dédiés](/links/bare-metal/bare-metal) :
 
@@ -286,14 +286,14 @@ Lors de l'exécution du script de post-installation Windows, les fichiers suivan
 }
 ```
 
-`123456789` correspond à l'identifiant de la tâche de la réinstallation de l'OS. Vous pouvez suivre l'état d'avancement global de la tâche à l'aide de l'appel suivant :
+`123456789` correspond à l'identifiant de la tâche de réinstallation de l'OS. Vous pouvez suivre l'état d'avancement global de la tâche à l'aide de l'appel suivant :
 
 > [!api]
 >
 > @api {v1} /dedicated/server GET  /dedicated/server/{serviceName}/task/{taskId}
 >
 
-Sinon vous pouvez aussi avoir un état détaillé de chaque étape de la réinstallation avec l'appel suivant :
+Vous pouvez aussi avoir un état détaillé de chaque étape de la réinstallation grâce à l'appel suivant :
 
 > [!api]
 >

pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.fr-fr.md

@@ -139,7 +139,7 @@ Une fois les champs complétés, démarrez le déploiement en cliquant sur `Exec
 | customizations/sshKey | La clé publique SSH | ❌ |
 | customizations/imageURL | L'URL de votre image Linux | ✅ |
 | customizations/imageCheckSum | Checksum de votre image | ❌ |
-| customizations/imageCheckSumType | Type de checksum de votre image. (md5, sha1, sha256, sha512) | ❌ (sauf si checksum fourni) |
+| customizations/imageCheckSumType | Type de checksum de votre image (md5, sha1, sha256, sha512) | ❌ (sauf si checksum fourni) |
 | customizations/configDriveUserData | Contenu de votre fichier configDrive¹ | ❌ |
 | customizations/configDriveMetadata | Métadonnées Cloud-Init personnalisées | ❌ |
 | customizations/httpHeaders?Key | Clé des en-têtes HTTP | ❌² |

pages/bare_metal_cloud/dedicated_servers/partitioning_ovh/guide.en-gb.md

@@ -11,7 +11,7 @@ updated: 2025-02-25
 > This article is intended for experimented users that have at least basic Linux knowledge, but more importantly deeper technical knowledge on storage and especially on hardware, software RAID as well as Logical volume management (LVM)
 >
 
-With [OVHcloud Dedicated Servers](/links/bare-metal/bare-metal), you can configure Disks, [hardware RAID](/pages/bare_metal_cloud/dedicated_servers/raid_hard), Partitions, [software RAID](/pages/bare_metal_cloud/dedicated_servers/raid_soft), LVM, ZFS, etc. during [OS reinstallation](/pages/bare_metal_cloud/dedicated_servers/getting-started-with-dedicated-server) from the [OVHcloud API](https://api.ovh.com/) as well as the [OVHcloud Control Panel](https://www.ovh.com/manager/#/dedicated/configuration). In this article, we will focus on the [OVHcloud API](https://api.ovh.com/). This will give us more details about the engine that is running in the background in order to create the storage customization on the dedicated server from the input data passed on to the OVHcloud API.
+With [OVHcloud Dedicated Servers](/links/bare-metal/bare-metal), you can configure Disks, [hardware RAID](/pages/bare_metal_cloud/dedicated_servers/raid_hard), Partitions, [software RAID](/pages/bare_metal_cloud/dedicated_servers/raid_soft), LVM, ZFS, etc. during [OS reinstallation](/pages/bare_metal_cloud/dedicated_servers/getting-started-with-dedicated-server) from the [OVHcloud API](/links/api) as well as the [OVHcloud Control Panel](/links/manager). In this article, we will focus on the [OVHcloud API](/links/api). This will give us more details about the engine that is running in the background in order to create the storage customization on the dedicated server from the input data passed on to the OVHcloud API.
 
 Providing in-depth details about storage configuration can help customers understand why:
 
@@ -21,7 +21,7 @@ Providing in-depth details about storage configuration can help customers unders
 ## Requirements
 
 * A [dedicated server](/links/bare-metal/bare-metal) **ready to be installed/reinstalled** in your OVHcloud account.
-* Access to the [OVHcloud API](https://api.ovh.com/).
+* Access to the [OVHcloud API](/links/api).
 
 > [!warning]
 >
@@ -169,7 +169,7 @@ Example of Debian 12 (Bookworm) OS installation on the diskGroup 2:
 
 > [!warning]
 >
-> For the moment API only supports OS installation and storage customization on 1 single disk group. From 1 up to all disks of the selected disk group can be involved in the storage customization. Nevertheless, all other disks will be erased but they will still be visible in the freshly new installed OS and can be used/configured afterward for data.
+> For the moment API only supports OS installation and storage customization on 1 single disk group. From 1 up to all disks of the selected disk group can be involved in the storage customization. Nevertheless, all other disks will be erased but they will still be visible in the freshly new installed OS and can be used/configured afterwards for data.
 >
 
 ### Hardware RAID <a name="hard-raid"></a>
@@ -382,9 +382,9 @@ The following table provides an overview of filesystem compatibility with RAID l
 |UFS, VMFS5, VMFS6, VMFS-L⁴|❌|❌|❌|❌|❌|❌|❌|
 
 ¹ See the [ZFS vdevs vs standard RAID](#raidz2RAID) table for more details.<br />
-² The RAID level for swap can only be set to 1 within the [OVHcloud API](https://api.ovh.com/). In reality, the swap partitions will not use RAID. When a swap partition with size `s` is defined on a server with `n` disks, this will create `n` partitions of size `s` on every disk without any software RAID device underneath.<br />
+² The RAID level for swap can only be set to 1 within the [OVHcloud API](/links/api). In reality, the swap partitions will not use RAID. When a swap partition with size `s` is defined on a server with `n` disks, this will create `n` partitions of size `s` on every disk without any software RAID device underneath.<br />
 ³ Windows native RAID (the one configured by the OVHcloud installer) supports RAID 1 but only between two disks while other implementations allow for more than two.<br />
-⁴ The ESXi installer does not support custom partitioning schemes. Partitioning is defined by the software publisher. Nevertheless, the [OVHcloud API](https://api.ovh.com/) can give you an idea of what the partitioning looks like: see [OS & Partitioning Compatibility](#os-partitioning-compatibility) for more details.<br />
+⁴ The ESXi installer does not support custom partitioning schemes. Partitioning is defined by the software publisher. Nevertheless, the [OVHcloud API](/links/api) can give you an idea of what the partitioning looks like: see [OS & Partitioning Compatibility](#os-partitioning-compatibility) for more details.<br />
 
 > [!warning]
 >
@@ -518,7 +518,7 @@ Basic customer input data errors are directly handled by the OVHcloud API. This
 Customer input data related to partitioning might be too specific to be checked by the OVHcloud API and therefore require pre-processing time. The drawback is that customers are notified later during the OS reinstallation process.
 
 Within the [OVHcloud Control Panel](https://www.ovh.com/manager/#/dedicated/configuration), this is visible on the progress bar
-From the [OVHcloud API](https://api.ovh.com/), this status can be obtained with the following API call:
+From the [OVHcloud API](/links/api), this status can be obtained with the following API call:
 
 > [!api]
 >
@@ -539,11 +539,11 @@ The following table gives an overview of well known customer errors and how to f
 |Error message|Details|Solution(s)|
 |---|---|---|
 |Some Linux distributions such as RHEL family OSes don't support those mountpoints / mountpoint reserved/managed by OVHcloud (`list forbidden mountpoints`). Please remove those mountpoints and restart an installation|- You have chosen `/boot/efi` as mountpoint. OVHcloud will create this partition automatically for you if your server needs one<br />- You have chosen a mountpoint that is symlinked on some operating systems. See [Filesystem Hierarchy Standard](https://refspecs.linuxfoundation.org/fhs.shtml) for more details.|- Choose another mountpoint for the partition or remove this partition from your partitioning layout|
-|Partition of type `t` with mountpoint `m` cannot fill the disk.|- You have chosen the `swap` partition to fill the disk (or partition with size 0 when defined within the [OVHcloud API](https://api.ovh.com/)), we disallow this to avoid creating unnecessarily large `swap` partitions|- Set a fixed size for the `swap` partition|
+|Partition of type `t` with mountpoint `m` cannot fill the disk.|- You have chosen the `swap` partition to fill the disk (or partition with size 0 when defined within the [OVHcloud API](/links/api)), we disallow this to avoid creating unnecessarily large `swap` partitions|- Set a fixed size for the `swap` partition|
 |Missing `/` partition. Please add a `/` partition in your partition scheme!|- Any Linux-based OS needs at least a `/` partition|- Add a `/` partition in your partitioning layout|
-|`message`. Please adjust partitions so that the `p` partition fits on `n` disk(s)|- You have chosen a partition with a RAID that requires a number of disks that your server can provide, but some disks are already full because of other partitions and/or this current partition|- If it is not already set on another partition, set the partition size to fill the disk (or partition with size 0 when defined within the [OVHcloud API](https://api.ovh.com/))<br />- Reduce the size of this partition so that it fits the disks<br />- Reduce the size of other partitions so that this partition fits the disks|
+|`message`. Please adjust partitions so that the `p` partition fits on `n` disk(s)|- You have chosen a partition with a RAID that requires a number of disks that your server can provide, but some disks are already full because of other partitions and/or this current partition|- If it is not already set on another partition, set the partition size to fill the disk (or partition with size 0 when defined within the [OVHcloud API](/links/api))<br />- Reduce the size of this partition so that it fits the disks<br />- Reduce the size of other partitions so that this partition fits the disks|
 |Error with MBR partition table: Partition `p` is larger than 2TiB and this server does not support GPT|- You have defined a partition with a size that exceeds 2TiB and you are trying to apply such partitioning to a server that doesn't support GPT|- Reduce the partition to a size less than 2TiB<br />- Apply this partitioning to another similar server that supports GPT|
-|Error with MBR partition table: partition `p` cannot end after 2 TiB (`interval stop`) and this server does not support GPT! OVHcloud also needs to add a `cloud-init size` cloud-init partition at the very end of the disk. Therefore all customer partitions must end before (2TiB - `cloud-init size`).|- We need to add a config-drive partition at the end of 1 disk on your dedicated server. The last partition of your partitioning will end after the 2TiB position on disk. So appending a config-drive partition after the last partition will start after 2TiB position on disk and you are trying to apply such partitioning to a server that doesn't support GPT|- Reduce the partition `p` size (or any other partition) so that the total sum of all partitions size is less than 2TiB<br />- Do not define a partition that fills the disk (or partition with size 0 when defined within the [OVHcloud API](https://api.ovh.com/)) for servers with disks bigger than 2TiB that don't support GPT|
+|Error with MBR partition table: partition `p` cannot end after 2 TiB (`interval stop`) and this server does not support GPT! OVHcloud also needs to add a `cloud-init size` cloud-init partition at the very end of the disk. Therefore all customer partitions must end before (2TiB - `cloud-init size`).|- We need to add a config-drive partition at the end of 1 disk on your dedicated server. The last partition of your partitioning will end after the 2TiB position on disk. So appending a config-drive partition after the last partition will start after 2TiB position on disk and you are trying to apply such partitioning to a server that doesn't support GPT|- Reduce the partition `p` size (or any other partition) so that the total sum of all partitions size is less than 2TiB<br />- Do not define a partition that fills the disk (or partition with size 0 when defined within the [OVHcloud API](/links/api)) for servers with disks bigger than 2TiB that don't support GPT|
 |`/boot` (or `/` if no `/boot` defined) partition cannot be larger than 2097151 MiB on this hardware|- GRUB partition cannot be larger than 2 TiB with this hardware RAID controller|- Create a separate `/boot` partition with a size less than 2TiB (1GiB should be enough)|
 |`/boot` (or `/` if no `/boot` defined) partition type cannot be `XFS`|- GRUB partition doesn't support `XFS` filesystem type on this Operating System. This is the case for most of debian-like OSes (debian, proxmox, ubuntu)|- Create a separate `/boot` partition with filesystem other than `XFS`<br />- Don't create a separate `/boot` partition but choose a filesystem other than `XFS` for the `/` partition|
 |`ZFS` partition already exists with zpool name `n`. Either choose another name for the `m` partition or set the same RAID level for all partitions within zpool `n`|Assigning multiple `ZFS` partitions to the same zpool name is possible: it means each dataset will be part of the same zpool. This is possible only if all the datasets (therefore the partitions defined via the API) have the same RAID level|- Set the same RAID level as on the existing `ZFS` partition which will be part of the same zpool<br />- Choose another zpool name: this partition will not be part of the same zpool<br />- Don't provide any zpool name: we will assign a default zpool name and this partition will not be part of the same zpool|