anchor.diff:  "iterating your traversal" is described further in link:http://tinkerpop.apache.org/docs/x.y.z/tutorials/the-gremlin-console/[The Gremlin Console Tutorial].
   
   In this first five minutes with Gremlin, you've gotten the Gremlin Console installed, instantiated a `Graph` and
  -`TraversalSource`, wrote some traversals and hopefully learned something about TinkerPop in general. You've only
  +`TraversalSource`, written some traversals and hopefully learned something about TinkerPop in general. You've only
   scratched the surface of what there is to know, but those accomplishments will help enable your understanding of the
   more detailed sections to come.
   
  
positive.code: ----
  
  NOTE: The fully qualified name for `T` is `org.apache.tinkerpop.gremlin.structure.T`. Another important static import
  that is often seen in Gremlin comes from `org.apache.tinkerpop.gremlin.process.traversal.dsl.graph.__`, which allows
  for the creation of link:http://tinkerpop.apache.org/docs/x.y.z/reference/#graph-traversal-steps[anonymous traversals].
  
  Second, don't forget that you are working with TinkerGraph which allows for identifier assignment. That is _not_ the
  case with most graph databases.
  
  Finally, the label for an `Edge` is required and is thus part of the method signature of `addEdge()`. It is the first
  parameter supplied, followed by the `Vertex` to which `v1` should be connected. Therefore, this usage of `addEdge` is
  creating an edge that goes _out_ of `v1` and into `v2` with a label of "created".
  
  === Graph Traversal - Staying Simple
  
negative.code:   values('name')
  ----
  
  So that's nice, we can see that "peter", "josh" and "marko" are all responsible for creating "lop". Of course, we already
  know about the involvement of "marko" and it seems strange to say that "marko" collaborates with himself, so excluding
  "marko" from the results seems logical. The following traversal handles that exclusion:
  
  