Update icons docs

components/icons.mdx

@@ -1,7 +1,7 @@
 ---
 title: "Icons"
 description: "Use icons from popular icon libraries"
-icon: 'flag'
+icon: "flag"
 ---
 
 <Icon icon="flag" size={32} />
@@ -11,22 +11,23 @@ icon: 'flag'
 ```mdx Icon Example
 <Icon icon="flag" size={32} />
 ```
+
 </RequestExample>
 
 ## Inline Icons
 
 The icon will be placed inline when used in a paragraph.
 
 ```markdown Inline Icon Example
-<Icon icon="flag" iconType="solid" /> The documentation you want, effortlessly 
+<Icon icon="flag" iconType="solid" /> The documentation you want, effortlessly. 
 ```
 
-<Icon icon="flag" iconType="solid" /> The documentation you want, effortlessly
+<Icon icon="flag" iconType="solid" /> The documentation you want, effortlessly.
 
 ### Props
 
 <ResponseField name="icon" type="string" required>
-  A [Font Awesome](https://fontawesome.com/icons) or [Lucide](https://lucide.dev/icons) icon
+  A [Font Awesome](https://fontawesome.com/icons) icon, [Lucide](https://lucide.dev/icons) icon, or URL pointing to an icon.
 </ResponseField>
 
 <ResponseField name="iconType" type="string">
@@ -39,4 +40,4 @@ The icon will be placed inline when used in a paragraph.
 
 <ResponseField name="size" type="number">
   The size of the icon in pixels
-</ResponseField>
+</ResponseField>

navigation.mdx

@@ -9,7 +9,7 @@ The [navigation](settings#param-navigation) property in [docs.json](settings) de
 With proper navigation configuration, you can organize your content into a logical hierarchy that makes it easy for users to find exactly what they're looking for.
 
 <Info>
-Do not use `api` as a title for any navigation element. The `/api` path is reserved in production and will cause pages to return 404 errors if their URLs contain `/api`.
+  Do not use `api` as a title for any navigation element. The `/api` path is reserved in production and will cause pages to return 404 errors if their URLs contain `/api`.
 </Info>
 
 ## Pages
@@ -45,7 +45,7 @@ Pages is an array where each entry must be a reference to the path of a [page fi
 
 ## Groups
 
-Use groups to organize your navigation into sections. Groups can be nested within each other and labeled with tags.
+Use groups to organize your navigation into sections. Groups can be nested within each other, labeled with tags, and styled with icons.
 
 <img
   className="block dark:hidden pointer-events-none"
@@ -63,15 +63,18 @@ Use groups to organize your navigation into sections. Groups can be nested withi
     "groups": [
       {
         "group": "Getting Started",
+		"icon": "play",
         "pages": [
           "quickstart",
           {
             "group": "Editing",
+			"icon": "pencil",
             "pages": [
 				"installation",
 				"editor",
 				{
 					"group": "Nested group",
+					"icon": "code",
 					"pages": [
 						"navigation",
 						"code"
@@ -83,6 +86,7 @@ Use groups to organize your navigation into sections. Groups can be nested withi
       },
       {
         "group": "Writing Content",
+ 		"icon": "notebook-text",
         "tag": "NEW",
         "pages": ["writing-content/page", "writing-content/text"]
       }
@@ -516,4 +520,4 @@ This way, you can create a very complex navigation structure that is easy to man
 }
 ```
 
-</CodeGroup>
+</CodeGroup>

pages.mdx

@@ -1,7 +1,7 @@
 ---
 title: "Pages"
 description: "Pages are the building blocks of your documentation"
-icon: 'letter-text'
+icon: "letter-text"
 ---
 
 ## Basics
@@ -39,7 +39,7 @@
 
 ## Icons
 
-You can set an icon for your sidebar item like the one for this page. You can set icons by using the `icon` metadata.
+Add an icon next to your page's sidebar title by including the `icon` field in your page's frontmatter.
 
 ```mdx
 ---
@@ -48,9 +48,9 @@
 ---
 ```
 
-You can set icons from [Font Awesome](https://fontawesome.com/icons) and [Lucide](https://lucide.dev/icons), depending on the [icon library setting](settings#param-icons).
+You can set icons from a URL, [Font Awesome](https://fontawesome.com/icons), or [Lucide](https://lucide.dev/icons). Choose your preferred icon library (Font Awesome or Lucide) with the [icon library setting](settings#param-icons).
 
-You can also set the icon type for Font Awesome icons (optional). If not set, the icon type will be regular.
+For Font Awesome icons, you can optionally set the icon type. If not set, the icon type will be regular.
 
 ```mdx
 ---
@@ -116,7 +116,6 @@
 This mode offers a blank canvas, which is ideal for creating a "landing page" or any page where
 you want a clean, distraction-free environment.
 
-
 ```mdx
 ---
 mode: "custom"
@@ -128,7 +127,6 @@
 Center Mode removes the sidebar and the table of contents, and centers the page content. This mode is great for changelogs
 or any page where you want to focus on the content.
 
-
 ```mdx
 ---
 mode: "center"
@@ -164,7 +162,7 @@
 
 ## Internal Search Optimization
 
 You can also enhance a specific page's discoverability in the built-in search by
 providing `keywords` in your metadata. These keywords won't appear as part of the page
 content or in search results, but users that search for them will be shown the page as a result.
 
@@ -172,4 +170,4 @@
 ---
 keywords: ['search', 'indexing']
 ---
-```
+```

settings.mdx

@@ -96,7 +96,7 @@
       The eyebrows style of the content. Defaults to `section`.
     </ResponseField>
     <ResponseField name="codeblocks" type="&quot;system&quot; | &quot;dark&quot;">
       The codeblock theme. Defaults to `system`.
     </ResponseField>
   </Expandable>
 </ResponseField>
@@ -115,7 +115,7 @@
 
   <Expandable title="Fonts">
     <ResponseField name="family" type="string" required>
       The font family, such as "Open Sans", "Playfair Display"
     </ResponseField>
     <ResponseField name="weight" type="number">
       The font weight, such as 400, 700. Precise font weights such as 550 are supported for variable fonts.
@@ -124,7 +124,7 @@
       The font source, such as https://mintlify-assets.b-cdn.net/fonts/Hubot-Sans.woff2
     </ResponseField>
     <ResponseField name="format" type="&quot;woff&quot; | &quot;woff2&quot;">
       The font format, can be one of woff, woff2
     </ResponseField>
     <ResponseField name="heading" type="object">
 
@@ -216,20 +216,21 @@
 ### Structure
 
 <ResponseField name="navbar" type="object">
   Navbar content and settings
 
   <Expandable title="Navbar">
     <ResponseField name="links" type="array of object">
       The links in the navbar
 
       <Expandable title="Links">
         <ResponseField name="label" type="string" required>
+          The display text for a link.
         </ResponseField>
         <ResponseField name="href" type="string (uri)" required>
-          A valid path or external link
+          A valid path or external link.
         </ResponseField>
         <ResponseField name="icon" type="string | object">
-          The icon to be displayed in the navbar.
+          The icon displayed for a link. Can be a URL, Font Awesome icon, or Lucide icon.
         </ResponseField>
       </Expandable>
     </ResponseField>
@@ -499,7 +500,7 @@
 
   <Expandable title="Api">
     <ResponseField name="openapi" type="string or array or object">
       A string or an array of strings of absolute or relative urls pointing to the OpenAPI file(s)
 
       <Expandable title="Openapi">
         <ResponseField name="source" type="string">