anchor.diff:     }
   ----
   
  -This will basically create a command that can be called _envers-setup_ from the CLI (note the substitution of colons and
  -spaces by hyphens) and as _Envers: Setup_ in the _Auditing_ category in the Forge wizard +
  -
  -As the newly created command will not require any input from the user, we will leave the `initializeUI` method empty.
  -However, in order to implement the command execution, we will need to change a little bit our class. More precisely we
  -will have to extend from another abstract command class. The rationale behind this is that we want to update the
  -*current* project POM. Extending `org.jboss.forge.addon.projects.ui.AbstractProjectCommand` instead of `AbstractUICommand` will give us some handy
  -methods to access and manipulate the project configuration:
  +This will basically create a command that can be called _envers-setup_ from the CLI (note the substitution of colons and spaces by hyphens) and as _Envers: Setup_ in the _Auditing_ category in the Forge wizard +
  +
  +As the newly created command will not require any input from the user, we will leave the `initializeUI` method empty. However, in order to implement the command execution behavior, we will need to change a little bit our class. More precisely we will have to extend from another abstract command class. The rationale behind this is that we want to update the *current* project POM, so extending `org.jboss.forge.addon.projects.ui.AbstractProjectCommand` instead of `AbstractUICommand` will give us some handy methods to access and manipulate the Project itself:
   
   [source, java]
   ----
  
positive.code:    }
  ----
  
  Next, we are going to make it possible running the setup command numerous times without polluting our POM file with as
  many dependencies to Hibernate Envers. For that we are going to use something as familiar - the DependencyFacet:
  
  [source, java]
  ----
  
negative.code: 
  ==== Installing and trying the Envers addon
  
  Once we have our basic functionality, we can build and install our new addon. For that we should use Forge's addons addon. It has a very handy command: _Addon: Build and install_. You can run it from the command line, or the IDE:
  
  [source, console]
  ----
  $ addon-build-and-install
  ----
  
  If you don't specify the `projectRoot` parameter, Forge will look for the sources of your addon in the current folder. If this is not the intended behavior, in the CLI run the command like that:
  
  [source, console]
  ----
  $ addon-build-and-install --projectRoot <path-to-the-addon-sources>
  ----
  
  In JBDS, either select the addon project before running the command, or specify the correct path in the command dialog:
  
  image::developing/addon-project-root.png[title="Specifying the addon project location"]
  
  This will trigger a build of the addon, and if it is successful, Forge will install it in its addon repository. You don't have to restart the tool; Forge it will automatically load the new software once it is deployed. After
  you see the success message, you can re-run the Forge quick access menu and will see the new command in the command list:
  
  image::developing/forge-envers-setup-command-wizard.png[title="_Envers: Setup_ command in the _Auditing_ category"]
  
  Now you can set up Hibernate Envers and open one of the JPA entities that you generated before starting to develop
  this addon, e.g. Country. You should be able to call now the other command. In the CLI:
  
  [source, console]
  