From f99421eb95f3e363d371ed1e9d91bcd5f2aaf892 Mon Sep 17 00:00:00 2001
From: hackerman <3372410+aeneasr@users.noreply.github.com>
Date: Sat, 25 Apr 2020 16:29:31 +0200
Subject: [PATCH] Update oauth2.md

---
 docs/versioned_docs/version-v1.4/oauth2.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/versioned_docs/version-v1.4/oauth2.md b/docs/versioned_docs/version-v1.4/oauth2.md
index b9112bf17a9..588d3db9dcb 100644
--- a/docs/versioned_docs/version-v1.4/oauth2.md
+++ b/docs/versioned_docs/version-v1.4/oauth2.md
@@ -79,7 +79,9 @@ More details about the various OAuth2 flows can be found in these articles:
 :::info The OAuth2 Scope reflects a permission the user gave to the OAuth2
 Application, not a permission the system (e.g. API) gave to that OAuth2
 application. Also, the OAuth2 Scope can not be changed without revoking the
-token. :::
+token.
+
+:::
 
 A second important concept is the OAuth 2.0 Scope. Many people confuse OAuth 2.0
 Scope with internal Access Control like for example Role Based Access Control