all integrations have quotes now (#568)

baell · web-flow · commit 5e861eea947e · 2025-03-12T15:42:33.000-07:00
* all integrations have quotes now

* fixed 2 broken links

* vale found the the
diff --git a/advanced/mcp/generate.mdx b/advanced/mcp/generate.mdx
@@ -6,7 +6,7 @@ description: "Learn how to set up your own MCP Server"
 <Tip>
   This page is dedicated to setting up your own MCP Server. If you are looking
   for information on using the Mintlify MCP Server, please refer to the
-  [Installing and using the Mintlify MCP Server](/advanced/mcp/cli) page.
+  [Installing and using the Mintlify MCP Server](/advanced/mcp/quickstart) page.
 </Tip>
 
 ## Get started
diff --git a/advanced/mcp/quickstart.mdx b/advanced/mcp/quickstart.mdx
@@ -19,7 +19,7 @@ Mintlify enables you to create an MCP server that allows AI tools to interact wi
 ## Install the MCP server
 
 <Tip>
-    This page is dedicated to the Mintlify MCP Server. If you are looking for information on generating your MCP, please refer to the [MCP Generator](/advanced/mcp/overview) page.
+    This page is dedicated to the Mintlify MCP Server. If you are looking for information on generating your MCP, please refer to the [MCP Generator](/advanced/mcp/generate) page.
 </Tip>
 
 ## Example installation with the Mintlify MCP server
@@ -54,7 +54,7 @@ To use the Mintlify MCP server you will need an [API key](https://mintlify.com/d
 ## Use your server with Claude
 
 <Note>
-    Download the the [Claude Desktop App](https://claude.ai/download)
+    Download the [Claude Desktop App](https://claude.ai/download)
 </Note>
 
 Once you have the Claude Desktop App installed, follow these steps:
diff --git a/integrations/analytics/clearbit.mdx b/integrations/analytics/clearbit.mdx
@@ -7,15 +7,15 @@ Add the following to your `docs.json` file to send analytics to Clearbit.
 <CodeGroup>
 
 ```json Analytics options in docs.json
-integrations: {
+"integrations": {
     "clearbit": {
         "publicApiKey": "required"
     }
 }
 ```
 
 ```json Example
-integrations: {
+"integrations": {
     "clearbit": {
         "publicApiKey": "pk_1a1882"
     }
diff --git a/integrations/analytics/fathom.mdx b/integrations/analytics/fathom.mdx
@@ -9,15 +9,15 @@ You can get the `siteId` from your script settings.
 <CodeGroup>
 
 ```json Analytics options in docs.json
-integrations: {
+"integrations": {
     "fathom": {
         "siteId": "required"
     }
 }
 ```
 
 ```json Example
-integrations: {
+"integrations": {
     "fathom": {
         "siteId": "YSVMSDAY"
     }
diff --git a/integrations/analytics/google-analytics.mdx b/integrations/analytics/google-analytics.mdx
@@ -25,7 +25,7 @@ Your Measurement ID looks like `G-XXXXXXX` and will show up under Stream Details
 Add your Measurement ID to your `docs.json` file like so:
 
 ```json docs.json
-integrations: {
+"integrations": {
     "ga4": {
         "measurementId": "G-XXXXXXX"
     }
diff --git a/integrations/analytics/google-tag-manager.mdx b/integrations/analytics/google-tag-manager.mdx
@@ -9,15 +9,15 @@ You are responsible for setting up cookie consent banners with Google Tag Manage
 <CodeGroup>
 
 ```json Analytics options in docs.json
-integrations: {
+"integrations": {
     "gtm": {
         "tagId": "required"
     }
 }
 ```
 
 ```json Example
-integrations: {
+"integrations": {
     "gtm": {
         "tagId": "GTM-MGBL4PW"
     }
diff --git a/integrations/analytics/heap.mdx b/integrations/analytics/heap.mdx
@@ -7,15 +7,15 @@ Add the following to your `docs.json` file to send analytics to Heap.
 <CodeGroup>
 
 ```json Analytics options in docs.json
-integrations: {
+"integrations": {
     "heap": {
         "appId": "required"
     }
 }
 ```
 
 ```json Example
-integrations: {
+"integrations": {
     "heap": {
         "appId": "1234567890"
     }
diff --git a/integrations/analytics/hotjar.mdx b/integrations/analytics/hotjar.mdx
@@ -5,7 +5,7 @@ title: "HotJar"
 Add the following to your `docs.json` file to send analytics to HotJar.
 
 ```json Analytics options in docs.json
-integrations: {
+"integrations": {
     "hotjar": {
         "hjid": "required",
         "hjsv": "required"
diff --git a/integrations/analytics/koala.mdx b/integrations/analytics/koala.mdx
@@ -7,15 +7,15 @@ Add the following to your `docs.json` file to send analytics to Koala.
 <CodeGroup>
 
 ```json Analytics options in docs.json
-integrations: {
+"integrations": {
     "koala": {
         "publicApiKey": "required"
     }
 }
 ```
 
 ```json Example
-integrations: {
+"integrations": {
     "koala": {
         "publicApiKey": "pk_1a1882"
     }
diff --git a/integrations/analytics/logrocket.mdx b/integrations/analytics/logrocket.mdx
@@ -5,7 +5,7 @@ title: "LogRocket"
 Add the following to your `docs.json` file to send analytics to LogRocket.
 
 ```json Analytics options in docs.json
-integrations: {
+"integrations": {
     "logrocket": {
         "apiKey": "required"
     }
diff --git a/integrations/analytics/mixpanel.mdx b/integrations/analytics/mixpanel.mdx
@@ -5,7 +5,7 @@ title: "Mixpanel"
 Add the following to your `docs.json` file to send analytics to Mixpanel.
 
 ```json Analytics options in docs.json
-integrations: {
+"integrations": {
     "mixpanel": {
         "projectToken": "required"
     }
diff --git a/integrations/analytics/pirsch.mdx b/integrations/analytics/pirsch.mdx
@@ -9,15 +9,15 @@ You can get your site ID from Settings \> Developer \> Identification Code.
 <CodeGroup>
 
 ```json Analytics options in docs.json
-integrations: {
+"integrations": {
     "pirsch": {
         "id": "required"
     }
 }
 ```
 
 ```json Example
-integrations: {
+"integrations": {
     "pirsch": {
         "id": "8Kw7OKxBfswOjnKGZa7P9Day8JmVYwTp"
     }
diff --git a/integrations/analytics/plausible.mdx b/integrations/analytics/plausible.mdx
@@ -13,7 +13,7 @@ Add your site's domain to `docs.json` to send analytics to Plausible.
 <CodeGroup>
 
 ```json Analytics options in docs.json
-integrations: {
+"integrations": {
     "plausible": {
         "domain": "required",
         "server": "optional"
@@ -22,7 +22,7 @@ integrations: {
 ```
 
 ```json Example
-integrations: {
+"integrations": {
     "plausible": {
         "domain": "docs.domain.com"
     }
diff --git a/integrations/analytics/posthog.mdx b/integrations/analytics/posthog.mdx
@@ -9,7 +9,7 @@ You only need to include `apiHost` if you are self-hosting PostHog. We send even
 <CodeGroup>
 
 ```json Analytics options in docs.json
-integrations: {
+"integrations": {
     "posthog": {
         "apiKey": "required",
         "apiHost": "optional"
@@ -18,7 +18,7 @@ integrations: {
 ```
 
 ```json Example
-integrations: {
+"integrations": {
     "posthog": {
         "apiKey": "phc_TXdpocbYTeZVm5VJmMzHTMrCofBQu3e0kN7HGMNGTVW"
     }
diff --git a/integrations/analytics/segment.mdx b/integrations/analytics/segment.mdx
@@ -7,15 +7,15 @@ Add your Segment write key to your `docs.json` file to send analytics to Segment
 <CodeGroup>
 
 ```json Analytics options in docs.json
-integrations: {
+"integrations": {
     "segment": {
         "key": "required",
     }
 }
 ```
 
 ```json Example
-integrations: {
+"integrations": {
     "segment": {
         "key": "nqJxiRG15Y6M594P8Sb8ESEciU3VC2"
     }

Original file line number	Diff line number	Diff line change
@@ -7,15 +7,15 @@ Add the following to your `docs.json` file to send analytics to Clearbit.
`7`	`7`	`<CodeGroup>`
`8`	`8`
`9`	`9`	```json Analytics options in docs.json
`10`		`-integrations: {`
	`10`	`+"integrations": {`
`11`	`11`	`"clearbit": {`
`12`	`12`	`"publicApiKey": "required"`
`13`	`13`	`}`
`14`	`14`	`}`
`15`	`15`	```
`16`	`16`
`17`	`17`	```json Example
`18`		`-integrations: {`
	`18`	`+"integrations": {`
`19`	`19`	`"clearbit": {`
`20`	`20`	`"publicApiKey": "pk_1a1882"`
`21`	`21`	`}`
Original file line number	Diff line number	Diff line change
@@ -9,15 +9,15 @@ You can get the `siteId` from your script settings.
`9`	`9`	`<CodeGroup>`
`10`	`10`
`11`	`11`	```json Analytics options in docs.json
`12`		`-integrations: {`
	`12`	`+"integrations": {`
`13`	`13`	`"fathom": {`
`14`	`14`	`"siteId": "required"`
`15`	`15`	`}`
`16`	`16`	`}`
`17`	`17`	```
`18`	`18`
`19`	`19`	```json Example
`20`		`-integrations: {`
	`20`	`+"integrations": {`
`21`	`21`	`"fathom": {`
`22`	`22`	`"siteId": "YSVMSDAY"`
`23`	`23`	`}`
Original file line number	Diff line number	Diff line change
@@ -25,7 +25,7 @@ Your Measurement ID looks like `G-XXXXXXX` and will show up under Stream Details
`25`	`25`	Add your Measurement ID to your `docs.json` file like so:
`26`	`26`
`27`	`27`	```json docs.json
`28`		`-integrations: {`
	`28`	`+"integrations": {`
`29`	`29`	`"ga4": {`
`30`	`30`	`"measurementId": "G-XXXXXXX"`
`31`	`31`	`}`
Original file line number	Diff line number	Diff line change
`@@ -9,15 +9,15 @@ You are responsible for setting up cookie consent banners with Google Tag Manage`
`9`	`9`	`<CodeGroup>`
`10`	`10`
`11`	`11`	```json Analytics options in docs.json
`12`		`-integrations: {`
	`12`	`+"integrations": {`
`13`	`13`	`"gtm": {`
`14`	`14`	`"tagId": "required"`
`15`	`15`	`}`
`16`	`16`	`}`
`17`	`17`	```
`18`	`18`
`19`	`19`	```json Example
`20`		`-integrations: {`
	`20`	`+"integrations": {`
`21`	`21`	`"gtm": {`
`22`	`22`	`"tagId": "GTM-MGBL4PW"`
`23`	`23`	`}`
Original file line number	Diff line number	Diff line change
`@@ -5,7 +5,7 @@ title: "LogRocket"`
`5`	`5`	Add the following to your `docs.json` file to send analytics to LogRocket.
`6`	`6`
`7`	`7`	```json Analytics options in docs.json
`8`		`-integrations: {`
	`8`	`+"integrations": {`
`9`	`9`	`"logrocket": {`
`10`	`10`	`"apiKey": "required"`
`11`	`11`	`}`