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

---
 configuration/authorization-storage.html | 2 +-
 manifest.json                            | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/configuration/authorization-storage.html b/configuration/authorization-storage.html
index c000dda..50dbba4 100644
--- a/configuration/authorization-storage.html
+++ b/configuration/authorization-storage.html
@@ -170,7 +170,7 @@ so that they can be automatically revoked if the authorization code was redeemed
 In the same vein, ad-hoc authorizations are also created when a refresh token is returned during a resource owner password credentials grant request.</p>
 <div class="NOTE"><h5>Note</h5><p>When using the <a href="https://www.nuget.org/packages/OpenIddict.Quartz/">OpenIddict.Quartz</a> integration, ad-hoc authorizations are automatically
 removed from the database after a short period of time (14 days by default). Unlike ad-hoc authorizations, permanent authorizations
-never removed from the database.</p>
+are never removed from the database.</p>
 </div>
 <h2 id="enabling-authorization-entry-validation-at-the-api-level">Enabling authorization entry validation at the API level</h2>
 <p><strong>For performance reasons, OpenIddict 3.0 doesn&#39;t check, by default, the status of an authorization entry when receiving an API request</strong>: access tokens are considered
diff --git a/manifest.json b/manifest.json
index 0f62548..3ebb57f 100644
--- a/manifest.json
+++ b/manifest.json
@@ -9861,7 +9861,7 @@
       "output": {
         ".html": {
           "relative_path": "configuration/authorization-storage.html",
-          "hash": "MSOP1zqo1i7Vi5mvLaISog=="
+          "hash": "klp+k2O0tciz5DQuxVYHaw=="
         }
       },
       "is_incremental": false,