From 2f5370e0a7b2f6b07c01dd5a64e92ebc14e1f935 Mon Sep 17 00:00:00 2001 From: zacharysarah Date: Tue, 1 Aug 2017 15:45:18 -0700 Subject: [PATCH] Fixed an awkward sentence --- .../authenticate-across-clusters-kubeconfig.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tasks/access-application-cluster/authenticate-across-clusters-kubeconfig.md b/docs/tasks/access-application-cluster/authenticate-across-clusters-kubeconfig.md index d274a44c23..3f99bd5cd4 100644 --- a/docs/tasks/access-application-cluster/authenticate-across-clusters-kubeconfig.md +++ b/docs/tasks/access-application-cluster/authenticate-across-clusters-kubeconfig.md @@ -307,6 +307,6 @@ So, tying this all together, a quick start to create your own kubeconfig file: - Replace the snippet above with information for your cluster's api-server endpoint. -- Make sure your api-server is launched in such a way that at least one user (for example, `green-user`) credentials are provided to it. You will of course have to look at api-server documentation in order to determine the current state-of-the-art in terms of providing authentication details. +- Make sure your api-server provides at least one set of credentials (for example, `green-user`) when launched. You will of course have to look at api-server documentation in order to determine the current state-of-the-art in terms of providing authentication details. {% include templates/task.md %}