anchor.diff:  	</plugin>
   ----
   
  -Then deploy with `mvn appengine:deploy` (if you need to authenticate first the build will
  -fail).
  -
  -NOTE: Google App Engine Classic is tied to the Servlet 2.5 API, so you can't deploy a
  +Then deploy with `mvn appengine:deploy` (if you need to authenticate first, the build
  +fails).
  +
  +NOTE: Google App Engine Classic is tied to the Servlet 2.5 API, so you cannot deploy a
   Spring Application there without some modifications. See the
  -<<howto.adoc#howto-servlet-2-5, Servlet 2.5 section>> of this guide.
  +<<howto.adoc#howto-servlet-2-5,Servlet 2.5 section>> of this guide.
   
   
   
   [[deployment-install]]
  -== Installing Spring Boot applications
  -In additional to running Spring Boot applications using `java -jar` it is also possible
  +== Installing Spring Boot Applications
  +In additional to running Spring Boot applications by using `java -jar`, it is also possible
   to make fully executable applications for Unix systems. A fully executable jar can be
   executed like any other executable binary or it can be <<deployment-service,registered
   with `init.d` or `systemd`>>. This makes it very easy to install and manage Spring Boot
   applications in common production environments.
   
   WARNING: Fully executable jars work by embedding an extra script at the front of the
  -file. Currently, some tools do not accept this format so you may not always be able to
  +file. Currently, some tools do not accept this format, so you may not always be able to
   use this technique. For example, `jar -xf` may silently fail to extract a jar or war that
  -has been made fully-executable. It is recommended that you only make your jar or war
  +has been made fully executable. It is recommended that you only make your jar or war
   fully executable if you intend to execute it directly, rather than running it with
   `java -jar` or deploying it to a servlet container.
   
  -To create a '`fully executable`' jar with Maven use the following plugin configuration:
  +To create a '`fully executable`' jar with Maven, use the following plugin configuration:
   
   [source,xml,indent=0,subs="verbatim,quotes,attributes"]
   ----
  
positive.code: 
  
  [[deployment-script-customization]]
  ==== Customizing the startup script
  The default embedded startup script written by the Maven or Gradle plugin can be
  customized in a number of ways. For most people, using the default script along with
  a few customizations is usually enough. If you find you can't customize something that
  you need to, you can always use the `embeddedLaunchScript` option to write your own
  file entirely.
  
  
  
  [[deployment-script-customization-when-it-written]]
  ===== Customizing script when it's written
  It often makes sense to customize elements of the start script as it's written into the
  jar file. For example, init.d scripts can provide a "`description`" and, since you know
  this up front (and it won't change), you may as well provide it when the jar is generated.
  
  To customize written elements, use the `embeddedLaunchScriptProperties` option of the
  Spring Boot Maven or Gradle plugins.
  
negative.code: 	</plugin>
  ----
  
  The following example shows the equivalent Gradle configuration:
  
  [source,groovy,indent=0,subs="verbatim,quotes,attributes"]
  ----
  