anchor.diff:  UberFire Workbench Concepts
   ~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
  -These concepts are expressed in the `uberfire-workbench` package,
  +These concepts are expressed in the `UberFire-workbench` package,
   which provides annotation processors for the core annotations in
  -`uberfire-client-api`, as well as the foundation for the client-side
  +`UberFire-client-api`, as well as the foundation for the client-side
   MVP (model, view, presenter) framework.
   
   * The Workbench widget hierarchy: App Widget < Workbench < Container < { Headers, Workbench Container < The Workbench Root Panel }
  
positive.code: UberFire Client API Concepts
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  
  These concepts are expressed in the `uberfire-client-api` package,
  which defines an API that's only accessible to client-side
  (in-browser) code.
  
  * Default Position
  * Perspective
  * Workbench things: Context, Context ID, Editor, Menu, Title, TitleDecoration, View, Popup, Screen, Tool Bar
  * `UberView`, a way of injecting MVP presenters into views
  * `UberFirePreferences`, a public global map
  * Resource types: Any, Client, and Dot
  * Client Type Registry
  
  
  UberFire Commons Concepts
  ~~~~~~~~~~~~~~~~~~~~~~~~~
  
  These concepts are expressed in the `uberfire-commons` package,
  which contains a mix of server-only definitions shared client/server definitions.
  
  * Clustering (server-only, see also UberFire I/O)
  
negative.code: UberFire Metadata Concepts
  ~~~~~~~~~~~~~~~~~~~~~~~~~~
  
  These concepts are expressed in the `UberFire-metadata` package,
  which appears to be a full-text search and indexing feature (TODO: is this correct?)
  
  The UberFire Metadata module includes an API submodule which defines
  