Add inline documentation to clarify Expeditor steps

Signed-off-by: Tom Duffield <tom@chef.io>

.expeditor/bundle_install.sh

@@ -1,9 +1,14 @@
 #!/bin/sh
+#
+# Simple file to perform a minimal bundle install to allow Chef Expeditor to run `rake` commands
+#
 
 set -evx
 
+# Only install groups required to run the Rake command
+export BUNDLE_WITHOUT=omnibus_package:test:aix:bsd:linux:mac_os_x:solaris:windows:default
+
 gem environment
 bundler_version=$(grep bundler omnibus_overrides.rb | cut -d'"' -f2)
 gem install bundler -v $bundler_version --user-install --conservative
-export BUNDLE_WITHOUT=omnibus_package:test:aix:bsd:linux:mac_os_x:solaris:windows:default
 bundle install

.expeditor/update_version.sh

@@ -1,11 +1,23 @@
 #!/bin/sh
+#
+# After a PR merge, Chef Expeditor will bump the PATCH version in the VERSION file.
+# It then executes this file to update any other files/components with that new version.
+#
 
 set -evx
 
+# The github-changelog-generator requires that LANG be set
 export LANG=en_US.UTF-8
 
+# We need to run a bundle install so that our `bundle exec rake` command will work.
 . .expeditor/bundle_install.sh
 
+# Run a rake command that will update various files in chef/chef-dk with the new VERSION
 bundle exec rake expeditor_update_version
 
+# Our `rake` command can sometimes modify this file, but we don't care about the
+# changes it makes. Reset it to HEAD.
 git checkout .bundle/config
+
+# Once Expeditor finshes executing this script, it will commit the changes and push
+# the commit as a new tag corresponding to the value in the VERSION file.