Merge pull request #2344 from Scrip7/patch-1

docs(guards): resolve confusion in the hint

Author: kamilmysliwiec

content/guards.md

@@ -8,7 +8,7 @@ Guards have a **single responsibility**. They determine whether a given request
 
 But middleware, by its nature, is dumb. It doesn't know which handler will be executed after calling the `next()` function. On the other hand, **Guards** have access to the `ExecutionContext` instance, and thus know exactly what's going to be executed next. They're designed, much like exception filters, pipes, and interceptors, to let you interpose processing logic at exactly the right point in the request/response cycle, and to do so declaratively. This helps keep your code DRY and declarative.
 
-> info **Hint** Guards are executed **after** each middleware, but **before** any interceptor or pipe.
+> info **Hint** Guards are executed **after** all middleware, but **before** any interceptor or pipe.
 
 #### Authorization guard