anchor.diff:  [appendix]
   [[executable-jar]]
  -== The executable jar format
  -The `spring-boot-loader` modules allows Spring Boot to support executable jar and
  -war files. If you're using the Maven or Gradle plugin, executable jars are
  -automatically generated and you generally won't need to know the details of how
  +== The Executable Jar Format
  +The `spring-boot-loader` modules lets Spring Boot support executable jar and
  +war files. If you use the Maven plugin or the Gradle plugin, executable jars are
  +automatically generated, and you generally do not need to know the details of how
   they work.
   
  -If you need to create executable jars from a different build system, or if you are just
  +If you need to create executable jars from a different build system or if you are just
   curious about the underlying technology, this section provides some background.
   
   
   
   [[executable-jar-nested-jars]]
   === Nested JARs
  -Java does not provide any standard way to load nested jar files (i.e. jar files that
  -are themselves contained within a jar). This can be problematic if you are looking
  -to distribute a self-contained application that you can just run from the command line
  +Java does not provide any standard way to load nested jar files (that is, jar files that
  +are themselves contained within a jar). This can be problematic if you need
  +to distribute a self-contained application that can be run from the command line
   without unpacking.
   
  -To solve this problem, many developers use "`shaded`" jars. A shaded jar simply packages
  -all classes, from all jars, into a single 'uber jar'. The problem with shaded jars is
  -that it becomes hard to see which libraries you are actually using in your application.
  +To solve this problem, many developers use "`shaded`" jars. A shaded jar packages
  +all classes, from all jars, into a single "`uber jar`". The problem with shaded jars is
  +that it becomes hard to see which libraries are actually in your application.
   It can also be problematic if the same filename is used (but with different content)
  -in multiple jars. Spring Boot takes a different approach and allows you to actually nest
  +in multiple jars. Spring Boot takes a different approach and lets you actually nest
   jars directly.
   
   
   
   [[executable-jar-jar-file-structure]]
  -==== The executable jar file structure
  -Spring Boot Loader compatible jar files should be structured in the following way:
  +==== The Executable Jar File Structure
  +Spring Boot Loader-compatible jar files should be structured in the following way:
   
   [indent=0]
   ----
  
positive.code: 
  
  [[executable-jar-jarfile]]
  === Spring Boot's "`JarFile`" class
  The core class used to support loading nested jars is
  `org.springframework.boot.loader.jar.JarFile`. It allows you to load jar
  content from a standard jar file, or from nested child jar data. When first loaded, the
  location of each `JarEntry` is mapped to a physical file offset of the outer jar:
  
  [indent=0]
  ----
  
negative.code: 	Start-Class: com.mycompany.project.MyApplication
  ----
  
  For a war file, it would be as follows:
  
  [indent=0]
  ----
  