From d1b884aec6d5e30de21cf7afee3ef9ce629ec87a Mon Sep 17 00:00:00 2001
From: frederikhors <41120635+frederikhors@users.noreply.github.com>
Date: Sun, 23 Feb 2020 21:33:57 +0100
Subject: [PATCH] Misprint (#40)

---
 docs/guide.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/guide.md b/docs/guide.md
index c97755d..5732303 100644
--- a/docs/guide.md
+++ b/docs/guide.md
@@ -1558,7 +1558,7 @@ roles:
 
 This configuration is relatively simple to follow the `roles_query` parameter is the query that must be run to help figure out a users role. This query can be as complex as you like and include joins with other tables. 
 
-The individual roles are defined under the `roles` parameter and this includes each table the role has a custom setting for. The role is dynamically matched using the `match` parameter for example in the above case `users.id = 1` means that when the `roles_query` is executed a user with the id `1` willbe assigned the admin role and those that don't match get the `user` role if authenticated successfully or the `anon` role.
+The individual roles are defined under the `roles` parameter and this includes each table the role has a custom setting for. The role is dynamically matched using the `match` parameter for example in the above case `users.id = 1` means that when the `roles_query` is executed a user with the id `1` will be assigned the admin role and those that don't match get the `user` role if authenticated successfully or the `anon` role.
 
 ## Remote Joins