anchor.diff:  instance, but instead return the result of the `GraphTraversal`. In the case of the example, `next()` is the terminal
   step and it returns the `Map` constructed in the `groupCount()`-step. Other examples of terminal steps include:
   `hasNext()`, `toList()`, and `iterate()`. Without terminal steps, you don't have a result. You only have a
  -`GraphTraversal`
  +`GraphTraversal`.
   
   NOTE: You can read more about traversal iteration in the
   link:http://tinkerpop.apache.org/docs/x.y.z/tutorials/the-gremlin-console/#result-iteration[Gremlin Console Tutorial].
  
positive.code: == Conclusion
  
  There's much more to a traversal than just a bunch of steps. Gremlin's Anatomy puts names to each of these component
  parts of a traversal and explains how they connect together. Understanding these components part should help provide
  more insight into how Gremlin works and help you grow in your Gremlin abilities.
negative.code: values, and classes with static methods that might spawn certain required values.
  
  A concrete example would be the class from which `within()` is called - `P`. The `P` class spawns `Predicate` values
  that can be used as arguments for certain traversal steps. Another example would be the `T` enum which provides a type
  safe way to reference `id` and `label` keys in a traversal. Like anonymous traversals, these classes are usually
  statically imported so that instead of having to write `P.within()`, you can simply write `within()`, as shown in the
  example.
  