From 10a6fb706d84d33d748221fd9502c8a0ae875406 Mon Sep 17 00:00:00 2001 From: zhangxiaoyu-zidif Date: Mon, 30 Oct 2017 13:50:50 +0800 Subject: [PATCH] fix typo --- docs/concepts/overview/working-with-objects/namespaces.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/overview/working-with-objects/namespaces.md b/docs/concepts/overview/working-with-objects/namespaces.md index b25b17a49a..82e5a4313d 100644 --- a/docs/concepts/overview/working-with-objects/namespaces.md +++ b/docs/concepts/overview/working-with-objects/namespaces.md @@ -48,7 +48,7 @@ Kubernetes starts with three initial namespaces: * `default` The default namespace for objects with no other namespace * `kube-system` The namespace for objects created by the Kubernetes system - * `kube-public` The namespace is created automatically and readable by all users (including those not authenticated). This namespace is mostly reserved for cluster usage, in case that some resources should be visible and readable publicly thoughout the whole cluster. The public aspect of this namespace is only a convention, not a requirement. + * `kube-public` The namespace is created automatically and readable by all users (including those not authenticated). This namespace is mostly reserved for cluster usage, in case that some resources should be visible and readable publicly throughout the whole cluster. The public aspect of this namespace is only a convention, not a requirement. ### Setting the namespace for a request