anchor.diff:  DependencyFactory.emailService.request(customEmailService)
   ----
   
  -Again, this is not a https://docs.spring.io/spring/docs/current/spring-framework-reference/html/beans.html#beans-factory-scopes-request[request scoped dependency] as
  -identified by spring.
  +Again, this is not a request scoped dependency, it is an override for the duration of a given request.
   
   == Session or request scoped dependencies
   
   The above examples only set the dependencies for the duration of a
  -given session or request,and only when the relevant code that sets
  +given session or request, and only when the relevant code that sets
   those dependencies was executed. 
   
   What if you want to always create a session/request scoped dependency
  -for all the users. Let's talk
  -about https://docs.spring.io/spring/docs/current/spring-framework-reference/html/beans.html#beans-factory-scopes-session[session scoped] dependencies. The discussion
  -would be identical for
  -the https://docs.spring.io/spring/docs/current/spring-framework-reference/html/beans.html#beans-factory-scopes-request[request scoped dependencies]. With session
  +for all the users. Let's talk about session scoped dependencies. The discussion
  +would be identical for request scoped dependencies. With session
   scoped dependencies, we want a new instance to be created for each
   session, for all the users.
   
   === Request scope with request lifecycle hooks
   
  -In your Boot.scala, which is used for instantiating and configuring
  +In your `Boot.scala`, which is generally used for instantiating and configuring
   various stuff in Lift:
   
   [source,scala]
  
positive.code: }
  ----
  
  Now, when you do `DependencyFactory.cardService.vend`, it will using
  the `DefaultInstance`. Your call will be implicitly translated to
  `DependencyFactory.instance.vend.cardService.vend`. This is the part
  that allows you to completely override everything you need in your
  
negative.code: `customEmailService` instance for the duration of the current session
  for the current user.
  
  Note that is not a session-scoped dependency (as recognized by Spring, for ex.).
  This is done explicitly in your application code. You are overriding a default dependency
  with some custom instance for the duration of _this_ session. No other user is going to
  see it. And as soon as this session is over, it will be gone until you
  set it explicitly again.
  
  You can do something similar when you need to override a dependency
  during a given request.
  
  [source]
  