Merge branch 'master' of https://github.com/kubernetes/kubernetes.github.io into release-1.6

* 'master' of https://github.com/kubernetes/kubernetes.github.io:
  fix the link of ogging-elasticsearch-kibana.md
  View $PAGE on Github without forking the repo
  update init-containers.md
  update out-of-resource.md

docs/concepts/cluster-administration/out-of-resource.md

@@ -106,7 +106,7 @@ To configure hard eviction thresholds, the following flag is supported:
 * `eviction-hard` describes a set of eviction thresholds (e.g. `memory.available<1Gi`) that if met
 would trigger a pod eviction.
 
-The `kubelet` has the following default hard eviction thresholds:
+The `kubelet` has the following default hard eviction threshold:
 
 * `--eviction-hard=memory.available<100Mi`
 

docs/concepts/workloads/pods/init-containers.md

@@ -227,7 +227,7 @@ validation error is thrown for any Container sharing a name with another.
 ### Resources
 
 Given the ordering and execution for Init Containers, the following rules
-for resource usage apply:
+for resource usage application:
 
 * The highest of any particular resource request or limit defined on all Init
   Containers is the *effective init request/limit*

docs/tasks/debug-application-cluster/logging-elasticsearch-kibana.md

@@ -75,7 +75,7 @@ Elasticsearch, and is part of a service named `kibana-logging`.
 
 The Elasticsearch and Kibana services are both in the `kube-system` namespace
 and are not directly exposed via a publicly reachable IP address. To reach them,
-follow the instructions for [Accessing services running in a cluster](/docs/user-guide/accessing-the-cluster/#accessing-services-running-on-the-cluster).
+follow the instructions for [Accessing services running in a cluster](/docs/concepts/cluster-administration/access-cluster/#accessing-services-running-on-the-cluster).
 
 If you try accessing the `elasticsearch-logging` service in your browser, you'll
 see a status page that looks something like this: