diff --git a/open-api/rest-catalog-open-api.py b/open-api/rest-catalog-open-api.py
index 77dcad9cfba6..b1d68978e027 100644
--- a/open-api/rest-catalog-open-api.py
+++ b/open-api/rest-catalog-open-api.py
@@ -80,7 +80,7 @@ class Namespace(BaseModel):
 class PageToken(BaseModel):
     __root__: str = Field(
         ...,
-        description='An opaque token which allows clients to make use of pagination for a list API (e.g. ListTables). Clients will initiate the first paginated request by sending an empty `pageToken` e.g. `GET /tables?pageToken` or `GET /tables?pageToken=` signaling to the service that the response should be paginated.\nServers that support pagination will recognize `pageToken` and return a `next-page-token` in response if there are more results available. After the initial request, it is expected that the value of `next-page-token` from the last response is used in the subsequent request. Servers that do not support pagination will ignore `next-page-token` and return all results.',
+        description='An opaque token which allows clients to make use of pagination for a list API (e.g. ListTables). Clients will initiate the first paginated request by sending an empty `pageToken` e.g. `GET /tables?pageToken=` signaling to the service that the response should be paginated.\nServers that support pagination will recognize `pageToken` and return a `next-page-token` in response if there are more results available. After the initial request, it is expected that the value of `next-page-token` from the last response is used in the subsequent request. Servers that do not support pagination will ignore `pageToken` and return all results.',
     )
 
 
diff --git a/open-api/rest-catalog-open-api.yaml b/open-api/rest-catalog-open-api.yaml
index 77aabc834adb..6da73b313647 100644
--- a/open-api/rest-catalog-open-api.yaml
+++ b/open-api/rest-catalog-open-api.yaml
@@ -1611,12 +1611,12 @@ components:
     PageToken:
       description:
         An opaque token which allows clients to make use of pagination for a list API (e.g. ListTables). 
-        Clients will initiate the first paginated request by sending an empty `pageToken` e.g. `GET /tables?pageToken` or `GET /tables?pageToken=`
+        Clients will initiate the first paginated request by sending an empty `pageToken` e.g. `GET /tables?pageToken=`
         signaling to the service that the response should be paginated.
 
         Servers that support pagination will recognize `pageToken` and return a `next-page-token` in response if there are more results available.
         After the initial request, it is expected that the value of `next-page-token` from the last response is used in the subsequent request.
-        Servers that do not support pagination will ignore `next-page-token` and return all results.
+        Servers that do not support pagination will ignore `pageToken` and return all results.
       type: string
 
     TableIdentifier: