anchor.diff:  
   You can use the Journey Pattern with Serenity BDD in JUnit, Cucumber or JBehave. For simplicity, the examples will be using JUnit.
   
  -=== The Journey Pattern in Action ===
  +=== Introducing the Journey Pattern ===
   
   Suppose we are implementing the “Add new todo items” feature. This feature could have and acceptance criteria along the lines of “Should be able to add a new todo item”. If we were testing these scenarios manually, we could create test plans like the following:
  -* Should be able to add a new todo item
  -** Open the application
  -** Add an item called ‘Buy some milk’
  -** The ‘Buy some milk’ item should appear in the todo list
  +
  + * Should be able to add a new todo item
  + ** Open the application
  + ** Add an item called ‘Buy some milk’
  + ** The ‘Buy some milk’ item should appear in the todo list
   
   Using the Journey Pattern, we could write this code very naturally like this:
   
  
positive.code: }
  ----
  
  ===== Tasks can be used as building blocks by other tasks =====
  
  It is easy to reuse tasks in other, higher level tasks. For example, the sample project uses a AddTodoItems task to add a number of todo items to the list, like this:
  
  
negative.code: ----
  
  For more readability, we can also wrap the actor in a static method from the `GivenWhenThen` class:
  
   * givenThat()
   * andThat()
   * when()
   * then()
   * and()
   * but()
  
  For example, we could have written the last line of code like this:
  [source,java]
  