diff --git a/docs/admin/namespaces/index.md b/docs/admin/namespaces/index.md
index 61382948ec..e5ef97e148 100644
--- a/docs/admin/namespaces/index.md
+++ b/docs/admin/namespaces/index.md
@@ -51,7 +51,7 @@ Let's create two new namespaces to hold our work.
 
 Use the file [`namespace-dev.json`](/docs/admin/namespacesnamespace-dev.json) which describes a development namespace:
 
-{% include code.html language="json" file="namespace-dev.json" ghlink="https://github.com/kubernetes/kubernetes.github.io/blob/master/docs/admin/namespaces/namespace-dev.json" %}
+{% include code.html language="json" file="namespace-dev.json" ghlink="/docs/admin/namespaces/namespace-dev.json" %}
 
 Create the development namespace using kubectl.
 
@@ -231,4 +231,4 @@ cattle-zz7ea   1/1       Running   0          12s
 At this point, it should be clear that the resources users create in one namespace are hidden from the other namespace.
 
 As the policy support in Kubernetes evolves, we will extend this scenario to show how you can provide different
-authorization rules for each namespace.
\ No newline at end of file
+authorization rules for each namespace.