anchor.diff:  	}
   ----
   
  -You can then run your application by typing `./my-application.jar` (where
  -`my-application` is the name of your artifact). The directory containing the
  -jar is used as your application's working directory.
  +You can then run your application by typing `./my-application.jar` (where `my-application`
  +is the name of your artifact). The directory containing the jar is used as your
  +application's working directory.
   
   [[deployment-install-supported-operating-systems]]
   === Supported Operating Systems
  -The default script supports most Linux distributions and is tested on CentOS and
  -Ubuntu. Other platforms, such as OS X and FreeBSD, require the use of a custom
  +The default script supports most Linux distributions and is tested on CentOS and Ubuntu.
  +Other platforms, such as OS X and FreeBSD, require the use of a custom
   `embeddedLaunchScript`.
   
   
   
   [[deployment-service]]
   === Unix/Linux Services
  -Spring Boot application can be easily started as Unix/Linux services by using either `init.d`
  -or `systemd`.
  +Spring Boot application can be easily started as Unix/Linux services by using either
  +`init.d` or `systemd`.
   
   
   [[deployment-initd-service]]
   ==== Installation as an `init.d` Service (System V)
  -If you configured Spring Boot's Maven or Gradle plugin to generate a
  -<<deployment-install,fully executable jar>>, and you do not use a custom
  -`embeddedLaunchScript`, your application can be used as an `init.d` service. To do so,
  -symlink the jar to `init.d` to support the standard `start`, `stop`, `restart` and
  -`status` commands.
  +If you configured Spring Boot's Maven or Gradle plugin to generate a <<deployment-install,
  +fully executable jar>>, and you do not use a custom `embeddedLaunchScript`, your
  +application can be used as an `init.d` service. To do so, symlink the jar to `init.d` to
  +support the standard `start`, `stop`, `restart` and `status` commands.
   
   The script supports the following features:
   
  
positive.code: more options. If there is a https://boxfuse.com/docs/commandline/#configuration
  [`boxfuse.conf`] file present in the current directory, it is considered.
  
  TIP: By default, Boxfuse activates a Spring profile named `boxfuse` on startup. If
  your executable jar or war contains an
  https://boxfuse.com/docs/payloads/springboot.html#configuration
  [`application-boxfuse.properties`]
  file, Boxfuse bases its configuration based on the properties it contains.
  
  At this point, `boxfuse` creates an image for your application, uploads it, and
  configures and starts the necessary resources on AWS resulting in output similar to the
  following example:
  
  [indent=0,subs="verbatim,quotes,attributes"]
  ----
  
negative.code: 
  |`inlinedConfScript`
  |Reference to a file script that should be inlined in the default launch script.
   This can be used to set environmental variables such as `JAVA_OPTS` before any external
   config files are loaded.
  
  |`logFolder`
  |The default value for `LOG_FOLDER`. Only valid for an `init.d` service.
  