anchor.diff:  -d language=groovy -d type=gradle-project -d baseDir=another-project | tar -xzvf -
   ----
   
  -NOTE: The `/starter.tgz` endpoint offers the same feature as `/starter.zip` but generates
  -a compressed tarball instead.
  -
  -You could use this infrastructure to create your own client since the project is generated
  -via a plain HTTP call.
  +NOTE: The `/starter.tgz` endpoint offers the same feature as `/starter.zip` but
  +generates a compressed tarball instead.
  +
  +You could use this infrastructure to create your own client since the project is
  +generated via a plain HTTP call.
   
   [[customize-form]]
   == Customize form inputs
   
  -You can share or bookmark URLs that will automatically customize form inputs. For instance,
  -the following URL from the default instance uses `groovy` by default and set the name
  -to `Groovy Sample`:
  +You can share or bookmark URLs that will automatically customize form inputs. For
  +instance, the following URL from the default instance uses `groovy` by default and
  +set the name to `Groovy Sample`:
   
   [source,bash]
   ----
   https://start.spring.io/#!language=groovy&name=Groovy%20Sample
   ----
   
  -The following hashbang parameters are supported: `type`, `groupId`, `artifactId`, `name`,
  -`description`, `packageName`, `packaging`, `javaVersion` and `language`. Review the section
  -above for a description of each of them.
  +The following hashbang parameters are supported: `type`, `groupId`, `artifactId`,
  +`name`, `description`, `packageName`, `packaging`, `javaVersion` and `language`.
  +Review the section above for a description of each of them.
   
   [[metadata]]
   == Service metadata
  
positive.code: $ curl -H 'Accept: application/json' https://start.spring.io
  ----
  
  NOTE: As stated above, if you use `curl` without an accept header, you'll retrieve a human
  readable text version of the metadata. `HTTPie` is also supported:
  
  [source,bash]
  ----
  $ http https://start.spring.io Accept:application/json
  ----
  
  
  
  The metadata basically lists the _capabilities_ of the service, that is the available
  options for all request parameters (`dependencies`, `type`, `bootVersion`, etc.) The web
  UI uses that information to initialize the select options and the tree of available
  dependencies.
  
  The metadata also lists the default values for simple _text_ parameter (i.e. the default
  `name` for the project).
  
  NOTE: More details about the structure of the metadata are {wiki}/Metadata-format[available
  on the wiki].
  
  == Running your own instance
  
  You can easily run your own instance. The `initializr-web` modules uses Spring Boot so when it
  is added to a project, it will trigger the necessary auto-configuration to deploy the service.
  
  You first need to create or update your configuration to define the necessary attributes that
  your instance will use. Again, check the wiki for a {wiki}/Configuration-format[description
  of the configuration] and {code}/initializr-service/application.yml[review our own config] for
  a sample.
  
  You can integrate the library in a traditional Java-based project or by writing the super-simple
  script below
  
  [source,groovy]
  ----
  
negative.code: [[run-app]]
  === Running the app locally
  
  Once you have <<building, built the library>>, you can easily start the app as any
  other Spring Boot app from the `initializr-service` directory:
  
  [indent=0]
  ----
  