Skip to content

Commit 32a1f3c

Browse files
eroviravimalloc
authored andcommitted
Minor grammar corrections in example's README
1 parent 8da4de8 commit 32a1f3c

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

examples/database_blacklist/README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
# Blacklist with a database
2-
Database are a common choice for storing blacklist tokens. It has many
2+
A database is a common choice for storing blacklisted tokens. It has many
33
benefits over an in memory store, like redis. The most obvious benefit of
44
using a database is data consistency. If you add something to the database,
55
you don't need to worry about it vanishing in an event like a power outage.
@@ -15,9 +15,9 @@ Databases also have some cons compared to an in memory store, namely that
1515
they are potentially slower, and they may grow huge over time and need to be
1616
manually pruned back down.
1717

18-
This project contains example code for you you might implement a blacklist
18+
This project contains example code for you to implement a blacklist
1919
using a database, with some more complex features that might benefit your
20-
application. For ease of use, we will use flask-sqlalchey with an in
20+
application. For ease of use, we will use flask-sqlalchemy with an in
2121
memory data store, but in production I would highly recommend using postgres.
2222
Please note that this code is only an example, and although I do my best to
23-
insure its quality, it has not been thoroughly tested.
23+
ensure its quality, it has not been thoroughly tested.

0 commit comments

Comments
 (0)