From 3326e24f290b8cd28b551af276dd40d83411e244 Mon Sep 17 00:00:00 2001 From: eulerzgy Date: Tue, 22 Sep 2015 09:48:53 +0800 Subject: [PATCH] update replication-controllers to replicaton controller --- docs/admin/namespaces/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/admin/namespaces/README.md b/docs/admin/namespaces/README.md index c866b1e20d5..22a36ac32fd 100644 --- a/docs/admin/namespaces/README.md +++ b/docs/admin/namespaces/README.md @@ -70,7 +70,7 @@ For this exercise, we will create two additional Kubernetes namespaces to hold o Let's imagine a scenario where an organization is using a shared Kubernetes cluster for development and production use cases. -The development team would like to maintain a space in the cluster where they can get a view on the list of pods, services, and replication-controllers +The development team would like to maintain a space in the cluster where they can get a view on the list of pods, services, and replication controllers they use to build and run their application. In this space, Kubernetes resources come and go, and the restrictions on who can or cannot modify resources are relaxed to enable agile development.