diff --git a/faq/index.html b/faq/index.html
index 8cb1ef45..17b96713 100644
--- a/faq/index.html
+++ b/faq/index.html
@@ -5,8 +5,8 @@
 title: Iron.io Frequently Asked Questions
 ---
 
-<small>This a compilation of helpful answers to frequently asked questions. If you don't see your question on here, fear not! Just send us an [email](mailto:support@iron.io) and we'll get back you shortly.
-	The Iron Team also encourages you to <a href="/community/docs/">contribute</a> to our documentation.</small>
+<small>This a compilation of helpful answers to frequently asked questions. If you don't see your question on here, fear not! Just send us an email to support@iron.io and we'll get back you shortly.
+	The Iron Team also encourages you to contribute to our documentation.</small>
 
 <h2 id="IronHUD-faq"> <a href="http://hud.iron.io">Iron Heads Up Display</a> </h2>
 <ul>
diff --git a/mq/3/reference/environment/index.md b/mq/3/reference/environment/index.md
index 6964a5b3..ed64c18c 100644
--- a/mq/3/reference/environment/index.md
+++ b/mq/3/reference/environment/index.md
@@ -55,7 +55,7 @@ Receivers get one or more messages (up to 100). Once the receive is done process
 <h2 id="queue_attributes">Queue Attributes</h2>
 
 Queues have their own set of attributes.
-To get the information about a queue, use the [Info API call](/mq/reference/api/#get_info_about_a_message_queue).
+To get the information about a queue, use the [Info API call](/mq/3/reference/api/#get_info_about_a_message_queue).
  The following is a list of all the queue attributes:
 
 #### Common Attributes
diff --git a/mq/3/reference/push_queues/index.md b/mq/3/reference/push_queues/index.md
index 0e1436cb..5bbfbd7c 100644
--- a/mq/3/reference/push_queues/index.md
+++ b/mq/3/reference/push_queues/index.md
@@ -41,7 +41,7 @@ breadcrumbs:
 <h2 id="overview">Overview</h2>
 
 [Blog Post for Overview](https://blog.iron.io/ironmq-push-queues-reliable-message). You should also review
-the [MQ API for push queue related endpoints](http://dev.iron.io/mq/reference/api/).
+the [MQ API for push queue related endpoints](http://dev.iron.io/mq/3/reference/api/).
 
 <h2 id="subscribers">Subscribers</h2>
 
@@ -153,7 +153,7 @@ The error queue message will contain the following information:
 }
 ```
 
-You can look up the original message if needed via the [GET message endpoint](/mq/reference/api/#get_message_by_id) using
+You can look up the original message if needed via the [GET message endpoint](/mq/3/reference/api/#get_message_by_id) using
 the `source_msg_id` value.
 
 ### To turn off/disable an error queue
@@ -255,7 +255,7 @@ At Iron we have 3 recommended ways to debug problems you may encounter with your
 
 <h3 id="using_error_queue">Using Error Queues (IronMQ Feature)</h3>
 Error queues are vastly useful to record, document, and react to retries, errors, and bugs that involve your Message queue endpoint.
-See our <a href="http://dev.iron.io/mq/reference/push_queues/#error_queues">Error Queue Documentation</a> on how to setup and read error queue messages.
+See our <a href="http://dev.iron.io/mq/3/reference/push_queues/#error_queues">Error Queue Documentation</a> on how to setup and read error queue messages.
 
 <h3 id="requestbin">Using RequestBin</h3>
 <a href="https://requestbin.com">RequestBin</a> is a very useful and free service provided that helps users debug all kinds of request to a unqiuely generated endpoint.
diff --git a/partner_docs/heroku_mq.md b/partner_docs/heroku_mq.md
index c15c4122..bbb2a0c8 100644
--- a/partner_docs/heroku_mq.md
+++ b/partner_docs/heroku_mq.md
@@ -12,7 +12,7 @@ This will add the developer level addon for IronMQ, which will let you test the
 
 ## Language Support
 
-IronMQ has clients for [a lot of languages](http://dev.iron.io/mq/libraries/), and you can always use [the REST API](http://dev.iron.io/mq/reference/api/) (or write your own!). This means your existing Heroku stack should work without any changes.
+IronMQ has clients for [a lot of languages](http://dev.iron.io/mq/libraries/), and you can always use [the REST API](http://dev.iron.io/mq/3/reference/api/) (or write your own!). This means your existing Heroku stack should work without any changes.
 
 ## Ruby
 
@@ -154,7 +154,7 @@ Once that's done, you can require it to get a simple wrapper for the API:
 ## Next Steps
 
 To get into more advanced uses of IronMQ, you may want to check out the
-[API docs](http://dev.iron.io/mq/reference/api/) or check out an example Sinatra application that ties in [IronWorker](http://addons.heroku.com/iron_worker)
+[API docs](http://dev.iron.io/mq/3/reference/api/) or check out an example Sinatra application that ties in [IronWorker](http://addons.heroku.com/iron_worker)
 at [https://github.com/iron-io/heroku_sinatra_example](https://github.com/iron-io/heroku_sinatra_example).
 
 ## Support
diff --git a/worker/webhooks/index.md b/worker/webhooks/index.md
index 10dd5859..3d5de84f 100644
--- a/worker/webhooks/index.md
+++ b/worker/webhooks/index.md
@@ -41,7 +41,7 @@ you don't need any updates in your existing workers to use them. A typical workf
 $ iron_worker webhook $WORKER_NAME
 ```
 
-* Pass webhook link to 3rdparty service like GitHub, or as subscriber URL for [IronMQ Push Queue](/mq/reference/push_queues)
+* Pass webhook link to 3rdparty service like GitHub, or as subscriber URL for [IronMQ Push Queue](/mq/3/reference/push_queues)
 * Do something to trigger the webhook, say, commit to GitHub or post a message to a Push Queue.
 
 When the IronWorker service receives the HTTP POST request to your webhook endpoint,