Merge pull request #306596 from dlepow/patch-918487

[APIM] Clarify scaling options for API Management tiers

Author: prmerger-automator[bot]

articles/api-management/upgrade-and-scale.md

@@ -20,7 +20,7 @@ ms.custom:
 Customers can scale an Azure API Management instance in a dedicated service tier by adding and removing units. A **unit** is composed of dedicated Azure resources and has a certain load-bearing capacity expressed as a number of API calls per second. This number doesn't represent a call limit, but rather an estimated maximum throughput value to allow for rough capacity planning. Actual throughput and latency vary broadly depending on factors such as number and rate of concurrent connections, the kind and number of configured policies, request and response sizes, and backend latency.
 
 > [!NOTE]
-> * In the **Basic**, **Standard**, and **Premium** tiers of the API Management service, and in [workspace gateways](workspaces-overview.md#workspace-gateway), you can configure an instance to [scale automatically](api-management-howto-autoscale.md) based on a set of rules.
+> * In the classic **Basic**, **Standard**, and **Premium** tiers, the **v2** tiers, and [workspace gateways](workspaces-overview.md#workspace-gateway), you can configure an instance to [scale automatically](api-management-howto-autoscale.md) based on a set of rules.
 > * API Management instances in the **Consumption** tier scale automatically based on the traffic. Currently, you cannot upgrade from or downgrade to the Consumption tier.
 
 The throughput and price of each unit depend on the [service tier](api-management-features.md) in which the unit exists. If you need to increase capacity for a service within a tier, you should add a unit. If the tier that is currently selected in your API Management instance doesn't allow adding more units, you need to upgrade to a higher-level tier.