Hey cgfrost!

Thanks for submitting this pull request! I'm here to inform the recipients of the pull request that you've already signed the CLA.

@cgfrost You've pushed your master again which means that there's some stuff hanging off the end of the intended commit. Beyond that, some changes that need to be made:

1. Expert mode does not require a full replica of the online repository. That is the easiest way to create an internal repository, but is not required. The only things that are required are indexes for the components that will be used, pointing to locations that the artifacts can be downloaded from.
2. Typo in the word "dose't"
3. You don't have to clone the repository to build a packaged buildpack. There are a number of other options.
4. Cloning
5. Tarball (https://github.com/cloudfoundry/java-buildpack/archive/master.tar.gz)
6. Zip (https://github.com/cloudfoundry/java-buildpack/archive/master.zip)
7. Release offline package (https://github.com/cloudfoundry/java-buildpack/releases/download/v2.4/java-buildpack-offline-v2.4.zip)
8. Release tarball (https://github.com/cloudfoundry/java-buildpack/archive/v2.4.tar.gz)
9. Release zip (https://github.com/cloudfoundry/java-buildpack/archive/v2.4.tar.gz)
10. Update your version of Bundler (gem update bundler) and rebuild the .iml file. I noticed that you reverted it's listing to an earlier version.

I think the structure should be something like:

• Buildpack Modes
• Easy Mode
  • How to clone
  • Where to download releases
  • How to use create-buildpack, update-buildpack
• Expert Mode
  • Forking/downloading sources
  • Modification to make
  • How to use create-buildpack, update-buildpack
  • Replicating the repository (optional)
• Offline Mode
  • How to clone
  • Where to download releases
  • How to build offline package
  • How to use create-buildpack, update-buildpack

That's just a rough outline, and my be missing things, but points you in the right direction.