ovh · Jessica41 · Nov 13, 2025 · Nov 13, 2025 · Nov 13, 2025 · Nov 13, 2025
diff --git a/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing/guide.de-de.md b/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing/guide.de-de.md
@@ -359,7 +359,7 @@ In unseren Beispielen verwenden wir den Texteditor `nano`. Bei einigen Betriebss
 >> > Bei Verwendung des Befehls `netplan try` kann eine Warnmeldung wie `Permissions for /etc/netplan/xx-cloud-init.yaml are too open. Netplan configuration should NOT be accessible by others`. Das bedeutet nur, dass die Datei keine einschränkenden Berechtigungen hat. Dies hat keine Auswirkungen auf die Konfiguration Ihrer Additional IP. Weitere Informationen zu Dateiberechtigungen finden Sie in der [offiziellen Dokumentation von Ubuntu](https://help.ubuntu.com/community/FilePermissions).
 >> >
 >>
-> AlmaLinux (8 & 9), Rocky Linux (8 & 9)
+> AlmaLinux / Rocky Linux
 >> **AlmaLinux (8 & 9), Rocky Linux (8 & 9)**
 >> Die Hauptkonfigurationsdatei befindet sich unter `/etc/sysconfig/network-scripts/`. In unserem Beispiel heißt es `ifcfg-eth0`. Überprüfen Sie Ihren Dateinamen in diesem Ordner, bevor Sie Änderungen vornehmen.
 >>

diff --git a/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing/guide.en-asia.md b/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing/guide.en-asia.md
@@ -317,7 +317,7 @@ In the examples below, we will use the `nano` text editor. With some operating s
 >> > It is important to respect the alignment of each element in this file as represented in the example above. Do not use the tab key to create your spacing. Only the space key is needed.
 >> >
 >>
->> /// details | **Configuration example:**
+>> /// details | **Configuration example**
 >>
 >> ```yaml
 >> network:
@@ -348,7 +348,7 @@ In the examples below, we will use the `nano` text editor. With some operating s
 >> > When using the `netplan try` command, it is possible that the system returns a warning message such as `Permissions for /etc/netplan/xx-cloud-init.yaml are too open. Netplan configuration should NOT be accessible by others`. This simply means that the file does not have restrictive permissions. This does not affect the configuration of your Additional IP. For more information about file permissions, consult the [official documentation of ubuntu](https://help.ubuntu.com/community/FilePermissions).
 >> >
 >>
-> AlmaLinux (8 & 9), Rocky Linux (8 & 9)
+> AlmaLinux / Rocky Linux
 >> **AlmaLinux (8 & 9), Rocky Linux (8 & 9)**
 >>
 >> The main configuration file is located in `/etc/sysconfig/network-scripts/`. In this example it is called `ifcfg-eth0`. Before making changes, verify the actual file name in this folder.
@@ -382,7 +382,7 @@ In the examples below, we will use the `nano` text editor. With some operating s
 >> BROADCAST=ADDITIONAL_IP
 >> ```
 >>
->> /// details | **Configuration example:**
+>> /// details | **Configuration example**
 >>
 >> ```console
 >> DEVICE=eth0:0

diff --git a/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing/guide.en-au.md b/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing/guide.en-au.md
@@ -317,7 +317,7 @@ In the examples below, we will use the `nano` text editor. With some operating s
 >> > It is important to respect the alignment of each element in this file as represented in the example above. Do not use the tab key to create your spacing. Only the space key is needed.
 >> >
 >>
->> /// details | **Configuration example:**
+>> /// details | **Configuration example**
 >>
 >> ```yaml
 >> network:
@@ -348,7 +348,7 @@ In the examples below, we will use the `nano` text editor. With some operating s
 >> > When using the `netplan try` command, it is possible that the system returns a warning message such as `Permissions for /etc/netplan/xx-cloud-init.yaml are too open. Netplan configuration should NOT be accessible by others`. This simply means that the file does not have restrictive permissions. This does not affect the configuration of your Additional IP. For more information about file permissions, consult the [official documentation of ubuntu](https://help.ubuntu.com/community/FilePermissions).
 >> >
 >>
-> AlmaLinux (8 & 9), Rocky Linux (8 & 9)
+> AlmaLinux / Rocky Linux
 >> **AlmaLinux (8 & 9), Rocky Linux (8 & 9)**
 >>
 >> The main configuration file is located in `/etc/sysconfig/network-scripts/`. In this example it is called `ifcfg-eth0`. Before making changes, verify the actual file name in this folder.
@@ -382,7 +382,7 @@ In the examples below, we will use the `nano` text editor. With some operating s
 >> BROADCAST=ADDITIONAL_IP
 >> ```
 >>
->> /// details | **Configuration example:**
+>> /// details | **Configuration example**
 >>
 >> ```console
 >> DEVICE=eth0:0

diff --git a/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing/guide.en-ca.md b/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing/guide.en-ca.md
@@ -317,7 +317,7 @@ In the examples below, we will use the `nano` text editor. With some operating s
 >> > It is important to respect the alignment of each element in this file as represented in the example above. Do not use the tab key to create your spacing. Only the space key is needed.
 >> >
 >>
->> /// details | **Configuration example:**
+>> /// details | **Configuration example**
 >>
 >> ```yaml
 >> network:
@@ -348,7 +348,7 @@ In the examples below, we will use the `nano` text editor. With some operating s
 >> > When using the `netplan try` command, it is possible that the system returns a warning message such as `Permissions for /etc/netplan/xx-cloud-init.yaml are too open. Netplan configuration should NOT be accessible by others`. This simply means that the file does not have restrictive permissions. This does not affect the configuration of your Additional IP. For more information about file permissions, consult the [official documentation of ubuntu](https://help.ubuntu.com/community/FilePermissions).
 >> >
 >>
-> AlmaLinux (8 & 9), Rocky Linux (8 & 9)
+> AlmaLinux / Rocky Linux
 >> **AlmaLinux (8 & 9), Rocky Linux (8 & 9)**
 >>
 >> The main configuration file is located in `/etc/sysconfig/network-scripts/`. In this example it is called `ifcfg-eth0`. Before making changes, verify the actual file name in this folder.
@@ -382,7 +382,7 @@ In the examples below, we will use the `nano` text editor. With some operating s
 >> BROADCAST=ADDITIONAL_IP
 >> ```
 >>
->> /// details | **Configuration example:**
+>> /// details | **Configuration example**
 >>
 >> ```console
 >> DEVICE=eth0:0

diff --git a/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing/guide.en-gb.md
@@ -317,7 +317,7 @@ In the examples below, we will use the `nano` text editor. With some operating s
 >> > It is important to respect the alignment of each element in this file as represented in the example above. Do not use the tab key to create your spacing. Only the space key is needed.
 >> >
 >>
->> /// details | **Configuration example:**
+>> /// details | **Configuration example**
 >>
 >> ```yaml
 >> network:
@@ -348,7 +348,7 @@ In the examples below, we will use the `nano` text editor. With some operating s
 >> > When using the `netplan try` command, it is possible that the system returns a warning message such as `Permissions for /etc/netplan/xx-cloud-init.yaml are too open. Netplan configuration should NOT be accessible by others`. This simply means that the file does not have restrictive permissions. This does not affect the configuration of your Additional IP. For more information about file permissions, consult the [official documentation of ubuntu](https://help.ubuntu.com/community/FilePermissions).
 >> >
 >>
-> AlmaLinux (8 & 9), Rocky Linux (8 & 9)
+> AlmaLinux / Rocky Linux
 >> **AlmaLinux (8 & 9), Rocky Linux (8 & 9)**
 >>
 >> The main configuration file is located in `/etc/sysconfig/network-scripts/`. In this example it is called `ifcfg-eth0`. Before making changes, verify the actual file name in this folder.
@@ -382,7 +382,7 @@ In the examples below, we will use the `nano` text editor. With some operating s
 >> BROADCAST=ADDITIONAL_IP
 >> ```
 >>
->> /// details | **Configuration example:**
+>> /// details | **Configuration example**
 >>
 >> ```console
 >> DEVICE=eth0:0

diff --git a/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing/guide.en-ie.md b/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing/guide.en-ie.md
@@ -317,7 +317,7 @@ In the examples below, we will use the `nano` text editor. With some operating s
 >> > It is important to respect the alignment of each element in this file as represented in the example above. Do not use the tab key to create your spacing. Only the space key is needed.
 >> >
 >>
->> /// details | **Configuration example:**
+>> /// details | **Configuration example**
 >>
 >> ```yaml
 >> network:
@@ -348,7 +348,7 @@ In the examples below, we will use the `nano` text editor. With some operating s
 >> > When using the `netplan try` command, it is possible that the system returns a warning message such as `Permissions for /etc/netplan/xx-cloud-init.yaml are too open. Netplan configuration should NOT be accessible by others`. This simply means that the file does not have restrictive permissions. This does not affect the configuration of your Additional IP. For more information about file permissions, consult the [official documentation of ubuntu](https://help.ubuntu.com/community/FilePermissions).
 >> >
 >>
-> AlmaLinux (8 & 9), Rocky Linux (8 & 9)
+> AlmaLinux / Rocky Linux
 >> **AlmaLinux (8 & 9), Rocky Linux (8 & 9)**
 >>
 >> The main configuration file is located in `/etc/sysconfig/network-scripts/`. In this example it is called `ifcfg-eth0`. Before making changes, verify the actual file name in this folder.
@@ -382,7 +382,7 @@ In the examples below, we will use the `nano` text editor. With some operating s
 >> BROADCAST=ADDITIONAL_IP
 >> ```
 >>
->> /// details | **Configuration example:**
+>> /// details | **Configuration example**
 >>
 >> ```console
 >> DEVICE=eth0:0

diff --git a/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing/guide.en-sg.md b/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing/guide.en-sg.md
@@ -317,7 +317,7 @@ In the examples below, we will use the `nano` text editor. With some operating s
 >> > It is important to respect the alignment of each element in this file as represented in the example above. Do not use the tab key to create your spacing. Only the space key is needed.
 >> >
 >>
->> /// details | **Configuration example:**
+>> /// details | **Configuration example**
 >>
 >> ```yaml
 >> network:
@@ -348,7 +348,7 @@ In the examples below, we will use the `nano` text editor. With some operating s
 >> > When using the `netplan try` command, it is possible that the system returns a warning message such as `Permissions for /etc/netplan/xx-cloud-init.yaml are too open. Netplan configuration should NOT be accessible by others`. This simply means that the file does not have restrictive permissions. This does not affect the configuration of your Additional IP. For more information about file permissions, consult the [official documentation of ubuntu](https://help.ubuntu.com/community/FilePermissions).
 >> >
 >>
-> AlmaLinux (8 & 9), Rocky Linux (8 & 9)
+> AlmaLinux / Rocky Linux
 >> **AlmaLinux (8 & 9), Rocky Linux (8 & 9)**
 >>
 >> The main configuration file is located in `/etc/sysconfig/network-scripts/`. In this example it is called `ifcfg-eth0`. Before making changes, verify the actual file name in this folder.
@@ -382,7 +382,7 @@ In the examples below, we will use the `nano` text editor. With some operating s
 >> BROADCAST=ADDITIONAL_IP
 >> ```
 >>
->> /// details | **Configuration example:**
+>> /// details | **Configuration example**
 >>
 >> ```console
 >> DEVICE=eth0:0

diff --git a/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing/guide.en-us.md b/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing/guide.en-us.md
@@ -317,7 +317,7 @@ In the examples below, we will use the `nano` text editor. With some operating s
 >> > It is important to respect the alignment of each element in this file as represented in the example above. Do not use the tab key to create your spacing. Only the space key is needed.
 >> >
 >>
->> /// details | **Configuration example:**
+>> /// details | **Configuration example**
 >>
 >> ```yaml
 >> network:
@@ -348,7 +348,7 @@ In the examples below, we will use the `nano` text editor. With some operating s
 >> > When using the `netplan try` command, it is possible that the system returns a warning message such as `Permissions for /etc/netplan/xx-cloud-init.yaml are too open. Netplan configuration should NOT be accessible by others`. This simply means that the file does not have restrictive permissions. This does not affect the configuration of your Additional IP. For more information about file permissions, consult the [official documentation of ubuntu](https://help.ubuntu.com/community/FilePermissions).
 >> >
 >>
-> AlmaLinux (8 & 9), Rocky Linux (8 & 9)
+> AlmaLinux / Rocky Linux
 >> **AlmaLinux (8 & 9), Rocky Linux (8 & 9)**
 >>
 >> The main configuration file is located in `/etc/sysconfig/network-scripts/`. In this example it is called `ifcfg-eth0`. Before making changes, verify the actual file name in this folder.
@@ -382,7 +382,7 @@ In the examples below, we will use the `nano` text editor. With some operating s
 >> BROADCAST=ADDITIONAL_IP
 >> ```
 >>
->> /// details | **Configuration example:**
+>> /// details | **Configuration example**
 >>
 >> ```console
 >> DEVICE=eth0:0

diff --git a/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing/guide.es-es.md b/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing/guide.es-es.md
@@ -188,8 +188,8 @@ En los ejemplos siguientes utilizaremos el editor de texto `nano`. En algunos si
 >> **Fedora 41 y versiones posteriores**
 >>
 >> Fedora ahora utiliza archivos clave (*keyfiles*).
-Fedora solía utilizar perfiles de red almacenados por NetworkManager en formato ifcfg en el directorio `/etc/sysconfig/network-scripts/`.<br>
-Como el ifcfg ya no está actualizado, NetworkManager ya no crea nuevos perfiles en este formato de forma predeterminada. El archivo de configuración se encuentra ahora en `/etc/NetworkManager/system-connections/`.
+>> Fedora solía utilizar perfiles de red almacenados por NetworkManager en formato ifcfg en el directorio `/etc/sysconfig/network-scripts/`.<br>
+>> Como el ifcfg ya no está actualizado, NetworkManager ya no crea nuevos perfiles en este formato de forma predeterminada. El archivo de configuración se encuentra ahora en `/etc/NetworkManager/system-connections/`.
 >>
 >> 1\. Crear una copia de seguridad del archivo de configuración
 >>
@@ -352,7 +352,7 @@ Como el ifcfg ya no está actualizado, NetworkManager ya no crea nuevos perfiles
 >> > Al utilizar el comando `netplan try`, es posible que el sistema envíe un mensaje de advertencia como `Permissions for /etc/netplan/xx-cloud-init.yaml are too open. Netplan configuration should NOT be accessible by others`. Simplemente significa que el archivo no tiene permisos restrictivos. Esto no afecta a la configuración de su Additional IP. Para obtener más información sobre los permisos de archivo, consulte la [documentación oficial de ubuntu](https://help.ubuntu.com/community/FilePermissions).
 >> >
 >>
-> AlmaLinux (8 & 9), Rocky Linux (8 & 9)
+> AlmaLinux / Rocky Linux
 >> **AlmaLinux (8 & 9), Rocky Linux (8 & 9)**
 >>
 >> El archivo de configuración principal se encuentra en `/etc/sysconfig/network-scripts/`. En nuestro ejemplo, se denomina `ifcfg-eth0`. Antes de realizar cualquier cambio, compruebe el nombre de archivo real en esta carpeta.
@@ -457,7 +457,7 @@ Como el ifcfg ya no está actualizado, NetworkManager ya no crea nuevos perfiles
 >>
 >> Los siguientes pasos pueden realizarse, bien mediante línea comandos, o bien a través de la interfaz gráfica.
 >>
->> Mediante línea de comandos (recomendado)
+>> **Mediante línea de comandos (recomendado)**
 >>
 >> En los comandos indicados más abajo, sustituya los siguientes valores:
 >>

diff --git a/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing/guide.es-us.md b/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing/guide.es-us.md
@@ -188,8 +188,8 @@ En los ejemplos siguientes utilizaremos el editor de texto `nano`. En algunos si
 >> **Fedora 41 y versiones posteriores**
 >>
 >> Fedora ahora utiliza archivos clave (*keyfiles*).
-Fedora solía utilizar perfiles de red almacenados por NetworkManager en formato ifcfg en el directorio `/etc/sysconfig/network-scripts/`.<br>
-Como el ifcfg ya no está actualizado, NetworkManager ya no crea nuevos perfiles en este formato de forma predeterminada. El archivo de configuración se encuentra ahora en `/etc/NetworkManager/system-connections/`.
+>> Fedora solía utilizar perfiles de red almacenados por NetworkManager en formato ifcfg en el directorio `/etc/sysconfig/network-scripts/`.<br>
+>> Como el ifcfg ya no está actualizado, NetworkManager ya no crea nuevos perfiles en este formato de forma predeterminada. El archivo de configuración se encuentra ahora en `/etc/NetworkManager/system-connections/`.
 >>
 >> 1\. Crear una copia de seguridad del archivo de configuración
 >>
@@ -352,7 +352,7 @@ Como el ifcfg ya no está actualizado, NetworkManager ya no crea nuevos perfiles
 >> > Al utilizar el comando `netplan try`, es posible que el sistema envíe un mensaje de advertencia como `Permissions for /etc/netplan/xx-cloud-init.yaml are too open. Netplan configuration should NOT be accessible by others`. Simplemente significa que el archivo no tiene permisos restrictivos. Esto no afecta a la configuración de su Additional IP. Para obtener más información sobre los permisos de archivo, consulte la [documentación oficial de ubuntu](https://help.ubuntu.com/community/FilePermissions).
 >> >
 >>
-> AlmaLinux (8 & 9), Rocky Linux (8 & 9)
+> AlmaLinux / Rocky Linux
 >> **AlmaLinux (8 & 9), Rocky Linux (8 & 9)**
 >>
 >> El archivo de configuración principal se encuentra en `/etc/sysconfig/network-scripts/`. En nuestro ejemplo, se denomina `ifcfg-eth0`. Antes de realizar cualquier cambio, compruebe el nombre de archivo real en esta carpeta.
@@ -457,7 +457,7 @@ Como el ifcfg ya no está actualizado, NetworkManager ya no crea nuevos perfiles
 >>
 >> Los siguientes pasos pueden realizarse, bien mediante línea comandos, o bien a través de la interfaz gráfica.
 >>
->> Mediante línea de comandos (recomendado)
+>> **Mediante línea de comandos (recomendado)**
 >>
 >> En los comandos indicados más abajo, sustituya los siguientes valores:
 >>

diff --git a/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing/guide.fr-ca.md b/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing/guide.fr-ca.md
@@ -191,8 +191,8 @@ Dans les exemples ci-dessous, nous utiliserons l'éditeur de texte `nano`. Avec
 >> sudo /etc/init.d/networking restart
 >> ```
 >>
-> Fedora 40+
->> **Fedora 40 et versions ultérieures**
+> Fedora 41+
+>> **Fedora 41 et versions ultérieures**
 >>
 >> Fedora utilise dorénavant des fichiers clés (*keyfiles*).
 >> Fedora utilisait auparavant des profils réseau stockés par NetworkManager au format ifcfg dans le répertoire `/etc/sysconfig/network-scripts/`.<br>
@@ -359,7 +359,7 @@ Dans les exemples ci-dessous, nous utiliserons l'éditeur de texte `nano`. Avec
 >> > Lors de l'utilisation de la commande `netplan try`, il est possible que le système renvoie un message d'avertissement tel que `Permissions for /etc/netplan/xx-cloud-init.yaml are too open. Netplan configuration should NOT be accessible by others`. Cela signifie simplement que le fichier n'a pas de permissions restrictives. Cela n'affecte pas la configuration de votre Additional IP. Pour plus d'informations sur les permissions de fichiers, consultez la [documentation officielle d'ubuntu](https://help.ubuntu.com/community/FilePermissions).
 >> >
 >>
-> AlmaLinux (8 & 9), Rocky Linux (8 & 9)
+> AlmaLinux / Rocky Linux
 >> **AlmaLinux (8 & 9), Rocky Linux (8 & 9)**
 >>
 >> Le fichier de configuration principal se trouve dans `/etc/sysconfig/network-scripts/`. Dans notre exemple, il est appelé `ifcfg-eth0`. Avant d'apporter des modifications, vérifiez le nom de fichier réel dans ce dossier.

diff --git a/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing/guide.fr-fr.md b/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing/guide.fr-fr.md
@@ -191,8 +191,8 @@ Dans les exemples ci-dessous, nous utiliserons l'éditeur de texte `nano`. Avec
 >> sudo /etc/init.d/networking restart
 >> ```
 >>
-> Fedora 40+
->> **Fedora 40 et versions ultérieures**
+> Fedora 41+
+>> **Fedora 41 et versions ultérieures**
 >>
 >> Fedora utilise dorénavant des fichiers clés (*keyfiles*).
 >> Fedora utilisait auparavant des profils réseau stockés par NetworkManager au format ifcfg dans le répertoire `/etc/sysconfig/network-scripts/`.<br>
@@ -359,7 +359,7 @@ Dans les exemples ci-dessous, nous utiliserons l'éditeur de texte `nano`. Avec
 >> > Lors de l'utilisation de la commande `netplan try`, il est possible que le système renvoie un message d'avertissement tel que `Permissions for /etc/netplan/xx-cloud-init.yaml are too open. Netplan configuration should NOT be accessible by others`. Cela signifie simplement que le fichier n'a pas de permissions restrictives. Cela n'affecte pas la configuration de votre Additional IP. Pour plus d'informations sur les permissions de fichiers, consultez la [documentation officielle d'ubuntu](https://help.ubuntu.com/community/FilePermissions).
 >> >
 >>
-> AlmaLinux (8 & 9), Rocky Linux (8 & 9)
+> AlmaLinux / Rocky Linux
 >> **AlmaLinux (8 & 9), Rocky Linux (8 & 9)**
 >>
 >> Le fichier de configuration principal se trouve dans `/etc/sysconfig/network-scripts/`. Dans notre exemple, il est appelé `ifcfg-eth0`. Avant d'apporter des modifications, vérifiez le nom de fichier réel dans ce dossier.