caps page metadata

Author: mxbaylee

advanced/user-auth/overview.mdx

@@ -65,9 +65,9 @@ User Auth is an enterprise feature. {
 If you return API Playground inputs in the user info, they will automatically be prefilled in the API Playground. Make sure the name of the field in the user info is an exact match of the name in the API Playground.
 ### Showing/Hiding Pages
 
-By default, every page is visible to every user. If you want to restrict which pages are visible to your users, you can add a `groups` field in your page metadata.
+By default, every page is visible to every user. If you want to restrict which pages are visible to your users, you can add a `groups` field in your Page Metadata.
 When determining which pages to show to the user, Mintlify will check which groups the user belongs to.
-If the user is not in any of the groups listed in the page metadata, the page will not be shown.
+If the user is not in any of the groups listed in the Page Metadata, the page will not be shown.
 
 ```md
 ---
@@ -77,12 +77,12 @@ groups: ['admin']
 ---
 ```
 
-Here's a table that displays whether a page is shown for different combinations of `groups` in UserInfo and page metadata:
+Here's a table that displays whether a page is shown for different combinations of `groups` in UserInfo and Page Metadata:
 
 |                                    | `groups` not in UserInfo | `groups: []` in UserInfo | `groups: ['admin']` in UserInfo |
 |:-----------------------------------|:------------------------:|:-------------------------:|:--------------------------------:|
 | `groups` not in metadata           |                        ✅ |                        ✅ |                               ✅ |
 | `groups: []` in metadata           |                        ❌ |                        ❌ |                               ❌ |
 | `groups: ['admin']` in metadata    |                        ❌ |                        ❌ |                               ✅ |
 
-<Note>Note that an empty array in the page metadata is interpreted as "No groups should see this page."</Note>
+<Note>Note that an empty array in the Page Metadata is interpreted as "No groups should see this page."</Note>

api-playground/mdx/authentication.mdx

@@ -21,7 +21,7 @@ The page's authentication method will override mint.json if both are set.
 }
 ```
 
-```md page metadata
+```md Page Metadata
 ---
 title: "Your page title"
 authMethod: "bearer"
@@ -42,7 +42,7 @@ authMethod: "bearer"
 }
 ```
 
-```md page metadata
+```md Page Metadata
 ---
 title: "Your page title"
 authMethod: "basic"
@@ -64,7 +64,7 @@ authMethod: "basic"
 }
 ```
 
-```md page metadata
+```md Page Metadata
 ---
 title: "Your page title"
 authMethod: "key"
@@ -78,7 +78,7 @@ authMethod: "key"
 The "none" authentication method is useful to disable authentication on a specific endpoint after setting a default in mint.json.
 
 <CodeGroup>
-```md page metadata
+```md Page Metadata
 ---
 title: "Your page title"
 authMethod: "none"

api-playground/troubleshooting.mdx

@@ -27,7 +27,7 @@ Here's a list of common issues we've seen customers run into:
   </Accordion>
 
   <Accordion title="One of my OpenAPI pages is completely blank">
-    This is usually caused by a misspelled `openapi` field in the page metadata. Make sure
+    This is usually caused by a misspelled `openapi` field in the Page Metadata. Make sure
     the HTTP method and path match the HTTP method and path in the OpenAPI document exactly.
 
     Here's an example of how things might go wrong:

page.mdx

@@ -44,7 +44,7 @@ description: "Setting the title and metadata for navigation and SEO"
 ## API Pages
 
 API pages let you build interactive API playgrounds. To create an API page, you
-must set an `api` or `openapi` property in the page metadata.
+must set an `api` or `openapi` property in the Page Metadata.
 
 Learn more about API playgrounds in [our demo](/api-playground).
 

settings/seo.mdx

@@ -47,7 +47,7 @@ title: 'Your Example Page Title'
 
 <Warning>
 
-Meta tags with colons need to be typed with quotes around them when you put them in the page metadata.
+Meta tags with colons need to be typed with quotes around them when you put them in the Page Metadata.
 
 </Warning>
 

settings/versioning.mdx

@@ -19,7 +19,7 @@ Add `"versions": ["v2", "v1"]` to your `mint.json` file where `v1` and `v2` are
 
 The best way to specify page versions is by adding a version value to a group in the navigation. When you specify the version of a group, that version is applied to all pages within that group.
 
-You can also specify the version of a single page in the page metadata. Versions on individual pages always take precedence.
+You can also specify the version of a single page in the Page Metadata. Versions on individual pages always take precedence.
 
 <CodeGroup>
 ```json Groups (mint.json)