anchor.diff:  
   ==== Traversal Wrappers
   
  -While it is possible to simply interact with Java classes in a `ScriptEngine` implementation, such Gremlin language variants
  -will not leverage the unique features of the host language. It is for this reason that JVM-based language variants such as
  -link:https://github.com/mpollmeier/gremlin-scala[Gremlin-Scala] were developed. Scala provides many syntax niceties not
  -available in Java. To leverage these niceties, Gremlin-Scala "wraps" `GraphTraversal` in order to provide Scala-idiomatic extensions.
  -Another example is Apache TinkerPop's Gremlin-Groovy which does the same via the
  +While it is possible to simply interact with Java classes in a `ScriptEngine` implementation, such Gremlin language
  +variants will not leverage the unique features of the host language. It is for this reason that JVM-based language
  +variants such as link:https://github.com/mpollmeier/gremlin-scala[Gremlin-Scala] were developed. Scala provides many
  +syntax niceties not available in Java. To leverage these niceties, Gremlin-Scala "wraps" `GraphTraversal` in order to
  +provide Scala-idiomatic extensions. Another example is Apache TinkerPop's Gremlin-Groovy which does the same via the
   link:http://tinkerpop.apache.org/docs/x.y.z/reference/#sugar-plugin[Sugar plugin], but uses
  -link:http://groovy-lang.org/metaprogramming.html[meta-programming] instead of object wrapping, where "behind the scenes,"
  -Groovy meta-programming is doing object wrapping.
  -
  -The Jython example below uses Python meta-programming to add functionality to `GraphTraversal`.
  -In particular, the `__getitem__` and `__getattr__` "magic methods" are leveraged.
  +link:http://groovy-lang.org/metaprogramming.html[meta-programming] instead of object wrapping, where "behind the
  +scenes," Groovy meta-programming is doing object wrapping.
  +
  +The Jython example below uses Python meta-programming to add functionality to `GraphTraversal`. In particular, the
  +`__getitem__` and `__getattr__` "magic methods" are leveraged.
   
   [source,python]
   ----
  
positive.code: GraphTraversal.__getattr__ = lambda self, key: self.values(key)
  ----
  
  The two methods `__getitem__` and `__getattr__` support Python _slicing_ and _object attribute interception_, respectively.
  In this way, the host language is able to use its native constructs in a meaningful way within a Gremlin traversal.
  
  IMPORTANT: Gremlin-Java serves as the standard/default representation of the Gremlin traversal language. Any Gremlin
  language variant **must** provide all the same functionality (methods) as `GraphTraversal`, but **can** extend it
  
negative.code: ----
  
  In query languages like link:https://en.wikipedia.org/wiki/SQL[SQL], the user must construct a string representation of
  their query and submit it to the database for evaluation. This is because SQL cannot be expressed in Java as they use
  fundamentally different constructs in their expression. The same example above is presented below using SQL and the
  link:https://en.wikipedia.org/wiki/Java_Database_Connectivity[JDBC] interface. The take home point is that Gremlin does
  not exist outside the programming language in which it will be used. Gremlin was designed to be able to be
  embedded in any modern programming language and thus, always free from the complexities of string manipulation as seen
  