Address comments

kubernetes · Jul 13, 2018 · 614308d · 614308d
1 parent 940019d
commit 614308d
Showing 1 changed file with 4 additions and 4 deletions.
diff --git a/...ocs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions.md b/...ocs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions.md
@@ -391,14 +391,14 @@ columns.
       kubectl create -f resourcedefinition.yaml
       ```
 
-3.  reate an instance using the `my-crontab.yaml` from the previous section.
+3.  Create an instance using the `my-crontab.yaml` from the previous section.
 
 4.  Invoke the server-side printing:
 
       ```shell
       kubectl get crontab my-new-cron-object
       ```
-      
+
       Notice the `NAME`, `SPEC`, `REPLICAS`, and `AGE` columns in the output:
 
       ```
@@ -424,10 +424,10 @@ A column's `type` field can be any of the following (compare [OpenAPI v3 data ty
 - `number` – floating point numbers
 - `string` – strings
 - `boolean` – true or false
-- `date` – renderend differentially as time since this timestamp.
+- `date` – rendered differentially as time since this timestamp.
 
 If the value inside a CustomResource does not match the type specified for the column,
-the value is omitted. Use CustomResourceDefinition validation to ensure that the value
+the value is omitted. Use CustomResource validation to ensure that the value
 types are correct.
 
 #### Format