Merge pull request #2568 from metabase/docs-fixes

Docs fixes

docs/operations-guide/running-metabase-on-docker.md

@@ -44,12 +44,12 @@ In this scenario all you need to do is make sure you launch Metabase with the co
 Keep in mind that Metabase will be connecting from within your docker container, so make sure that either you're using a fully qualified hostname or that you've set a proper entry in your container's `/etc/hosts file`.
 
 
-### Setting the JVM Timezone
+### Setting the Java Timezone
 
-It's best to set your JVM timezone to match the timezone you'd like all your reports to come in.  You can do this by simply specifying the `JVM_TIMEZONE` environment variable which is picked up by the Metabase launch script.  For example:
+It's best to set your Java timezone to match the timezone you'd like all your reports to come in.  You can do this by simply specifying the `JAVA_TIMEZONE` environment variable which is picked up by the Metabase launch script.  For example:
 
     docker run -d -p 3000:3000 \
-      -e "JVM_TIMEZONE=US/Pacific" \
+      -e "JAVA_TIMEZONE=US/Pacific" \
       --name metabase metabase/metabase
 
 

docs/operations-guide/running-metabase-on-elastic-beanstalk.md

@@ -17,7 +17,7 @@ The Metabase team runs a number of production installations on AWS using Elastic
 
 Metabase provides an Elastic Beanstalk pre-configured launch url to help new installations getting started.  If you are starting fresh we recommend you follow this link to begin creating the Elastic Beanstalk deployment with a few choices pre-filled.
 
-[Launch Metabase on Elastic Beanstalk](http://downloads.metabase.com/v0.17.0/launch-aws-eb.html)
+[Launch Metabase on Elastic Beanstalk](http://downloads.metabase.com/v0.17.1/launch-aws-eb.html)
 
 The rest of this guide will follow each phase of the Elastic Beanstalk setup step-by-step.
 
@@ -54,7 +54,7 @@ When your environment type settings look like the above then go ahead and click
 
 The application version describes the exact binary you wish to deploy to your Elastic Beanstalk application.  Metabase provides a pre-built AWS Elastic Beanstalk application version which can be linked to directly.  Simply enter the following url in the `S3 URL` textbox:
 
-https://s3.amazonaws.com/downloads.metabase.com/v0.17.0/metabase-aws-eb.zip
+https://s3.amazonaws.com/downloads.metabase.com/v0.17.1/metabase-aws-eb.zip
 
 Leave all the settings under Deployment Limits on their defaults.  These settings won't impact Metabase.
 
@@ -187,7 +187,7 @@ Here's each step:
 1. Go to Elastic Beanstalk and select your `Metabase` application
 * Click on `Application Versions` on the left nav (you can also choose `Application Versions` from the dropdown at the top of the page)
 * Download the latest Metabase Elastic Beanstalk deployment file
-  * https://s3.amazonaws.com/downloads.metabase.com/v0.17.0/metabase-aws-eb.zip
+  * https://s3.amazonaws.com/downloads.metabase.com/v0.17.1/metabase-aws-eb.zip
 * Upload a new Application Version
 	* Click the `Upload` button on the upper right side of the listing
 		* Give the new version a name, ideally including the Metabase version number (e.g. v0.13.0)

docs/operations-guide/running-metabase-on-heroku.md

@@ -44,16 +44,16 @@ Upgrading to the next version of Metabase is a simple process where you will gra
 Here's each step:
 
 * Clone the latest version to your local machine:
-```
-git clone https://github.com/metabase/metabase-deploy.git
-cd metabase-deploy
-```
+
+    git clone https://github.com/metabase/metabase-deploy.git  
+    cd metabase-deploy
+
 * Add a git remote with your metabase setup:
-```
-git remote add heroku https://git.heroku.com/your-metabase-app.git
-```
+
+    git remote add heroku https://git.heroku.com/your-metabase-app.git
+
 * Force push the new version to Heroku:
-```
-git push -f heroku master
-```
+
+    git push -f heroku master
+
 * Wait for the deploy to finish