README.md in bosh-stemcell-1.3012.0 vs README.md in bosh-stemcell-1.3016.0

@@ -19,16 +19,17 @@
 
 ### Bring up the vagrant stemcell building VM
 
 From a fresh copy of the bosh repo:
 
+    git submodule update --init --recursive
+
 If you use AWS EC2-Classic environment, run:
 
     export BOSH_AWS_ACCESS_KEY_ID=YOUR-AWS-ACCESS-KEY
     export BOSH_AWS_SECRET_ACCESS_KEY=YOUR-AWS-SECRET-KEY
     cd bosh-stemcell
-    git submodule update --init --recursive
     vagrant up remote --provider=aws
 
 If you use AWS VPC environment, run:
 
     export BOSH_AWS_ACCESS_KEY_ID=YOUR-AWS-ACCESS-KEY
@@ -107,11 +108,11 @@
 Substitute *\<current_build\>* with the current build number, which can be found by looking at [bosh artifacts](http://bosh_artifacts.cfapps.io).
 The final two arguments are the S3 bucket and key for the OS image to use, which can be found by reading the OS\_IMAGES document in this project.
 
     vagrant ssh -c '
       cd /bosh
-      CANDIDATE_BUILD_NUMBER=<current_build> http_proxy=http://localhost:3142/ bundle exec rake stemcell:build[vsphere,esxi,centos,nil,go,bosh-os-images,bosh-centos-7-os-image.tgz]
+      CANDIDATE_BUILD_NUMBER=<current_build> bundle exec rake stemcell:build[vsphere,esxi,centos,7,go,bosh-os-images,bosh-centos-7-os-image.tgz]
     ' remote
 
 
 ### Building the stemcell with local OS image
 
@@ -134,9 +135,11 @@
       cd /bosh
       export BOSH_AWS_ACCESS_KEY_ID=YOUR-AWS-ACCESS-KEY
       export BOSH_AWS_SECRET_ACCESS_KEY=YOUR-AWS-SECRET-KEY
       bundle exec rake stemcell:build_light[/tmp/bosh-stemcell.tgz,hvm]
     ' remote
+
+To build for specific region specify `BOSH_AWS_REGION` environment variable.
 
 ### When things go sideways
 
 If you find yourself debugging any of the above processes, here is what you need to know: