diff --git a/docs/concepts/cluster-administration/out-of-resource.md b/docs/concepts/cluster-administration/out-of-resource.md
index 76e7125e7e..27a84464f3 100644
--- a/docs/concepts/cluster-administration/out-of-resource.md
+++ b/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`
 
diff --git a/docs/concepts/workloads/pods/init-containers.md b/docs/concepts/workloads/pods/init-containers.md
index 1a43dea943..d3dc7beb88 100644
--- a/docs/concepts/workloads/pods/init-containers.md
+++ b/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*
diff --git a/docs/tasks/debug-application-cluster/logging-elasticsearch-kibana.md b/docs/tasks/debug-application-cluster/logging-elasticsearch-kibana.md
index 4441067d60..9931bab209 100644
--- a/docs/tasks/debug-application-cluster/logging-elasticsearch-kibana.md
+++ b/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:
diff --git a/editdocs.md b/editdocs.md
index b089db1c43..0a5ff53c88 100644
--- a/editdocs.md
+++ b/editdocs.md
@@ -13,6 +13,8 @@ $( document ).ready(function() {
     	$("#continueEdit").show();
     	$("#continueEditButton").text("Edit " + forwarding);
     	$("#continueEditButton").attr("href", "https://github.com/kubernetes/kubernetes.github.io/edit/master/" + forwarding)
+    	$("#viewOnGithubButton").text("View " + forwarding + " on GitHub");
+    	$("#viewOnGithubButton").attr("href", "https://github.com/kubernetes/kubernetes.github.io/tree/master/" + forwarding)
     } else {
         $("#generalInstructions").show();
     	$("#continueEdit").hide();
@@ -26,6 +28,7 @@ $( document ).ready(function() {
 <p>Click the button below to edit the page you were just on. When you are done, click <b>Commit Changes</b> at the bottom of the screen. This creates a copy of our site in your GitHub account called a <i>fork</i>. You can make other changes in your fork after it is created, if you want. When you are ready to send us all your changes, go to the index page for your fork and click <b>New Pull Request</b> to let us know about it.</p>
 
 <p><a id="continueEditButton" class="button"></a></p>
+<p><a id="viewOnGithubButton" class="button"></a></p>
 
 </div>
 <div id="generalInstructions">