Merge pull request #1333 from jmcdo29/middleware-execution

docs(request-lifecycle): adds information about module bound mw

Author: kamilmysliwiec

content/faq/request-lifecycle.md

@@ -4,7 +4,7 @@ Nest applications handle requests and produce responses in a sequence we refer t
 
 #### Middleware
 
-Middleware is executed in a particular sequence. First, Nest runs globally bound middleware (such as middleware bound with `app.use`) and then it runs [module bound middleware](/middleware), which are determined on paths. Middleware are run sequentially in the order they are bound, similar to the way middleware in Express works.
+Middleware is executed in a particular sequence. First, Nest runs globally bound middleware (such as middleware bound with `app.use`) and then it runs [module bound middleware](/middleware), which are determined on paths. Middleware are run sequentially in the order they are bound, similar to the way middleware in Express works. In the case of middleware bound across different modules, the middleware bound to the root module will run first, and then middleware will run in the order that the modules are added to the imports array.
 
 #### Guards