anchor.diff:  
   For more information, refer to the [Build Tool Integration](./build-tool-int.html) topic.
   
  -<p class="tip"><strong>Sample App Step</strong><br />You can skip this step. The <code>pong_matcher_grails</code> sample app includes a <code>Dockerfile</code> file.</p>
  +<p class="tip"><strong>Sample App Step</strong><br />You can skip this step. The <code>pong_matcher_grails</code> sample app includes <code>Dockerfile</code> and <code>BuildConfig.groovy</code> files to build the app and does not require additional external plugin integration.</p>
   
   ### Step 3: Declare App Dependencies ###
   
  -Declare all the dependency tasks for your app in the build script of your chosen build tool. The table lists build script information for Gradle and Maven and provides documentation links for each build tool.
  +Declare all the dependency tasks for your app in the build script of your chosen build tool. The table lists build script information for Gradle, Grails, and Maven and provides documentation links for each build tool.
   
   <table border="1" class="nice">
   <tr>
  
positive.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 the health and status of the instances.
  
  <pre class="terminal">
  $ |master ✓| → cf push pong_matcher_grails -n my-grails-app
  
negative.code: * Include the appropriate driver in your application.
  * Create a dependency task for the driver in the build script for your build tool or IDE.
  
  <p class="tip"><strong>Sample App Step</strong><br />You can skip this step. The <code>pong_matcher_grails</code> sample app declares a MySQL JDBC driver in the <code>pong_matcher_grails/app/grails-app/conf/DataSource.groovy</code> file because the app uses ClearDB, which is a database-as-service for MySQL-powered apps. The example below shows this declaration.</p>
  
  <!-- <%= yield_for_code_snippet from: 'camelpunch/pong_matcher_grails', at: 'gsg-grails-s5' %> -->
  
  ### Step 6: (Optional) Configure a Procfile ###
  
  