anchor.diff:  `@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.
  +To allow JPA integration, the `org.jboss.weld.injection.spi.JpaInjectionServices` interface 
  +should be implemented. This service is not required if the implementation of 
  +<<_injection_services>> takes care of `@PersistenceContext` injection.
   
   [NOTE]
   ====
  
positive.code: 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()`.
  
  Weld uses services to communicate with its environment. A service is a
  java class that implements the `org.jboss.weld.bootstrap.api.Service`
  
negative.code: 
  * An observer for `@Initialized(ConversationScoped.class)` or `@Destroyed(ConversationScoped.class)` event no longer forces eager conversation context initialization. See also <<_lazy_and_eager_conversation_context_initialization>>.
  
  * `ScheduledExecutorServiceFactory` is deprecated and no default implementation is provided by default. This service has not been used by Weld internals at least since version 1.1.0.Final.
  