Merge pull request #189397 from johndowns/apim-revisions

Remove instruction to take API revisions offline

Author: PRMerger17

articles/api-management/api-management-revisions.md

@@ -4,10 +4,9 @@ description: Learn about the concept of revisions in Azure API Management.
 services: api-management
 documentationcenter: ''
 author: johndowns
- 
 ms.service: api-management
 ms.topic: article
-ms.date: 06/12/2020
+ms.date: 02/22/2022
 ms.author: jodowns
 ms.custom: fasttrack-new, devx-track-azurepowershell
 ---
@@ -35,11 +34,6 @@ Each revision to your API can be accessed using a specially formed URL. Append `
 
 By default, each revision has the same security settings as the current revision. You can deliberately change the policies for a specific revision if you want to have different security applied for each revision. For example, you might want to add a [IP filtering policy](./api-management-access-restriction-policies.md#RestrictCallerIPs) to prevent external callers from accessing a revision that is still under development.
 
-A revision can be taken offline, which makes it inaccessible to callers even if they try to access the revision through its URL. You can mark a revision as offline using the Azure portal. If you use PowerShell, you can use the `Set-AzApiManagementApiRevision` cmdlet and set the `Path` argument to `$null`.
-
-> [!NOTE]
-> We suggest taking revisions offline when you aren't using them for testing.
-
 ## Current revision
 
 A single revision can be set as the *current* revision. This revision will be the one used for all API requests that don't specify an explicit revision number in the URL. You can roll back to a previous revision by setting that revision as current.
@@ -67,6 +61,13 @@ When you set a revision as current you can also optionally specify a public chan
 > These properties can only be changed in the current revision.  If your edits change any of the above 
 > properties of a non-current revision, the error message `Can't change property for non-current revision` will be displayed.
 
+## Take a revision offline
+
+A revision can be taken offline, which makes it inaccessible to callers even if they try to access the revision through its URL. You can mark a revision as offline using the Azure portal.
+
+> [!NOTE]
+> We suggest taking revisions offline when you aren't using them for testing.
+
 ## Versions and revisions
 
 Versions and revisions are distinct features. Each version can have multiple revisions, just like a non-versioned API. You can use revisions without using versions, or the other way around. Typically versions are used to separate API versions with breaking changes, while revisions can be used for minor and non-breaking changes to an API.