Skip to content

Commit f120510

Browse files
authored
Update api-management-get-started-publish-versions.md
Improved clarity in the API versioning explanation, emphasizing the benefits of supporting multiple versions in Azure API Management.
1 parent ae4c4a5 commit f120510

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/api-management/api-management-get-started-publish-versions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.author: danlep
1616

1717
[!INCLUDE [api-management-availability-all-tiers](../../includes/api-management-availability-all-tiers.md)]
1818

19-
There are times when it's impractical to have all callers to your API use the same version. When callers want to upgrade to a later version, they want an approach that's easy to understand. As shown in this tutorial, it's possible to provide multiple *versions* in Azure API Management.
19+
There are situations where it's impractical for all API consumers to use the same version. When consumers are ready to upgrade to a newer version, they prefer a simple and understandable approach. As demonstrated in this tutorial, Azure API Management supports exposing multiple API versions to meet this need.
2020

2121
For background, see [Versions](api-management-versions.md) and [Revisions](api-management-revisions.md).
2222

0 commit comments

Comments
 (0)