anchor.diff:  
   ## <a id='http-2'></a> HTTP/2
   
  -Java applications can be deployed on Cloud Foundry and use HTTP/2. There are two requirements.
  -
  -1. A Cloud Foundry foundation that has HTTP/2 support enabled. <%= vars.http2_admin_link %>
  -2. Version 8+ of the cf cli.
  -
  -Without any changes to your application, you can deploy any Java application and get automatic support for the HTTP/2 protocol. A client can connect through routes mapped to your Java applications over HTTP/2, and the foundation will transparently downgrade the protocol and communicate with your application over HTTP/1.1.
  -
  -If you require end-to-end HTTP/2, for example because of gRPC, you will need to take some additional steps.
  -
  -1. The application needs to enable support for HTTP/2.
  -    - <a href="https://docs.spring.io/spring-boot/docs/current/reference/html/howto.html#howto.webserver.configure-http2">Spring Boot instructions to enable HTTP/2 support in the application</a>.
  -    - If you are deploying a standard non-executable WAR file, you only need to ensure you are using version 4.43 or newer of the Java buildpack. Starting with 4.43, the Java buildpack will configure Apache Tomcat to accept HTTP/2 connections.
  -    - For other frameworks like Play and Ratpack or for apps utilizing the Dist Zip format, these also embed an HTTP server and need to be configured to enable HTTP/2 (specifically H2C, clear-text). See your framework's documentation for enabling HTTP/2 and H2C (only H2C is required because Cloud Foundry uses Envoy to secure communications into the application container).
  -2. You need to configure the route to use the HTTP/2 protocol.
  -    - Using the cf cli: `cf map-route MY-APP EXAMPLE.COM --hostname host --destination-protocol http2`.
  +To deploy Java apps that use HTTP/2 on <%= vars.app_runtime_abbr %>, you must have:
  +
  +1. A <%= vars.app_runtime_abbr %> foundation that has HTTP/2 support enabled. <%= vars.http2_admin_link %>
  +2. Cloud Foundry Command-Line Interface (cf CLI) v8 or later. See [Upgrading to cf CLI v8](../../cf-cli/v8.html).
  +
  +You can deploy any Java app and get automatic support for the HTTP/2 protocol without making any changes to your app.
  +When a client connects through a route mapped to your Java apps over HTTP/2, the foundation transparently downgrades the protocol and communicates with your app over HTTP/1.1.
  +
  +If you require end-to-end HTTP/2, for example, because of gRPC, do the following:
  +
  +1. Enable HTTP/2 support in the app:
  +    - See <a href="https://docs.spring.io/spring-boot/docs/current/reference/html/howto.html#howto.webserver.configure-http2">Configure HTTP/2</a> in the Spring Boot documentation.
  +    - If you are deploying a standard non-executable WAR file, you only need to make sure that you are using Java buildpack v4.43 or later. Starting with v4.43, the Java buildpack configures Apache Tomcat to accept HTTP/2 connections.
  +    - Other frameworks, including Play, Ratpack, and apps that use the distZip format, embed an HTTP server. You must configure these apps to enable HTTP/2, specifically H2C, clear-text. See your framework's documentation for enabling HTTP/2 and H2C.
  +    <p class="note"><strong>Note</strong>: H2C is required because <%= vars.app_runtime_abbr %> uses Envoy to secure communications into the app container.</p>
  +2. Configure the route to use the HTTP/2 protocol using either the cf CLI or the app manifest:
  +    - Using the cf CLI: `cf map-route MY-APP EXAMPLE.COM --hostname host --destination-protocol http2`.
       - Using a `manifest.yml` file:
   
           ```
  
positive.code:         * Delete `manifest.yml` and run `cf push` again, specifying the location of the WAR using the `-p` flag.
          * Edit the `path` argument in `manifest.yml` to point to the WAR, and re-push the app.
  
  ### <a id='debugging'></a> Debug Java Apps on Cloud Foundry
  
  Because of the way that Cloud Foundry deploys your apps and isolates them, it is not possible to connect to your app with the remote Java debugger. Instead, instruct the app to connect to the Java debugger on your local machine.
  
  To set up remote debugging when using BOSH Lite or a Cloud Foundry installation:
  
  1. Open your project in Eclipse.
  
  
negative.code: 
  ## <a id='groovy'></a> Groovy
  
  <%= vars.app_runtime_abbr %> supports Groovy apps based on both Ratpack and a simple collection of files.
  
  ### <a id='ratpack'></a> Ratpack
  
  Ratpack packages apps into two different styles. <%= vars.app_runtime_abbr %> supports the `distZip` style. To build the ZIP file and deploy it, run:
  
  ```
  gradle distZip
  