From c693a2bffd5a5a1a13136a903a19f764bc47bddb Mon Sep 17 00:00:00 2001
From: "Lewis M. Kabui" <13940255+lewisemm@users.noreply.github.com>
Date: Mon, 10 Jul 2023 01:40:29 +0300
Subject: [PATCH] Replace "defining" with "define" (#517)

---
 docs/blocklist_and_token_revoking.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/blocklist_and_token_revoking.rst b/docs/blocklist_and_token_revoking.rst
index 9250cfc0..2b2353a6 100644
--- a/docs/blocklist_and_token_revoking.rst
+++ b/docs/blocklist_and_token_revoking.rst
@@ -4,7 +4,7 @@ JWT Revoking / Blocklist
 ========================
 JWT revoking is a mechanism for preventing an otherwise valid JWT from accessing your
 routes while still letting other valid JWTs in. To utilize JWT revoking in this
-extension, you must defining a callback function via the
+extension, you must define a callback function via the
 :meth:`~flask_jwt_extended.JWTManager.token_in_blocklist_loader` decorator.
 This function is called whenever a valid JWT is used to access a protected route.
 The callback will receive the JWT header and JWT payload as arguments, and must