anchor.diff:  
   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
  +can see the former listens to changes on the latter and copying the values over. This happens every 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
  +Let's move to the View. Open up `ContainerView.java` and paste the following into it
   
   [source,java,options="nowrap"]
   .griffon-app/views/editor/ContainerView.java
  
positive.code: as is its responsibility to display the file's contents. One thing that must happen at some point is the new tab
  being added to the tab container. We can make this happen at the point where an instance of the `editor` MVC group
  is created; this requires the `EditorView` to expose its tab somehow. Or we can keep this behavior local to this
  group and make sure that this View handles adding and removing the tab. This is the reason why we exposed the _tabCount_
  field in `ContainerView`. Let's look at the `EditorView`, shall we?
  
  [source,java,options="nowrap"]
  
negative.code: include::{editor-swing-java}/griffon-app/views/editor/ContainerView.java[lines=16..-1]
  ----
  
  Here we find a `Window` object containing a `JMenuBar` and a tab container (a `JTabbedPane`) named _tabGroup_.
  This tab container is exposed to the outside world via a getter method; we'll see why it's done this way when the
  second MVC group comes into play. The View is also responsible for managing a `JFileChooser` that will be used to
  select files for reading. Notice the conditional enabling of the `save` action given the state of the `dirty` property
  