Skip to content

Commit 6cf0a91

Browse files
committed
edits
1 parent 61db06f commit 6cf0a91

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/api-management/api-management-versions.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,14 +9,14 @@ ms.topic: concept-article
99
ms.date: 05/12/2025
1010
ms.author: danlep
1111

12-
#Customer intent: As an API developer, I want to use versions in API Management so I can safely handle breaking changes in my API.
12+
#Customer intent: As an API developer, I want to use versions in API Management so that I can safely handle breaking changes in my API.
1313
---
1414

1515
# Versions in Azure API Management
1616

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

19-
Versions enable you to present groups of related APIs to your developers. You can use versions to handle breaking changes in your API safely. Clients can choose to use your new API version when they're ready, while existing clients continue to use an older version. Versions are differentiated via a version identifier (which is any string value you choose), and a versioning scheme allows clients to identify which version of an API they want to use.
19+
Versions enable you to present groups of related APIs to your developers. You can use versions to handle breaking changes in your API safely. Clients can choose to use your new API version when they're ready, while existing clients continue to use an older version. Versions are differentiated via a version identifier (which is any string value you choose), and a versioning scheme allows clients to identify which version of an API they want to use. This article describes how to use versions in API Management.
2020

2121
For most purposes, each API version can be considered its own independent API. Two different API versions might have different sets of operations and different policies.
2222

@@ -26,7 +26,7 @@ With versions you can:
2626
- Use a path, query string, or header to differentiate among versions.
2727
- Use any string value you want to identify your version. It could be a number, a date, or a name.
2828
- Show your API versions grouped together on the developer portal.
29-
- Create a new version of an existing (non-versioned) API without breaking existing clients.
29+
- Create a new version of an existing (non-versioned) API without affecting existing clients.
3030

3131
[Get started with versions by completing a walkthrough.](./api-management-get-started-publish-versions.md)
3232

0 commit comments

Comments
 (0)