From 45bc6280d109b7e353ffaa497a0352c9d040c36d Mon Sep 17 00:00:00 2001
From: Matheus Souza <37983247+souzasmatheus@users.noreply.github.com>
Date: Tue, 11 Dec 2018 14:35:24 -0200
Subject: [PATCH] Fix Markdown comment in proxying docs (#6009)

---
 docusaurus/docs/proxying-api-requests-in-development.md | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/docusaurus/docs/proxying-api-requests-in-development.md b/docusaurus/docs/proxying-api-requests-in-development.md
index 3d27f7d9..d094d267 100644
--- a/docusaurus/docs/proxying-api-requests-in-development.md
+++ b/docusaurus/docs/proxying-api-requests-in-development.md
@@ -9,11 +9,9 @@ sidebar_label: Proxying in Development
 People often serve the front-end React app from the same host and port as their backend implementation.<br>
 For example, a production setup might look like this after the app is deployed:
 
-```
-/             - static server returns index.html with React app
-/todos        - static server returns index.html with React app
-/api/todos    - server handles any /api/* requests using the backend implementation
-```
+    /             - static server returns index.html with React app
+    /todos        - static server returns index.html with React app
+    /api/todos    - server handles any /api/* requests using the backend implementation
 
 Such setup is **not** required. However, if you **do** have a setup like this, it is convenient to write requests like `fetch('/api/todos')` without worrying about redirecting them to another host or port during development.