diff --git a/api-guide/source/versions.rst b/api-guide/source/versions.rst
index 9ca2feeae786..351a4a88eb29 100644
--- a/api-guide/source/versions.rst
+++ b/api-guide/source/versions.rst
@@ -85,18 +85,17 @@ links and MIME types to available versions.
     ]
   }
 
-The API with ``CURRENT`` status is the newest API and continue improved by the
-Nova project. The API with ``SUPPORTED`` is the old API and new features is
-frozen. The API with ``DEPRECATED`` status is the API will be removed in the
+The API with ``CURRENT`` status is the newest API and continues to be improved by the
+Nova project. The API with ``SUPPORTED`` status is the old API, where new features are
+frozen. The API with ``DEPRECATED`` status is the API that will be removed in the
 foreseeable future. Providers should work with developers and partners to
 ensure there is adequate time to migrate to the new version before deprecated
-versions are discontinued. For any API which is under development and didn't
-release yet, the API status is ``EXPERIMENTAL``.
+versions are discontinued. For any API which is under development but isn't
+released as yet, the API status is ``EXPERIMENTAL``.
 
 Your application can programmatically determine available API versions
 by performing a **GET** on the root URL (i.e. with the version and
-everything to the right of it truncated) returned from the
-authentication system.
+everything following that truncated) returned from the authentication system.
 
 You can also obtain additional information about a specific version by
 performing a **GET** on the base version URL (such as,