anchor.diff:  == 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.+parts of a traversal and explains how they connect together. Understanding these component parts should help provide
  +more insight into how Gremlin works and help you grow in your Gremlin abilities.
  
positive.code: with a `VertexProgram` for OLAP based traversals - for example, see
  link:http://tinkerpop.apache.org/docs/x.y.z/reference/#sparkgraphcomputer[Spark]
  
  IMPORTANT: How you instantiate the `GraphTraversalSource` is highly depending on the graph database implementation that
  you are using. Typically, they are instantiated from a `Graph` instance with the `traversal()` method, but some graph
  databases, ones that are managed or "server-oriented", will simply give you a `g` to work with. Consult the
  documentation of your graph database to determine how the `GraphTraversalSource` is constructed.
  
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.
  