Merge pull request #253 from karthequian/master

fixes a few simple spelling errors

content/blog/2015-04-24-prometheus-monitring-spreads-through-the-internet.md

@@ -5,7 +5,7 @@ kind: article
 author_name: Brian Brazil
 ---
 
-It has been almost three months since we publicy announced Prometheus version
+It has been almost three months since we publicly announced Prometheus version
 0.10.0, and we're now at version 0.13.1.
 
 [SoundCloud's announcement blog post](https://developers.soundcloud.com/blog/prometheus-monitoring-at-soundcloud)

content/docs/operating/configuration.md

@@ -211,7 +211,7 @@ A `tls_config` allows configuring TLS connections.
 ### Target groups `<target_group>`
 
 A `target_group` allows specifying a list of targets and a common label set for them.
-They are the canoncial way to specify static targets in a scrape configuration.
+They are the canonical way to specify static targets in a scrape configuration.
 
 ```
 # The targets specified by the target group.

content/docs/practices/instrumentation.md

@@ -35,7 +35,7 @@ and latency. The number of in-progress requests can also be useful.
 Online-serving systems should be monitored on both the client and server side.
 If the two sides see different behaviors, that is very useful information for debugging.
 If a service has many clients, it is also not practical for the service to track them
-individally, so they have to rely on their own stats.
+individually, so they have to rely on their own stats.
 
 Be consistent in whether you count queries when they start or when they end.
 When they end is suggested, as it will line up with the error and latency stats,
@@ -161,7 +161,7 @@ take advantage of them, so it takes a bit of getting used to.
 When you have multiple metrics that you want to add/average/sum, they should
 usually be one metric with labels rather than multiple metrics.
 
-For example, rather than `http_responses_500_total` and `http_resonses_403_total`,
+For example, rather than `http_responses_500_total` and `http_responses_403_total`,
 create a single metric called `http_responses_total` with a `code` label
 for the HTTP response code. You can then process the entire metric as one in
 rules and graphs.