anchor.diff:  * The [cf Command Line Interface (CLI)](../../devguide/installcf/install-go-cli.html)
   * JDK 1.7 or 1.8 for Java 7 or 8 configured on your workstation
   
  -<p class="note"><strong>Note</strong>: You can develop Grails applications in Java 7 or 8 or any JVM language. The Cloud Foundry Java buildpack uses JDK 1.8, but you can modify the buildpack and the manifest for your app to compile to JDK 1.7. Refer to <a href="#configure-manifest">Step 8: Configure the Deployment Manifest</a>.</p>
  -
  -TBD: ARE MOST GRAILS APPS WRITTEN IN GROOVY?
  +<p class="note"><strong>Note</strong>: You can develop Grails applications in Groovy, Java 7 or 8, or any JVM language. The Cloud Foundry Java buildpack uses JDK 1.8, but you can modify the buildpack and the manifest for your app to compile to JDK 1.7. Refer to Step 8: Configure the Deployment Manifest.</p>
   
   ### Step 1: Add the Cloud Foundry Java Client Library to Your Project ###
   
  
positive.code: 
  The `config/open_jdk_jre.yml` file of the [Cloud Foundry Java buildpack](https://github.com/cloudfoundry/java-buildpack) contains default memory size and weighting settings for the JRE. See the [Open JDK JRE README](https://github.com/cloudfoundry/java-buildpack/blob/master/docs/jre-open_jdk_jre.md) on GitHub for an explanation of JRE memory sizes and weightings and how the Java buildpack calculates and allocates memory to the JRE for your app.
  
  To configure memory-related JRE options for your app, you create a custom buildpack and specify this buildpack in your deployment manifest. For more information on configuring custom buildpacks and manifests, see [Step 8: Configure the Deployment Manifest](#configure-manifest).
  
  When your app is running, you can use the `cf app [APP_NAME]` command to see memory utilization.
  
  
negative.code: <p class="note"><strong>Note</strong>: You do not have to include the <code>-p</code> flag when you deploy the sample app. The sample app manifest declares the path to the archive that <code>cf push</code> uses to upload the app files.
  </p>
  
  The example below shows the terminal output of deploying the <code>pong\_matcher\_grails</code> app. <code>cf push</code> uses the instructions in the manifest file to create the app, create and bind the route, and upload the app. It then binds the app to the <code>mysql</code> service and follows the instructions in the manifest to start two instances of the app, allocating 1 GB of memory between the instances. After the instances start, the output displays their health and status.
  
  <pre class="terminal">
  $ |master ✓| → cf push pong_matcher_grails -n my-grails-app
  