From 237fe58d3d6092ff5802394ef2dc9325dffd43e3 Mon Sep 17 00:00:00 2001
From: Juanito Fatas <me@juanitofatas.com>
Date: Wed, 19 Jul 2023 09:53:46 +0900
Subject: [PATCH] Apply suggestions from code review

Co-authored-by: Michael Belton <119824349+mbelton-buildkite@users.noreply.github.com>
---
 pages/apis/graphql/graphql_cookbook.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/pages/apis/graphql/graphql_cookbook.md b/pages/apis/graphql/graphql_cookbook.md
index c8c2eaa98b..a98f4018c6 100644
--- a/pages/apis/graphql/graphql_cookbook.md
+++ b/pages/apis/graphql/graphql_cookbook.md
@@ -678,12 +678,12 @@ mutation UpdateSessionDuration {
 }
 ```
 
-### Update the revoke inactive tokens after
+### Update when inactive access tokens are revoked
 
-You can control how many days to revoke inactive API access tokens. By default that's `NEVER` revoke inactive API access tokens, but you can set to 30, 60, 90, 180, 365 days. This is only available to Enterprise customers.
+On the Enterprise plan, you can control when inactive API access tokens are revoked. By default, they are never (`NEVER`) revoked, but you can set your token expiry policy to either 30, 60, 90, 180, or 365 days.
 
 ```graphql
-mutation UpdateRevokeInactiveTokenAfter {
+mutation UpdateRevokeInactiveTokenPeriod {
   organizationRevokeInactiveTokensAfterUpdate(input: {
     organizationId: "organization-id",
     revokeInactiveTokensAfter: DAYS_30