Update installation and wording in "Getting started".

content/docs/introduction/getting_started.md

@@ -21,28 +21,23 @@ git clone https://github.com/prometheus/prometheus.git
 
 ## Building Prometheus
 
-Building Prometheus currently still requires a `make` step, as some parts of
-the source are autogenerated (web assets).
+[Download the latest release](https://github.com/prometheus/prometheus/releases)
+of Prometheus for your platform, then extract and run it:
 
-```language-bash
-cd prometheus
-make build
+```
+tar xvfz prometheus-*.tar.gz
+./prometheus
 ```
 
-Note that building requires a fair amount of memory. You should have
-at least 2GiB of RAM available.
-
-If you encounter problems building Prometheus, see [the more detailed build
-instructions](https://github.com/prometheus/prometheus#use-make) in the
-README.md.
+It should fail to start, complaining about the absence of a configuration file.
 
 ## Configuring Prometheus to monitor itself
 
 Prometheus collects metrics from monitored targets by scraping metrics HTTP
 endpoints on these targets. Since Prometheus also exposes data in the same
-manner about itself, it may also be used to scrape and monitor its own health.
+manner about itself, it can also scrape and monitor its own health.
 
-While a Prometheus server which collects only data about itself is not very
+While a Prometheus server that collects only data about itself is not very
 useful in practice, it is a good starting example. Save the following basic
 Prometheus configuration as a file named `prometheus.yml`:
 
@@ -56,7 +51,7 @@ global:
   labels:
     monitor: 'codelab-monitor'
 
-# A scrape configuration containing exactly one endpoint to scrape: 
+# A scrape configuration containing exactly one endpoint to scrape:
 # Here it's Prometheus itself.
 scrape_configs:
   # The job name is added as a label `job=<job_name>` to any timeseries scraped from this config.
@@ -86,11 +81,11 @@ Prometheus build directory and run:
 ```
 
 Prometheus should start up and it should show a status page about itself at
-http://localhost:9090. Give it a couple of seconds to start collecting data
-about itself from its own HTTP metrics endpoint.
+http://localhost:9090. Give it a couple of seconds to collect data about itself
+from its own HTTP metrics endpoint.
 
 You can also verify that Prometheus is serving metrics about itself by
-navigating to its metrics exposure endpoint: http://localhost:9090/metrics
+navigating to its metrics endpoint: http://localhost:9090/metrics
 
 By default, Prometheus will only execute at most one OS thread at a
 time. In production scenarios on multi-CPU machines, you will most
@@ -140,7 +135,7 @@ To count the number of returned time series, you could write:
 count(prometheus_target_interval_length_seconds)
 ```
 
-For further details about the expression language, see the
+For more about the expression language, see the
 [expression language documentation](/docs/querying/basics/).
 
 ## Using the graphing interface