From 528910f5f46c687b959b10d46fa4438772a051a3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Lucas=20K=C3=A4ldstr=C3=B6m?=
 <lucas.kaldstrom@hotmail.co.uk>
Date: Mon, 25 Jan 2016 09:33:08 +0200
Subject: [PATCH] Fix the apiserver proxy doc

---
 docs/user-guide/accessing-the-cluster.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/user-guide/accessing-the-cluster.md b/docs/user-guide/accessing-the-cluster.md
index 1b0ed12f9e3..9c601b6246a 100644
--- a/docs/user-guide/accessing-the-cluster.md
+++ b/docs/user-guide/accessing-the-cluster.md
@@ -243,9 +243,9 @@ at `https://104.197.5.247/api/v1/proxy/namespaces/kube-system/services/elasticse
 #### Manually constructing apiserver proxy URLs
 
 As mentioned above, you use the `kubectl cluster-info` command to retrieve the service's proxy URL. To create proxy URLs that include service endpoints, suffixes, and parameters, you simply append to the service's proxy URL:
-`http://`*`kubernetes_master_address`*`/`*`service_path`*`/`*`service_name`*`/`*`service_endpoint-suffix-parameter`*
-<!--- TODO: update this part of doc because it doesn't seem to be valid. What
-about namespaces? 'proxy' verb? -->
+`http://`*`kubernetes_master_address`*`/api/v1/proxy/namespaces/`*`namespace_name`*`/services/`*`service_name[:port_name]`*
+
+If you haven't specified a name for your port, you don't have to specify *port_name* in the URL
 
 ##### Examples