From 231c9a1589b5dafdcdd91237746ec850c6472023 Mon Sep 17 00:00:00 2001 From: EdLeafe Date: Tue, 8 Dec 2015 13:54:21 +0000 Subject: [PATCH] Edit the text to be more native-English sounding No substantial changes; just wanted to make the text sound more like native English. blueprint complete-todo-in-api-concept-doc Change-Id: I9ff48113bf709f63e3654a5851aa8d6853b519b5 --- api-guide/source/microversions.rst | 26 ++++++++++++++------------ 1 file changed, 14 insertions(+), 12 deletions(-) diff --git a/api-guide/source/microversions.rst b/api-guide/source/microversions.rst index baedcdd0665e..d496ad909d25 100644 --- a/api-guide/source/microversions.rst +++ b/api-guide/source/microversions.rst @@ -15,22 +15,24 @@ Microversions ============= -API v2.1 supports Microversions. User uses Microversions to discover the -supported API version in the cloud. If cloud is upgraded to support newer -versions, it will still support all older versions to maintain the backward -compatibility for users using older versions. Also user can discover new -features easily with Microversions, then user can take all the advantages of -current cloud. +API v2.1 supports Microversions: small, documented changes to the API. A user +can use Microversions to discover the latest API version supported in their +cloud. A cloud that is upgraded to support newer versions will still support +all older versions to maintain the backward compatibility for those users who +depend on older versions. Users can also discover new features easily with +Microversions, so that they can benefit from all the advantages and +improvements of the current cloud. There are multiple cases which you can resolve with Microversions: Legacy v2 API user with new cloud -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +================================= -The minimum version of Microversions is `2.1`, this is a version compatible -with legacy v2 API. The legacy v2 API user don't need to worry about that his -old client is broken with new cloud deployment. Cloud operator don't need to -worry that upgrading cloud to newer versions will break any user with old -client. +The minimum version of Microversions is `2.1`, which is a version compatible +with the legacy v2 API. The legacy v2 API user doesn't need to worry that their +older client software will be broken when their cloud is upgraded with new +versions. And the cloud operator doesn't need to worry that upgrading their +cloud to newer versions will break any user with older clients that don't +expect these changes. TODO: add more use-cases for Microversions