anchor.diff:  implementation of the `Environment` interface. A number of standard
   environments are built in, and described by the `Environments`
   enumeration. Different environments require different services to be
  -present (for example a Servlet container doesn't require transaction,
  -EJB or JPA services). By default an EE environment is assumed, but you
  -can adjust the environment by calling `bootstrap.setEnvironment()`.
  +present. For example a Servlet container doesn't require transaction,
  +EJB or JPA services.
   
   Weld uses services to communicate with its environment. A service is a
   java class that implements the `org.jboss.weld.bootstrap.api.Service`
  
positive.code: `@PersistenceContext` for injection into managed beans (with the
  `InjectionPoint` provided), is delegated to the container.
  
  To allow JPA integration, the `JpaServices` interface should be
  implemented. This service is not required if the implementation of <<_injection_services>>
  takes care of `@PersistenceContext` injection.
  
  [NOTE]
  ====
  
negative.code: The `org.jboss.weld.bootstrap.api.Bootstrap` interface defines the
  initialization for Weld, bean deployment and bean validation. To boot
  Weld, you must create an instance of
  `org.jboss.weld.bootstrap.WeldBootstrap` which implements 
  `org.jboss.weld.bootstrap.api.CDI11Bootstrap` which extends the above mentioned
  `Bootstrap`. Then you need to tell it about the services in use, and finally request the
  container start.
  
  [source.JAVA, java]
  