anchor.diff:  include::{projectdir}/src/spec/test/SyntaxTest.groovy[tags=multiline_comment,indent=0]
   ----
   
  -=== GroovyDoc comment
  -
  -Similarly to multiline comments, GroovyDoc comments are multiline, but start with `/\**` and end with `*/`.
  -Lines following the first GroovyDoc comment line can optionally start with a star `*`.
  +=== Groovydoc comment
  +
  +Similarly to multiline comments, Groovydoc comments are multiline, but start with `/\**` and end with `*/`.
  +Lines following the first Groovydoc comment line can optionally start with a star `*`.
   Those comments are associated with:
   
   * type definitions (classes, interfaces, enums, annotations),
   * fields and properties definitions
   * methods definitions
   
  -Although the compiler will not complain about GroovyDoc comments not being associated with the above language elements,
  +Although the compiler will not complain about Groovydoc comments not being associated with the above language elements,
   you should prepend those constructs with the comment right before it.
   
   [source,groovy]
  
positive.code: include::{projectdir}/src/spec/test/SyntaxTest.groovy[tags=groovydoc_comment,indent=0]
  ----
  
  GroovyDoc follows the same conventions as Java's own JavaDoc.
  So you'll be able to use the same tags as with JavaDoc.
  
  === Shebang line
  
  Beside the single line comment, there is a special line comment, often called the _shebang_ line understood by UNIX systems
  which allows scripts to be run directly from the command-line, provided you have installed the Groovy distribution
  and the `groovy` command is available on the `PATH`.
  
  
negative.code: 
  == Comments
  
  === Single-line comment
  
  Single-line comments start with `//` and can be found at any position in the line.
  The characters following `//`, until the end of the line, are considered part of the comment.
  
  [source,groovy]
  ----
  