Merge pull request #221868 from tomkerkhove/patch-6

fix(apim): Clarify that revision IDs must be specified as part of API ID

Author: prmerger-automator[bot]

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

@@ -30,10 +30,13 @@ With revisions you can:
 
 Each revision to your API can be accessed using a specially formed URL. Append `;rev={revisionNumber}` at the end of your API URL, but before the query string, to access a specific revision of that API. For example, you might use this URL to access revision 3 of the `customers` API:
 
-`https://apis.contoso.com/customers;rev=3?customerId=123`
+`https://apis.contoso.com/customers;rev=3/leads?customerId=123`
 
 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.
 
+> [!NOTE]
+> The `;rev={id}` must be appended to the API ID, and not the URI path.
+
 ## 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.