anchor.diff:  RETURN e.name
   ----
   
  -. Prefer single nouns for labels.
  -+
  -.Bad
  -[source, cypher]
  -----
  -MATCH (e:IsEmployed)
  -RETURN e.name
  -----
  -+
  -.Good
  -[source, cypher]
  -----
  -MATCH (e:Employee)
  -RETURN e.name
  -----
  -
   . Write relationship types in upper case, using underscore to separate words.
   +
   .Bad
  
positive.code: 
  == Rules
  
  Whenever two rules are in conflict, use the order to decide which one trumps.
  
  // Template:
  //. rule
  
negative.code: ----
  RETURN 1
  ----
  
  == Recommendations
  
  * When using Cypher language constructs in prose, use a monospaced font and follow the styling rules.
  ** When referring to labels and relationship types, include the colon like so: `:Label`, `:REL_TYPE`.
  ** When referring to functions, use lower camel case and parentheses like so: `shortestPath()`. Arguments should normally not be included.
  * If you are storing Cypher statements in a separate file, use the file extension `.cypher`.
  
  === Graph modelling
  
  . Prefer single nouns for labels.
  +
  .Bad
  [source, cypher]
  ----
  MATCH (e:IsEmployed)
  RETURN e.name
  ----
  +
  .Good
  [source, cypher]
  ----
  MATCH (e:Employee)
  RETURN e.name
  ----
  