anchor.diff:  working with a small static graph that doesn't change much, writing unit tests and other use cases where the graph
   can fit in memory.
   
  -TIP: Resist the temptation to "get started" with more complex databases like link:http://thinkaurelius.github.io/titan/[Titan]
  -or to delve into how to get link:http://tinkerpop.apache.org/docs/x.y.z/reference/#gremlin-server[Gremlin Server]
  +TIP: For purposes of "getting started", resist the temptation to dig into more complex databases that have lots of
  +configuration options or to delve into how to get link:http://tinkerpop.apache.org/docs/x.y.z/reference/#gremlin-server[Gremlin Server]
   working properly. Focusing on the basics, presented in this guide, builds a good foundation for all the other things
   TinkerPop offers.
   
  -To make your process even easier, start with one of TinkerPop's "toy" graphs. These are "small" graphs designed to
  -provide a quick start into querying. It is good to get familiar with them, as almost all TinkerPop documentation is based
  -on them and when you need help and have to come to the link:http://groups.google.com/group/gremlin-users[mailing list],
  -a failing example put in the context of the toy graphs can usually get you a fast answer to your problem.
  +To make your learning process even easier, start with one of TinkerPop's "toy" graphs. These are "small" graphs
  +designed to provide a quick start into querying. It is good to get familiar with them, as almost all TinkerPop
  +documentation is based on them and when you need help and have to come to the
  +link:http://groups.google.com/group/gremlin-users[mailing list], a failing example put in the context of the toy graphs
  +can usually get you a fast answer to your problem.
  +
  +TIP: When asking questions on the mailing list or StackOverflow about Gremlin, it's is always helpful to include a
  +sample graph so that those attempting to answer your question understand exactly what kind of graph you have and can
  +focus their energies on a good answer rather than trying to build sample data themselves. The sample graph should just
  +be a simple Gremlin script that can be cut and paste into a Gremlin Console session.
   
   For your first graph, use the "Modern" graph which looks like this:
   
  
positive.code: 
  The use of `by()` here provides the mechanism by which to do the grouping. In this case, we've asked Gremlin to
  use the `label` (which, again, is an automatic static import from `T` in the console). We can't really tell much
  about our distribution though because we just have vertex unique identifiers as output. To make that nicer we
  could ask Gremlin to get us the value of the "name" property from those vertices, by supplying another `by()`
  modulator to `group()` to transform the values.
  
  
negative.code: 
  [gremlin-groovy,modern]
  ----
  g.V().has('name','marko').as('exclude').
    out('created').in('created').
    where(neq('exclude')).
    values('name')
  ----
  
  We made two additions to the traversal to make it exclude "marko" from the results. First, we added the
  