anchor.diff:  affecting other tests. Doing this manually would be nightmarish,
   extremely prone to errors. The way to do it is to have isolated
   dependency graph for your tests. The key is realizing that the
  -`DependencyFactory` could be just a normal scala instance that itself
  +`DependencyFactory` could be just a normal Scala instance that itself
   can be injected as needed. See, there are no turtles all the way!.
  -This is what David Pollak keeps saying repeatedly about lift and its simplicity.
  -It's just scala code. There is no magic here.
  +This is what David Pollak keeps saying repeatedly about Lift and its simplicity.
  +It is just Scala code. There is no magic here.
   
   A trait that represents your `DependencyFactory`
   
  
positive.code: . https://liftweb.net/api/26/api/index.html#net.liftweb.util.SimpleInjector$Inject[`Inject`], an abstract class within the
   `SimpleInjector` trait.
  
  `FactoryMaker` and `Injector` serve the same purpose, with the former
  having more features. The difference is important. Notes on this are
  at the end. I'll continue with `FactoryMaker` for the sake of
  examples, and then note the differences between the two at the end.
  
negative.code: === Request scope with request lifecycle hooks
  
  In your Boot.scala, which is used for instantiating and configuring
  various stuff in Lift:
  
  [source,scala]
  ----
  