From bdf6d77a18aebff26a28da9251665321733c82c4 Mon Sep 17 00:00:00 2001 From: Kyle Ibrahim Date: Wed, 21 Dec 2016 18:50:01 -0800 Subject: [PATCH] Fix typos in thirdpartyresources.md --- docs/user-guide/thirdpartyresources.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/user-guide/thirdpartyresources.md b/docs/user-guide/thirdpartyresources.md index e76c64e295..b6e608b3b9 100644 --- a/docs/user-guide/thirdpartyresources.md +++ b/docs/user-guide/thirdpartyresources.md @@ -34,9 +34,9 @@ $ kubectl explain thirdpartyresource ## Creating a ThirdPartyResource -When you user create a new `ThirdPartyResource`, the Kubernetes API Server reacts by creating a new, namespaced RESTful resource path. For now, non-namespaced objects are not supported. As with existing built-in objects, deleting a namespace deletes all custom objects in that namespace. `ThirdPartyResources` themselves are non-namespaced and are available to all namespaces. +When you create a new `ThirdPartyResource`, the Kubernetes API Server reacts by creating a new, namespaced RESTful resource path. For now, non-namespaced objects are not supported. As with existing built-in objects, deleting a namespace deletes all custom objects in that namespace. `ThirdPartyResources` themselves are non-namespaced and are available to all namespaces. -For example, if a save the following `ThirdPartyResource` to `resource.yaml`: +For example, if you save the following `ThirdPartyResource` to `resource.yaml`: ```yaml apiVersion: extensions/v1beta1