anchor.diff:  $ java -jar myapp-swarm.jar -s/home/app/openshift.yml -Scloud -Stesting
   ----
   
  -In this example, the following YAML files are loaded in this order:
  +The following YAML files are loaded, in this order:
   
   . `/home/app/openshift.yml`
   . `project-cloud.yml`
   . `project-testing.yml`
   . `project-defaults.yml`
   
  -The same order of preference is applied even when the application is invoked as follows:
  +The same order of preference is applied even if you invoke the application as follows:
   
   [source,bash]
   ----
  
positive.code: ====
  The configuration item documented as `swarm.undertow.servers.KEY.default-host` indicates that the configuration applies to a particular named server.
  
  In practical usage, the property would be, for example, `swarm.undertow.servers.default.default-host`, for a server known as `default`.
  ====
  
  [discrete]
  
negative.code: [#configuring-a-wildfly-swarm-application]
  = Configuring a WildFly Swarm application
  
  You can configure numerous options with applications built with WildFly Swarm.
  For all options, reasonable defaults are already applied, so you do not have to change any options unless you explicitly want to.
  
  This reference is a complete list of all configurable items, grouped by the fraction that introduces them.
  Only the items related to the fractions that your application uses are relevant to you.
  
  [#configuring-an-application-using-properties]
  == Configuring an application using properties
  
  Here, configuration items are presented using dotted notation, and are suitable for use as Java property names, which your application consumes through explicit setting in the Maven plugin configuration, or through the command line when your application is being executed.
  
  Any property that has the _KEY_ parameter in its name indicates that you must supply a key or identifier in that segment of the name.
  
  