anchor.diff:  
   *Resources*
   
  -* http://docs.oracle.com/javase/6/docs/technotes/guides/language/assert.html[Programming With Assertions] - a guide from Oracle.
  -* http://stackoverflow.com/questions/5509082/eclipse-enable-assertions[How to enable assertions in Eclipse]
  +* https://se-edu.github.io/se-book/errorHandling/assertions/[se-edu/se-book: Implementation: Error Handling: Assertions]
   
   === Exercise: Add more assertions
   
  -* Make sure assertions are enabled in Eclipse by forcing an assertion failure (e.g. add `assert false;` somewhere in the code and run the code
  -to ensure the runtime reports an assertion failure).
  +* Make sure assertions are enabled in your IDE by forcing an assertion failure (e.g. add `assert false;` somewhere in the code and run the code to ensure the runtime reports an assertion failure).
   * Add more assertions to AddressBook as you see fit.
   
   
  
positive.code: 
  Note how the <<DeveloperGuide#architecture, Developer Guide>> describes the high-level design using an _Architecture Diagrams_ and high-level sequence diagrams.
  
  '''
  
  == Use Event-Driven Programming `[LO-EventDriven]`
  
  Note how the <<DeveloperGuide#architecture, Developer Guide>> uses events to communicate with components without needing a direct coupling. Also note how the `EventsCenter` class acts as an event dispatcher to facilitate communication between event creators and event consumers.
  
  '''
  
  
negative.code: 
  *Resources*
  
  * https://se-edu.github.io/se-book/integration/buildAutomation/what/[se-edu/se-book: Implementation: Integration: Build Automation: What]
  
  === Exercise: Use gradle to run tasks
  
  