anchor.diff:  link:configuration/prettyfaces[PrettyFaces XML and Annotations], and via link:integration/cdi[cdi] and 
   link:integration/spring[spring]; these methods may be used to avoid the need for a provider registration file.
   
  -=== Verify that your configuration is installed
  +=== 4. Verify that your configuration is installed
   
   Before link:configuration[configuring Rewrite], you may wish to verify that your provider has
   been properly installed and activated. To do this, start your application and look at the server output, where
  
positive.code: of the provider registration file, and make sure that you have correctly spelled the fully qualified name of
  each provider implementation.
  
  === Add rules to your configuration
  
  As can be seen above, configuring Rewrite may be performed using the +ConfigurationBuilder+ class, which allows
  addition of pre-constructed +Rule+ instances, as well as definition of custom rules using +Condition+, +Operation+, 
  
negative.code: }
  ----
  
  === 3. Activate your configuration
  
  The next step is to register your +ConfigurationProvider+ with Rewrite. You will need to create a
  provider registration file called +/META-INF/services/org.ocpsoft.rewrite.config.ConfigurationProvider+.
  
  This file must contain the fully qualified class name of each configuration implementation that
  