minor fix

Author: jfankam

pages/bare_metal_cloud/dedicated_servers/vrack_configuring_on_dedicated_server/guide.de-de.md

@@ -222,7 +222,7 @@ sudo systemctl restart NetworkManager.service
 
 Wiederholen Sie diesen Vorgang für Ihre anderen Server und weisen Sie jedem Server eine noch ungenutzte IP-Adresse aus Ihrem privaten Bereich zu. Ihre Server können dann über das private Netzwerk untereinander kommunizieren.
 
-##### Fedora
+##### **Fedora**
 
 Sobald Sie den Namen Ihrer privaten Schnittstelle identifiziert haben (wie [hier](#vrack-interface) erklärt), führen Sie folgenden Befehl aus, um sicherzustellen, dass sie korrekt verbunden ist. In unserem Beispiel heißt das Interface `eno2`:
 

pages/bare_metal_cloud/dedicated_servers/vrack_configuring_on_dedicated_server/guide.en-asia.md

@@ -240,7 +240,7 @@ sudo systemctl restart NetworkManager.service
 
 Repeat this process for your other server(s) and assign an unused IP address from your private range. Once you have done this, your servers will be able to communicate with each other on the private network.
 
-##### Fedora
+##### **Fedora**
 
 Once you have identified the name of your private interface (as explained [here](#vrack-interface)), verify that is it connected. In our example, our interface is called `eno2`:
 

pages/bare_metal_cloud/dedicated_servers/vrack_configuring_on_dedicated_server/guide.en-au.md

@@ -240,7 +240,7 @@ sudo systemctl restart NetworkManager.service
 
 Repeat this process for your other server(s) and assign an unused IP address from your private range. Once you have done this, your servers will be able to communicate with each other on the private network.
 
-##### Fedora
+##### **Fedora**
 
 Once you have identified the name of your private interface (as explained [here](#vrack-interface)), verify that is it connected. In our example, our interface is called `eno2`:
 

pages/bare_metal_cloud/dedicated_servers/vrack_configuring_on_dedicated_server/guide.en-ca.md

@@ -240,7 +240,7 @@ sudo systemctl restart NetworkManager.service
 
 Repeat this process for your other server(s) and assign an unused IP address from your private range. Once you have done this, your servers will be able to communicate with each other on the private network.
 
-##### Fedora
+##### **Fedora**
 
 Once you have identified the name of your private interface (as explained [here](#vrack-interface)), verify that is it connected. In our example, our interface is called `eno2`:
 

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

@@ -240,7 +240,7 @@ sudo systemctl restart NetworkManager.service
 
 Repeat this process for your other server(s) and assign an unused IP address from your private range. Once you have done this, your servers will be able to communicate with each other on the private network.
 
-##### Fedora
+##### **Fedora**
 
 Once you have identified the name of your private interface (as explained [here](#vrack-interface)), verify that is it connected. In our example, our interface is called `eno2`:
 

pages/bare_metal_cloud/dedicated_servers/vrack_configuring_on_dedicated_server/guide.en-ie.md

@@ -240,7 +240,7 @@ sudo systemctl restart NetworkManager.service
 
 Repeat this process for your other server(s) and assign an unused IP address from your private range. Once you have done this, your servers will be able to communicate with each other on the private network.
 
-##### Fedora
+##### **Fedora**
 
 Once you have identified the name of your private interface (as explained [here](#vrack-interface)), verify that is it connected. In our example, our interface is called `eno2`:
 

pages/bare_metal_cloud/dedicated_servers/vrack_configuring_on_dedicated_server/guide.en-sg.md

@@ -240,7 +240,7 @@ sudo systemctl restart NetworkManager.service
 
 Repeat this process for your other server(s) and assign an unused IP address from your private range. Once you have done this, your servers will be able to communicate with each other on the private network.
 
-##### Fedora
+##### **Fedora**
 
 Once you have identified the name of your private interface (as explained [here](#vrack-interface)), verify that is it connected. In our example, our interface is called `eno2`:
 

pages/bare_metal_cloud/dedicated_servers/vrack_configuring_on_dedicated_server/guide.en-us.md

@@ -240,7 +240,7 @@ sudo systemctl restart NetworkManager.service
 
 Repeat this process for your other server(s) and assign an unused IP address from your private range. Once you have done this, your servers will be able to communicate with each other on the private network.
 
-##### Fedora
+##### **Fedora**
 
 Once you have identified the name of your private interface (as explained [here](#vrack-interface)), verify that is it connected. In our example, our interface is called `eno2`:
 

pages/bare_metal_cloud/dedicated_servers/vrack_configuring_on_dedicated_server/guide.es-es.md

@@ -222,7 +222,7 @@ sudo systemctl restart NetworkManager.service
 
 Repita este procedimiento para los demás servidores y asígnele a cada uno de ellos una dirección IP no utilizada desde su rango privado. A continuación, los servidores podrán comunicarse entre sí en la red privada.
 
-##### Fedora
+##### **Fedora**
 
 Una vez que haya identificado el nombre de su interfaz privada (como se explica [aquí](#vrack-interface)), ejecute el siguiente comando para comprobar que esté conectada. En nuestro ejemplo, nuestra interfaz se denomina `eno2`:
 

pages/bare_metal_cloud/dedicated_servers/vrack_configuring_on_dedicated_server/guide.es-us.md

@@ -222,7 +222,7 @@ sudo systemctl restart NetworkManager.service
 
 Repita este procedimiento para los demás servidores y asígnele a cada uno de ellos una dirección IP no utilizada desde su rango privado. A continuación, los servidores podrán comunicarse entre sí en la red privada.
 
-##### Fedora
+##### **Fedora**
 
 Una vez que haya identificado el nombre de su interfaz privada (como se explica [aquí](#vrack-interface)), ejecute el siguiente comando para comprobar que esté conectada. En nuestro ejemplo, nuestra interfaz se denomina `eno2`: