[APIM] Test single resolver

Author: dlepow

articles/api-management/configure-graphql-resolver.md

@@ -6,7 +6,7 @@ author: dlepow
 
 ms.service: api-management
 ms.topic: reference
-ms.date: 06/08/2023
+ms.date: 07/20/2023
 ms.author: danlep
 ---
 
@@ -25,7 +25,7 @@ Currently, API Management supports resolvers that can access the following data
 * A resolver is a resource containing a policy definition that's invoked only when a matching object type and field in the schema is executed. 
 * Each resolver resolves data for a single field. To resolve data for multiple fields, configure a separate resolver for each.
 * Resolver-scoped policies are evaluated *after* any `inbound` and `backend` policies in the policy execution pipeline. They don't inherit policies from other scopes. For more information, see [Policies in API Management](api-management-howto-policies.md).
-
+* You can configure API-scoped policies for a GraphQL API, independent of the resolver-scoped policies. For example, you might want to add a [validate-graphql-request](validate-graphql-request-policy.md) policy to the `inbound` scope to validate the request before the resolver is invoked. Configure API-scoped policies on the **API policies** tab for the API.
 
 > [!IMPORTANT]
 > * If you use the preview `set-graphql-resolver` policy in policy definitions, you should migrate to the managed resolvers described in this article.
@@ -59,13 +59,30 @@ The following steps create a resolver using an HTTP-based data source. The gener
 
         :::image type="content" source="media/configure-graphql-resolver/configure-resolver-policy.png" alt-text="Screenshot of resolver policy editor in the portal." lightbox="media/configure-graphql-resolver/configure-resolver-policy.png":::
 
-1. The resolver is attached to the field. Go to the **Resolvers** tab to list and manage the resolvers configured for the API. You can also create resolvers from the **Resolvers** tab.
+    The resolver is attached to the field and appears on the **Resolvers** tab. 
+
 
     :::image type="content" source="media/configure-graphql-resolver/list-resolvers.png" alt-text="Screenshot of the resolvers list for GraphQL API in the portal." lightbox="media/configure-graphql-resolver/list-resolvers.png":::
 
-    > [!TIP]
-    > * The **Linked** column indicates whether the resolver is configured for a field that's currently in the GraphQL schema. If a resolver isn't linked, it can't be invoked.
-    > * You can clone a listed resolver to quickly create a similar resolver that targets a different type and field. In the context menu (**...**), select **Clone**. 
+## Manage resolvers
+
+List and manage the resolvers for a GraphQL API on the API's **Resolvers** tab. 
+
+On the **Resolvers** tab:
+
+* The **Linked** column indicates whether the resolver is configured for a field that's currently in the GraphQL schema. If a resolver isn't linked, it can't be invoked.
+
+* In the context menu (**...**) for a resolver, find commands to **Clone**, **Edit**, or **Delete** a resolver.  Clone a listed resolver to quickly create a similar resolver that targets a different type and field. 
+
+* You can create a new resolver by selecting **+ Create**.
+
+When you edit a single resolver, the **Edit resolver** page opens. You can:
+
+* Update the resolver's policy definition and optionally the data source. Changing the data source overwrites the resolver's current policy definition.
+
+* Change the type and field that the resolver targets. 
+
+* Test and debug the resolver's configuration. Select **Run test** to see sample resolver output that you can validate against the schema. 
 
 ## GraphQL context