review comments, auth assistant edits

Author: dlepow

articles/api-management/grpc-api.md

@@ -6,7 +6,7 @@ author: dlepow
 
 ms.service: azure-api-management
 ms.topic: how-to
-ms.date: 10/06/2025
+ms.date: 02/18/2026
 ms.author: danlep
 ms.custom:
   - devx-track-arm-template
@@ -30,9 +30,9 @@ To add a gRPC API to API Management, you need to:
 API Management supports pass-through with the following types of gRPC service methods: unary, server streaming, client streaming, and bidirectional streaming. To learn more about gRPC, see [Introduction to gRPC](https://grpc.io/docs/what-is-grpc/introduction/).
 
 > [!NOTE]
-> * Currently, gRPC APIs are supported in the self-hosted gateway and in the managed gateway for classic tier instances created starting February 2026.
+> * The self-hosted gateway and the managed gateway for classic tier instances created starting January 2026 support gRPC APIs. Contact support to enable gRPC API support in the managed gateway for classic tier instances created before this date. gRPC APIs currently aren't supported in the v2 tiers.
 > * Currently, testing gRPC APIs isn't supported in the test console of the Azure portal or in the API Management developer portal.
-> * Import is limited to a single protobuf (*.proto*) file. 
+> * Import is limited to a single protobuf (*.proto*) file.  
 
 ## Prerequisites
 
@@ -42,9 +42,11 @@ API Management supports pass-through with the following types of gRPC service me
 
 * A gRPC protobuf (*.proto*) file available locally, and gRPC service that's accessible over HTTPS.
 
+* HTTP/2 protocol support enabled for client traffic. For more information, see [Manage protocols and ciphers in Azure API Management](api-management-howto-manage-protocols-ciphers.md).
+
 ## Add a gRPC API
 
-1. In the [Azure portal](https://portal.azure.com), navigate to your API Management instance.
+1. In the [Azure portal](https://portal.azure.com), go to your API Management instance.
 
 1. Under **APIs** in the sidebar menu, select **APIs**.
 
@@ -54,7 +56,7 @@ API Management supports pass-through with the following types of gRPC service me
 
 1. In the **Create a gRPC API window**, select **Full**.
 
-1. For a gRPC API, you must specify the following settings:
+1. For a gRPC API, specify the following settings:
 
     1. Enter a display name.
 
@@ -67,15 +69,15 @@ API Management supports pass-through with the following types of gRPC service me
         > [!IMPORTANT]
         > In public preview, you can only select a self-hosted gateway. The **Managed** gateway isn't supported.
 
-1. Enter any remaining settings to configure your API. These settings are explained in the [Import and publish your first API](import-and-publish.md#import-and-publish-a-backend-api) tutorial.
+1. Enter any remaining settings to configure your API. The [Import and publish your first API](import-and-publish.md#import-and-publish-a-backend-api) tutorial explains these settings.
 
 1. Select **Create**.
 
-    The API is added to the **APIs** list. You can view update your settings by going to the **Settings** tab of the API.
+    The portal adds the API to the **APIs** list. You can view and update your settings by going to the **Settings** tab of the API.
 
-## Call gRPC services with .NET
+## Call gRPC services by using .NET
 
-For information about calling gRPC services with .NET, see the following articles:
+For information about calling gRPC services by using .NET, see the following articles:
 
 * [Tutorial: Create a gRPC client and server in ASP.NET Core](/aspnet/core/tutorials/grpc/grpc-start)
 * [Troubleshoot gRPC on .NET](/aspnet/core/grpc/troubleshoot#calling-grpc-services-hosted-in-a-sub-directory)