From 637e80ed46d40f28f87fd22e41168a3c3e1d5456 Mon Sep 17 00:00:00 2001
From: Victory Ifebhor <63762763+VictoryIfebhor@users.noreply.github.com>
Date: Tue, 12 Jul 2022 00:41:22 +0100
Subject: [PATCH] Fixed a grammatical error in the docs

A grammatical error was observed in the docs. It said "Which keeps javascript cannot be able to access the cookies."

I think want was meant was "Which means javascript cannot be able to access the cookies."
---
 docs/usage/jwt-in-cookies.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/usage/jwt-in-cookies.md b/docs/usage/jwt-in-cookies.md
index 9cb5bb0..ba87899 100644
--- a/docs/usage/jwt-in-cookies.md
+++ b/docs/usage/jwt-in-cookies.md
@@ -1,4 +1,4 @@
-Highly recommended using JWT in cookies, if your frontend interacts with the backend, your frontend may be storing JWT in the browser localStorage or sessionStorage. There is nothing wrong with this, but if you have any sort of XSS vulnerability on your site, an attacker will be able to trivially steal your tokens. If you want some additional security on your site, you can save your JWT in an httponly cookies. Which keeps javascript cannot be able to access the cookies.
+Highly recommended using JWT in cookies, if your frontend interacts with the backend, your frontend may be storing JWT in the browser localStorage or sessionStorage. There is nothing wrong with this, but if you have any sort of XSS vulnerability on your site, an attacker will be able to trivially steal your tokens. If you want some additional security on your site, you can save your JWT in an httponly cookies. Which means javascript cannot be able to access the cookies.
 
 Here is a basic example of how to store JWT in cookies: