diff --git a/Running-Mastodon/Docker-Guide.md b/Running-Mastodon/Docker-Guide.md
index e9f3e07c..b06c2ed3 100644
--- a/Running-Mastodon/Docker-Guide.md
+++ b/Running-Mastodon/Docker-Guide.md
@@ -28,15 +28,31 @@ Do NOT change the `REDIS_*` or `DB_*` settings when running with the default doc
 
 You will need to fill in, at least: `LOCAL_DOMAIN`, `LOCAL_HTTPS`, and the `SMTP_*` settings.
 
+## Getting the Mastodon image
 
+### Using a prebuilt image
+
+If you're not making any local code changes or customizations on your instance, you can use a prebuilt Docker image to avoid the time and resource consumption of a build. Images are available from Docker Hub: https://hub.docker.com/r/gargron/mastodon/
+    
+To use the prebuilt images:
+
+1. Open `docker-compose.yml` in your favorite text editor.
+2. Comment out the `build: .` lines for all images (web, streaming, sidekiq).
+3. Edit the `image: gargron/mastodon` lines for all images to include the release you want. The default is `latest` which may not be a tagged release. If you wanted to use v2.2.0 for example, you would edit the lines to say: `image: gargron/mastodon:v2.2.0`
+4. Save the file and exit the text editor.
+4. Run `docker-compose build`. It will now pull the correct image from Docker Hub.
+
+### Building your own image
+
+You must build your own image if you've made any code modifications. To build your own image:
+
+1. Open `docker-compose.yml` in your favorite text editor.
+2. Uncomment the `build: .` lines for all images (web, streaming, sidekiq) if needed.
+3. Save the file and exit the text editor.
+3. Run `docker-compose build`.
+    
 ## Building the app
 
-If you want to build your own image, run the command below:
-
-    docker-compose build
-
-If you want to use prebuilt images on Docker Hub, just comment out all `build` keys in `docker-compose.yml` and continue.
-
 Now the image can be used to generate secrets. Run the command below for each of `PAPERCLIP_SECRET`, `SECRET_KEY_BASE`, and `OTP_SECRET` then copy the results into the `.env.production` file:
 
     docker-compose run --rm web rake secret
@@ -91,7 +107,10 @@ This approach makes updating to the latest version a real breeze.
   - If the `docker-compose.yml` file is modified, run `git stash` to stash your changes.
 3. `git checkout TAG_NAME` to use the tag code. (If you have committed changes, use `git merge TAG_NAME` instead, though this isn't likely.)
 4. Only if you ran `git stash`, now run `git stash pop` to redo your changes to `docker-compose.yml`. Double check the contents of this file.
-5. `docker-compose build` to compile the Docker image out of the changed source files.
+5. Build the updated Mastodon image. 
+- If you are using a prebuilt image: First, edit the `image: gargron/mastodon` lines in `docker-compose.yml` to include the tag for the new version. E.g. `image: gargron/mastodon:v2.2.0`
+- To pull the prebuilt image, or build your own from the updated code: `docker-compose build`
 6. (optional) `docker-compose run --rm web rake db:migrate` to perform database migrations. Does nothing if your database is up to date.
 7. (optional) `docker-compose run --rm web rake assets:precompile` to compile new JS and CSS assets.
-8. `docker-compose up -d` to re-create (restart) containers and pick up the changes.
+8. Follow any other special instructions in the release notes.
+9. `docker-compose up -d` to re-create (restart) containers and pick up the changes.