Merge pull request #47 from mmoya/doc-improvements

Random docs improvements

content/docs/introduction/faq.md

@@ -66,7 +66,7 @@ development has been sponsored by [SoundCloud](https://soundcloud.com).
 
 Other companies making active contributions include [Boxever](http://www.boxever.com/)
 and [Docker](https://www.docker.com). A full list can be found in the
-[CONTRIBUTORS](https://github.com/prometheus/prometheus/blob/master/CONTRIBUTORS.md)
+[AUTHORS](https://github.com/prometheus/prometheus/blob/master/AUTHORS.md)
 file in each repository.
 
 ### What license is Prometheus released under?

content/docs/introduction/roadmap.md

@@ -26,7 +26,7 @@ GitHub issue: [#9](https://github.com/prometheus/prometheus/issues/9)
 **Aggregatable histograms**
 
 The current client-side [summary
-types](http://localhost:3000/docs/concepts/metric_types/#summaries) do not
+types](/docs/concepts/metric_types/#summaries) do not
 support aggregation of quantiles. For example, it is [statistically
 incorrect](http://latencytipoftheday.blogspot.de/2014/06/latencytipoftheday-you-cant-average.html)
 to average over the 90th percentile latency of multiple monitored instances.

content/docs/querying/examples.md

@@ -51,7 +51,7 @@ but still preserve the `job` dimension:
 If we have two different metrics with the same dimensional labels, we can apply
 binary operators to them and elements on both sides with the same label set
 will get matched and propagated to the output. For example, this expression
-returns the unused memory in MB for every instance (on a fictional cluster
+returns the unused memory in MiB for every instance (on a fictional cluster
 scheduler exposing these metrics about the instances it runs):
 
     (instance_memory_limit_bytes - instance_memory_usage_bytes) / 1024 / 1024

content/docs/visualization/consoles.md

@@ -28,7 +28,8 @@ The example consoles have 5 parts:
 1. The main content in the center, usually graphs
 1. A table on the right
 
-The navigation bar is for links to other systems, such as other Prometheuses,
+The navigation bar is for links to other systems, such as other Prometheis
+<sup>[1](/docs/introduction/faq/#what-is-the-plural-of-prometheus?)</sup>,
 documentation, and whatever else makes sense to you. The menu is for navigation
 inside the same Prometheus server, which is very useful to be able to quickly
 open a console in another tab to correlate information. Both are configured in

content/docs/visualization/promdash.md

@@ -90,7 +90,7 @@ To configure which data to display, select the `Datasources` menu tab. It
 allows you to set one or multiple expressions to be graphed, along with the
 Prometheus server they should be queried from. The supported expressions are
 any standard [Prometheus expression language
-expressions](https://github.com/prometheus/prometheus/wiki/Expression-Language).
+expressions](/docs/querying/examples/).
 
 For each expression, you can select a graph axis to map the resulting data on,
 as well as a format string that specifies how the returned time series labels