anchor.diff:  
   image:grateful-gremlin.png[float=right,width=110] As you might have noticed from the diagrams of these graphs or from
   the output of the Gremlin Console itself, these toy graphs are small (only a few vertices and edges each). It is nice
  -to have a small graph when learning Gremlin so that you can easily see if you are getting the results you expect. Even
  +to have a small graph when learning Gremlin, so that you can easily see if you are getting the results you expect. Even
   though these graphs are "small", they are robust enough in structure to try out many different kinds of traversals.
   However, if you find that a larger graph might be helpful, there is another option: The Grateful Dead
   (link:http://tinkerpop.apache.org/docs/x.y.z/images/grateful-dead-schema.png[schema]).
  
positive.code: link:http://groups.google.com/group/gremlin-users[Gremlin Users mailing list] about a traversal that you are having
  trouble with in your application, try to convert the gist of it to one of the toy graphs.  Taking this step will make it
  easier for advanced Gremlin users to help you, which should lead to a faster response time for your problem. In
  addition, there is the added benefit that the mailing list post will likely be more relevant to other users, as it is
  not written solely in the context of your domain.
  
  [[help]]
  
negative.code: inspire you to new levels of usage. While a use case may not fit your needs, you may well find it worthwhile to
  read, as it is possible that a "feature" will be discussed that may be useful to you.
  
  The following points summarize the key features discussed in each use case:
  
  * <<learning-tool,A Learning Tool>>
  ** Introducing the <<toy-graphs,toy graphs>>
  