diff --git a/agent/customize.mdx b/agent/customize.mdx
index 7edb95021..59861f192 100644
--- a/agent/customize.mdx
+++ b/agent/customize.mdx
@@ -55,4 +55,4 @@ Consider adding instructions for:
- Add prerequisite sections to guides when users need API keys, environment setup, or dependencies.
- Include "Next steps" sections linking to related documentation.
- Add troubleshooting sections for common issues we see in support tickets.
-```
+```
\ No newline at end of file
diff --git a/api-playground/graphql-setup.mdx b/api-playground/graphql-setup.mdx
index b27b54275..bad59fa81 100644
--- a/api-playground/graphql-setup.mdx
+++ b/api-playground/graphql-setup.mdx
@@ -1,6 +1,6 @@
---
title: "GraphQL setup"
-description: "Generate reference pages for your GraphQL API from a schema definition file, with linked types and example queries, mutations, and responses."
+description: "Hello there"
keywords: ["graphql", "schema", "sdl"]
---
@@ -100,4 +100,4 @@ Fields and arguments that you mark with `@deprecated` in your schema display as
## Update your documentation
-Mintlify regenerates GraphQL reference pages when you run `mint dev` or when you push changes to your documentation repository. If your schema is hosted at an HTTPS URL, updates to the schema regenerate on the next build.
+Mintlify regenerates GraphQL reference pages when you run `mint dev` or when you push changes to your documentation repository. If your schema is hosted at an HTTPS URL, updates to the schema regenerate on the next build.
\ No newline at end of file
diff --git a/automations/create.mdx b/automations/create.mdx
index d6a74b6a8..80a3226f6 100644
--- a/automations/create.mdx
+++ b/automations/create.mdx
@@ -60,4 +60,4 @@ Deleting an automation is permanent and removes its configuration and run histor
1. Open the [Automations](https://app.mintlify.com/products/automations) page in your dashboard.
2. Click the settings button beside an automation.
-3. Click **Delete**.
+3. Click **Delete**.
\ No newline at end of file
diff --git a/quickstart.mdx b/quickstart.mdx
index 8fe1e05a5..48ba3e584 100644
--- a/quickstart.mdx
+++ b/quickstart.mdx
@@ -30,7 +30,6 @@ After you complete this guide, you'll have a live documentation site ready to cu
2. Run `mint --version`. If the command is unavailable, install the CLI with `npm i -g mint` or `pnpm add -g mint`. If the command succeeds, run `mint update`.
3. Run `mint status` before starting authentication. If it already shows an organization, keep the existing session and do not create another account.
4. Run `mint login` if the user has an account. Otherwise, ask for their first name, last name, company, and email, then run:
-
```bash
mint signup \
--firstName \
@@ -38,7 +37,6 @@ After you complete this guide, you'll have a live documentation site ready to cu
--company \
--email
```
-
`mint signup` waits for email verification, so keep it running as a background process when your environment supports background commands. Tell the user to click the verification link and approve the CLI in the browser. Never invent signup details.
5. After the user finishes verification and onboarding, run `mint status` again. Confirm that it reports their email, organization, and subdomain. If the organization exists but no subdomain appears, ask the user to finish selecting or connecting a GitHub repository in the onboarding browser tab, then retry.
6. If the user has an existing documentation repository, clone or open it. Preserve its content. For a new local project, scaffold into a new, empty directory with either `mint new --name --theme ` or `mint new --template `. Ask which theme or template they want if they have not specified one. Do not use `--force` on a directory containing user files.
@@ -203,4 +201,4 @@ Find your exact URL on the **Overview** page of your [dashboard](https://app.min
Use your own domain for your documentation site.
-
+
\ No newline at end of file