Merge pull request #291163 from dlepow/versiont

[APIM] Update version tutorial

Author: v-shils

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

@@ -13,7 +13,7 @@ ms.author: danlep
 
 [!INCLUDE [api-management-availability-all-tiers](../../includes/api-management-availability-all-tiers.md)]
 
-There are times when it's impractical to have all callers to your API use exactly 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 is possible to provide multiple *versions* in Azure API Management. 
+There are times when it's impractical to have all callers to your API use exactly 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. 
 
 For background, see [Versions](api-management-versions.md) & [Revisions](api-management-revisions.md).
 
@@ -25,7 +25,7 @@ In this tutorial, you learn how to:
 > * Add the version to a product
 > * Browse the developer portal to see the version
 
-:::image type="content" source="media/api-management-getstarted-publish-versions/azure-portal.png" alt-text="Version shown in Azure portal":::
+:::image type="content" source="media/api-management-get-started-publish-versions/azure-portal.png" alt-text="Screenshot showing API versions in the Azure portal.":::
 
 ## Prerequisites
 
@@ -37,11 +37,11 @@ In this tutorial, you learn how to:
 
 1. In the [Azure portal](https://portal.azure.com), navigate to your API Management instance.
 1. Select **APIs**.
-1. Select **Demo Conference API** from the API list. 
-1. Select the context menu (**...**) next to **Demo Conference API**.
+1. Select **Swagger Petstore** from the API list. 
+1. Select the context menu (**...**) next to **Swagger Petstore**.
 1. Select **Add version**.
 
-:::image type="content" source="media/api-management-getstarted-publish-versions/add-version-menu.png" alt-text="API context menu - add version":::
+:::image type="content" source="media/api-management-get-started-publish-versions/add-version-menu.png" alt-text="Screenshot showing command to add version in the API context menu in the portal.":::
 
 
 > [!TIP]
@@ -53,27 +53,27 @@ In Azure API Management, you choose how callers specify the API version by selec
 
 Enter the values from the following table. Then select **Create** to create your version.
 
-:::image type="content" source="media/api-management-getstarted-publish-versions/add-version.png" alt-text="Add version window":::
+:::image type="content" source="media/api-management-get-started-publish-versions/add-version.png" alt-text="Screenshot showing window to create a new version in the portal.":::
 
 
 
 |Setting   |Value  |Description  |
 |---------|---------|---------|
-|**Name**     |  *demo-conference-api-v1*       |  Unique name in your API Management instance.<br/><br/>Because a version is in fact a new API based off an API's [revision](api-management-get-started-revise-api.md), this setting is the new API's name.   |
-|**Versioning scheme**     |  **Path**       |  The way callers specify the API version.     |
-|**Version identifier**     |  *v1*       |  Scheme-specific indicator of the version. For **Path**, the suffix for the API URL path. <br/><br/> If **Header** or **Query string** is selected, enter an additional value: the name of the header or query string parameter.<br/><br/> A usage example is displayed.        |
-|**Products**     |  **Unlimited**       |  Optionally, one or more products that the API version is associated with. To publish the API, you must associate it with a product. You can also [add the version to a product](#add-the-version-to-a-product) later.      |
+|**Version identifier**     |  *v1*       |  Scheme-specific indicator of the version. For **Path**, the suffix for the API URL path.  |
+|**Versioning scheme**     |  **Path**       |  The way callers specify the API version.<br/><br/> If **Header** or **Query string** is selected, enter another value: the name of the header or query string parameter.<br/><br/> A usage example is displayed.            |
+|**Full API version name**     |  *swagger-petstore-v1*       |  Unique name in your API Management instance.<br/><br/>Because a version is in fact a new API based off an API's [revision](api-management-get-started-revise-api.md), this setting is the new API's name.   |
+|**Products**     |  **Unlimited** (provided in certain service tiers)     |  Optionally, one or more products that the API version is associated with. To publish the API, you must associate it with a product. You can also [add the version to a product](#add-the-version-to-a-product) later.      |
 
-After creating the version, it now appears underneath **Demo Conference API** in the API List. You now see two APIs: **Original**, and **v1**.
+After creating the version, it now appears underneath **Swagger Petstore** in the API List. You now see two APIs: **Original**, and **v1**.
 
-![Versions listed under an API in the Azure portal](media/api-management-getstarted-publish-versions/version-list.png)
+:::image type="content" source="media/api-management-get-started-publish-versions/version-list.png" alt-text="Screenshot of versions listed under API in the portal.":::
 
 > [!Note]
 > If you add a version to a non-versioned API, an **Original** is also automatically created. This version responds on the default URL. Creating an Original version ensures that any existing callers are not broken by the process of adding a version. If you create a new API with versions enabled at the start, an Original isn't created.
 
 ## Edit a version
 
-After adding the version, you can now edit and configure it as an API that is separate from an Original. Changes to one version do not affect another. For example, add or remove API operations, or edit the OpenAPI specification. For more information, see [Edit an API](edit-api.md).
+After adding the version, you can now edit and configure it as an API that is separate from an Original. Changes to one version don't affect another. For example, add or remove API operations, or edit the OpenAPI specification. For more information, see [Edit an API](edit-api.md).
 
 ## Add the version to a product
 
@@ -82,10 +82,10 @@ In order for callers to see the new version, it must be added to a *product*. If
 For example, to add the version to the **Unlimited** product:
 1. In the Azure portal, navigate to your API Management instance.
 1. Select **Products** > **Unlimited** > **APIs** > **+ Add**.
-1. Select **Demo Conference API**, version **v1**.
+1. Select **Swagger Petstore**, version **v1**.
 1. Click **Select**.
 
-:::image type="content" source="media/api-management-getstarted-publish-versions/08-add-multiple-versions-03-add-version-product.png" alt-text="Add version to product":::
+:::image type="content" source="media/api-management-get-started-publish-versions/08-add-multiple-versions-03-add-version-product.png" alt-text="Screenshot of adding version to product in the portal.":::
 
 ## Use version sets
 
@@ -118,7 +118,7 @@ For more information about version sets, see [Versions in Azure API Management](
 If you've tried the [developer portal](api-management-howto-developer-portal-customize.md), you can see API versions there.
 
 1. Select **Developer Portal** from the top menu.
-2. Select **APIs**, and then select **Demo Conference API**.
+2. Select **APIs**, and then select **Swagger Petstore**.
 3. You should see a dropdown with multiple versions next to the API name.
 4. Select **v1**.
 5. Notice the **Request URL** of the first operation in the list. It shows that the API URL path includes **v1**.