diff --git a/content/en/docs/concepts/extend-kubernetes/api-extension/custom-resources.md b/content/en/docs/concepts/extend-kubernetes/api-extension/custom-resources.md
index f64d438c64afe..efab74152a30a 100644
--- a/content/en/docs/concepts/extend-kubernetes/api-extension/custom-resources.md
+++ b/content/en/docs/concepts/extend-kubernetes/api-extension/custom-resources.md
@@ -107,7 +107,7 @@ Use a custom resource (CRD or Aggregated API) if most of the following apply:
 
 Kubernetes provides two ways to add custom resources to your cluster:
 
-- CRDs are simple and do not always require programming.
+- CRDs are simple and can be created without any programming.
 - [API Aggregation](/docs/concepts/api-extension/apiserver-aggregation/) requires programming, but allows more control over API behaviors like how data is stored and conversion between API versions.
 
 Kubernetes provides these two options to meet the needs of different users, so that neither ease of use nor flexibility are compromised.
diff --git a/content/en/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definition-versioning.md b/content/en/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definition-versioning.md
index dc92c47335704..cd9c700ca6f60 100644
--- a/content/en/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definition-versioning.md
+++ b/content/en/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definition-versioning.md
@@ -107,7 +107,7 @@ by parsing the _name_ field to determine the version number, the stability
 The algorithm used for sorting the versions is designed to sort versions in the
 same way that the Kubernetes project sorts Kubernetes versions. Versions start with a
 `v` followed by a number, an optional `beta` or `alpha` designation, and
-optional additional versioning information. Broadly, a version string might look
+optional additional numeric versioning information. Broadly, a version string might look
 like `v2` or `v2beta1`. Versions are sorted using the following algorithm:
   
 - Entries that follow Kubernetes version patterns are sorted before those that
@@ -149,14 +149,14 @@ the version.
 When an object is written, it is persisted at the version designated as the
 storage version at the time of the write. If the storage version changes,
 existing objects are never converted automatically. However, newly-created
-or updated objects are created at the new storage version. It is possible for an
+or updated objects are written at the new storage version. It is possible for an
 object to have been written at a version that is no longer served.
 
 When you read an object, you specify the version as part of the path. If you
 specify a version that is different from the object's persisted version,
-Kubernetes returns the object to you at the version you requested, but does not
-modify the persisted object. You can request an object at any version that is
-currently served.
+Kubernetes returns the object to you at the version you requested, but
+the persisted object is not changed on disk and is returned without any conversion.
+You can request an object at any version that is currently served.
 
 If you update an existing object, it is rewritten at the version that is
 currently the storage version. This is the only way that objects can change from
@@ -164,15 +164,15 @@ one version to another.
 
 To illustrate this, consider the following hypothetical series of events:
 
-1.  The storage version is `v1beta`. You create an object. It is persisted in
+1.  The storage version is `v1beta1`. You create an object. It is persisted in
     storage at version `v1beta1`
 2.  You add version `v1` to your CustomResourceDefinition and designate it as
     the storage version.
-3.  You read your object at version `v1beta`, then you read the object again at
+3.  You read your object at version `v1beta1`, then you read the object again at
     version `v1`. Both returned objects are identical except for the apiVersion
     field.
 4.  You create a new object. It is persisted in storage at version `v1`. You now
-    have two objects, one of which is at `v1beta`, and the other of which is at
+    have two objects, one of which is at `v1beta1`, and the other of which is at
     `v1`.
 5.  You update the first object. It is now persisted at version `v1` since that
     is the current storage version.