From 0718bfe1458b8a6ffe63e178edcb0fa08a9b1c41 Mon Sep 17 00:00:00 2001
From: OpenIddict Bot <32257313+openiddict-bot@users.noreply.github.com>
Date: Mon, 25 Jan 2021 20:42:38 +0000
Subject: [PATCH] Update the documentation pages

---
 configuration/token-formats.html | 5 ++---
 manifest.json                    | 2 +-
 2 files changed, 3 insertions(+), 4 deletions(-)

diff --git a/configuration/token-formats.html b/configuration/token-formats.html
index 8f8490a..9990f2f 100644
--- a/configuration/token-formats.html
+++ b/configuration/token-formats.html
@@ -68,11 +68,10 @@
             <article class="content wrap" id="_content" data-uid="">
 <h1 id="token-formats">Token formats</h1>
 
-<blockquote><p>[!INFO]
-In OpenIddict 3.0, being able to revoke a token is not tied to the token format and doesn&#39;t require enabling reference tokens:
+<div class="NOTE"><h5>Note</h5><p>In OpenIddict 3.0, being able to revoke a token is not tied to the token format and doesn&#39;t require enabling reference tokens:
 regular JWT or ASP.NET Core Data Protection tokens can be revoked as long as token storage is not explicitly disabled by the developer</p>
 <p>For more information about reference tokens, read <a href="token-storage.html">Token storage</a>.</p>
-</blockquote>
+</div>
 <h2 id="json-web-token">JSON Web Token</h2>
 <p>OpenIddict 3.0 implements the <a href="https://tools.ietf.org/html/rfc7519">JSON Web Token</a>, <a href="https://tools.ietf.org/html/rfc7515">JSON Web Signature</a>
 and <a href="https://tools.ietf.org/html/rfc7516">JSON Web Encryption</a> standards and relies on the
diff --git a/manifest.json b/manifest.json
index 3ebb57f..5793fbc 100644
--- a/manifest.json
+++ b/manifest.json
@@ -9897,7 +9897,7 @@
       "output": {
         ".html": {
           "relative_path": "configuration/token-formats.html",
-          "hash": "eAWnxe/vobBoHyPOHuKRmQ=="
+          "hash": "ql1BoqZfIUvMtjewno3HPA=="
         }
       },
       "is_incremental": false,