diff --git a/docs/3.0.0-beta.x/deployment/haproxy-proxy.md b/docs/3.0.0-beta.x/deployment/haproxy-proxy.md
index 5dde8aa38e..b98a586779 100644
--- a/docs/3.0.0-beta.x/deployment/haproxy-proxy.md
+++ b/docs/3.0.0-beta.x/deployment/haproxy-proxy.md
@@ -28,7 +28,7 @@ This config is using the sub-domain that is dedicated to Strapi only. It will re
Example Domain: `api.example.com`
-Path: `/etc/haproxy/haproxy.cfg`
+**Path —** `/etc/haproxy/haproxy.cfg`
```
global
@@ -94,7 +94,7 @@ HAProxy **cannot** serve static content, the below example is proxying frontend
Example Domain: `example.com/api`
-Path: `/etc/haproxy/haproxy.cfg`
+**Path —** `/etc/haproxy/haproxy.cfg`
```
global
@@ -171,7 +171,7 @@ Example API Domain: `example.com/api`
Example Admin Domain: `example.com/dashboard`
-Path: `/etc/haproxy/haproxy.cfg`
+**Path —** `/etc/haproxy/haproxy.cfg`
```
global
@@ -252,7 +252,7 @@ In order to take full advantage of a proxied Strapi application you will need to
Example Domain: `api.example.com`
-Path: `config/server.js`
+**Path —** `config/server.js`
```js
module.exports = ({ env }) => ({
@@ -272,7 +272,7 @@ module.exports = ({ env }) => ({
Example Domain: `example.com/api`
-Path: `config/server.js`
+**Path —** `config/server.js`
```js
module.exports = ({ env }) => ({
@@ -294,7 +294,7 @@ Example API Domain: `example.com/api`
Example Admin Domain: `example.com/dashboard`
-Path: `config/server.js`
+**Path —** `config/server.js`
```js
module.exports = ({ env }) => ({
diff --git a/docs/3.0.0-beta.x/getting-started/deployment.md b/docs/3.0.0-beta.x/getting-started/deployment.md
index 55ae69e45a..7683daac20 100644
--- a/docs/3.0.0-beta.x/getting-started/deployment.md
+++ b/docs/3.0.0-beta.x/getting-started/deployment.md
@@ -29,7 +29,7 @@ Manual guides for deployment on various platforms, for One-click and docker plea
Azure
- Step by step guide for deploying on Azure web app
+ Step by step guide for deploying on Azure