From 78e51d51591dbd07dc8ebdc5569c52199496bbdd Mon Sep 17 00:00:00 2001
From: 0xflotus <0xflotus@gmail.com>
Date: Thu, 14 May 2020 18:49:48 +0200
Subject: [PATCH] (docs): enabled syntax highlighting for http patch

---
 docs/custom_virtualenvs.md | 16 +++++++++-------
 1 file changed, 9 insertions(+), 7 deletions(-)

diff --git a/docs/custom_virtualenvs.md b/docs/custom_virtualenvs.md
index 792cb25bcb..9b47c5d5ca 100644
--- a/docs/custom_virtualenvs.md
+++ b/docs/custom_virtualenvs.md
@@ -140,14 +140,16 @@ Assigning Custom Virtualenvs
 Once you've created a custom virtualenv, you can assign it at the Organization,
 Project, or Job Template level:
 
-    PATCH https://awx-host.example.org/api/v2/organizations/N/
-    PATCH https://awx-host.example.org/api/v2/projects/N/
-    PATCH https://awx-host.example.org/api/v2/job_templates/N/
+```http
+PATCH https://awx-host.example.org/api/v2/organizations/N/
+PATCH https://awx-host.example.org/api/v2/projects/N/
+PATCH https://awx-host.example.org/api/v2/job_templates/N/
 
-    Content-Type: application/json
-    {
-        'custom_virtualenv': '/opt/my-envs/custom-venv/'
-    }
+Content-Type: application/json
+{
+    "custom_virtualenv": "/opt/my-envs/custom-venv/"
+}
+```
 
 An HTTP `GET` request to `/api/v2/config/` will provide a list of
 detected installed virtualenvs: