anchor.diff:   in the script.
   
   |`STOP_WAIT_TIME`
  -|The time in seconds to wait when stopping the application before forcing a shutdown
  - (`60` by default).
  +|The time in seconds to wait when stopping the application before forcing a shutdown (`60`
  + by default).
   |===
   
   NOTE: The `PID_FOLDER`, `LOG_FOLDER`, and `LOG_FILENAME` variables are only valid for an
  -`init.d` service. For `systemd`, the equivalent customizations are made by using the '`service`'
  -script. See the
  +`init.d` service. For `systemd`, the equivalent customizations are made by using the
  +'`service`' script. See the
   http://www.freedesktop.org/software/systemd/man/systemd.service.html[service unit
   configuration man page] for more details.
   
   [[deployment-script-customization-conf-file]]
  -With the exception of `JARFILE` and `APP_NAME`, the above settings can be configured by using
  -a `.conf` file. The file is expected to be next to the jar file and have the same name but
  -suffixed with `.conf` rather than `.jar`. For example, a jar named `/var/myapp/myapp.jar`
  -uses the configuration file named `/var/myapp/myapp.conf`.
  +With the exception of `JARFILE` and `APP_NAME`, the above settings can be configured by
  +using a `.conf` file. The file is expected to be next to the jar file and have the same
  +name but suffixed with `.conf` rather than `.jar`. For example, a jar named
  +`/var/myapp/myapp.jar` uses the configuration file named `/var/myapp/myapp.conf`.
   
   .myapp.conf
   [indent=0,subs="verbatim,quotes,attributes"]
  
positive.code: [[cloud-deployment-cloud-foundry]]
  === Cloud Foundry
  Cloud Foundry provides default buildpacks that come into play if no other buildpack is
  specified. The Cloud Foundry https://github.com/cloudfoundry/java-buildpack[Java buildpack]
  has excellent support for Spring applications, including Spring Boot. You can deploy
  stand-alone executable jar applications as well as traditional `.war` packaged
  applications.
  
  Once you have built your application (by using, for example, `mvn clean package`) and have
  http://docs.cloudfoundry.org/devguide/installcf/install-go-cli.html[installed the `cf`
  command line tool], deploy your application by using the `cf push` command,
  substituting the path to your compiled `.jar`. Be sure to have
  http://docs.cloudfoundry.org/devguide/installcf/whats-new-v6.html#login[logged in with your
  `cf` command line client] before pushing an application. The following line shows using
  the `cf push` command to deploy an application:
  
  [indent=0,subs="verbatim,quotes,attributes"]
  ----
  	$ cf push acloudyspringtime -p target/demo-0.0.1-SNAPSHOT.jar
  ----
  
  NOTE: In the preceding example, we substitute `acloudyspringtime` for whatever value you give `cf`
  as the name of your application.
  
  See the http://docs.cloudfoundry.org/devguide/installcf/whats-new-v6.html#push[`cf push`
  documentation] for more options. If there is a Cloud Foundry
  
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.
  