From a79533257dfd0ecad2ef168ab2311e3225b153e3 Mon Sep 17 00:00:00 2001 From: dnoland1 Date: Thu, 11 Apr 2019 22:37:53 -0700 Subject: [PATCH] Update _index.md --- content/rancher/v2.x/en/project-admin/namespaces/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.x/en/project-admin/namespaces/_index.md b/content/rancher/v2.x/en/project-admin/namespaces/_index.md index ba3b9cf7dc2..e56bfd6bc1c 100644 --- a/content/rancher/v2.x/en/project-admin/namespaces/_index.md +++ b/content/rancher/v2.x/en/project-admin/namespaces/_index.md @@ -5,7 +5,7 @@ weight: 2520 Within Rancher, you can further divide projects into different [namespaces](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/), which are virtual clusters within a project backed by a physical cluster. Should you require another level of organization beyond projects and the `default` namespace, you can use multiple namespaces to isolate applications and resources. -Although you assign resources at the project level so that each namespace can in the project can use them, you can override this inheritance by assigning resources explicitly to a namespace. +Although you assign resources at the project level so that each namespace in the project can use them, you can override this inheritance by assigning resources explicitly to a namespace. Resources that you can assign directly to namespaces include: