anchor.diff:    </tr>
     <tr>
       <td><a href="./ruby/index.html" class="subnav">Ruby</a></td>
  -    <td><p>Ruby, Rack, Rails, or Sinatra</p></td>
  +    <td><p>JRuby, Rack, Rails, or Sinatra</p></td>
       <td><a href="https://github.com/cloudfoundry/ruby-buildpack">Ruby source</a></td>
     </tr>
     <tr>
  
positive.code: 
  ## System Buildpacks
  
  This table describes Cloud Foundry system buildpacks. Each buildpack row lists supported languages and frameworks and includes a GitHub repo link. Specific buildpack names also link to additional documentation.
  
  <table border="1" class="nice" >
    <tr>
      <th>Name</th>
      <th>Other Supported Languages and Frameworks</th>
      <th>GitHub Repo</th>
    </tr>
    <tr>
  
negative.code: Buildpacks provide framework and runtime support for your applications.
  Buildpacks typically examine user-provided artifacts to determine what dependencies to download and how to configure applications to communicate with bound services.
  
  When you push an application, Cloud Foundry automatically [detects](./detection.html) which buildpack is required and installs it on the Diego Cell where the application needs to run.
  
  <p class="note"><strong>Note</strong>: Cloud Foundry deployments often have limited access to dependencies. This limitation occurs when the deployment is behind a firewall, or when administrators want to use local mirrors and proxies. In these circumstances, Cloud Foundry provides a <a href="https://github.com/cloudfoundry/buildpack-packager">
  Buildpack Packager</a> application.</p>
  
  The following topics contain information that might be relevant to your deployment:
  