anchor.diff:   * MVC Group parent-child relationships
    * MVC Group lifecycle
   
  -The goal of the Editor application shown here is to be provide basic editing capabilities fo text files. Each
  +The goal of the Editor application shown here is to provide basic editing capabilities for text files. Each
   file will be handled by its own tab; tabs will be located inside a tab container.
   
   . <<_tutorial_2_1,Creating an Editor application>>
  
positive.code: 
  Notice that the _documentModel_ property is declared as final; this means it will always have the same value, thus we
  can use it to create stable bindings. This is the reason for making `DocumentModel` a subclass of `Document`. As you
  can see the former listens to changes on the latter and copying the values over. This happens very time the application
  changes the value of _documentModel.document_ due to the ``PropertyChangeListener``s that were put into place.
  
  The final remark on this model class is that it implements the `javax.swing.event.ChangeListener` interface. In this
  way the model instance can listen to tab selection changes and update the _documentModel_ property.
  
  Let's mode to the View. Open up `ContainerView.java` and paste the following into it
  
  [source,java,options="nowrap"]
  .griffon-app/views/editor/ContainerView.java
  
negative.code: application. We select `editor` as the name of the new MVC group. There are 5 new files generated using the
  default templates. Take special care of the last message; the files were created but this doesn't mean the application
  will be able to instantiate the MVC group at runtime. The final piece of the puzzle is letting the application know
  about this new MVC group, this is done by editing `Config.java`
  
  [source,java,options="nowrap"]
  .griffon-app/conf/Config.java
  