From d3b98ca01cbb41a56023492b53cbc123a0e2cc74 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Nicolaj=20Gr=C3=A6sholt?= Date: Tue, 23 Jan 2018 17:20:12 +0100 Subject: [PATCH] typo and phrasing MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Updated with respect to Storage/Storage Classes _"A StorageClass provides a way for administrators to describe the “classes” of storage *they* offer."_ --- docs/admin/admission-controllers.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/admin/admission-controllers.md b/docs/admin/admission-controllers.md index 5833a026f9..cebdf5d73a 100644 --- a/docs/admin/admission-controllers.md +++ b/docs/admin/admission-controllers.md @@ -98,8 +98,8 @@ This way, users that do not request any special storage class do not need to car will get the default one. This admission controller does not do anything when no default storage class is configured. When more than one storage -class is marked as default, it rejects any creation of `PersistentVolumeClaim` with an error and administrator -must revisit `StorageClass` objects and mark only one as default. +class is marked as default, it rejects any creation of `PersistentVolumeClaim` with an error and an administrator +must revisit their `StorageClass` objects and mark only one as default. This admission controller ignores any `PersistentVolumeClaim` updates; it acts only on creation. See [persistent volume](/docs/concepts/storage/persistent-volumes/) documentation about persistent volume claims and