> For the complete documentation index, see [llms.txt](https://gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.com/docs/help/contribute.md).

# Contribute to the docs

Suggest improvements to GitBook's documentation

Thank you for investing your time in contributing to GitBook's documentation. Every contribution is reviewed by the team.

This documentation is published with GitBook, using Git Sync to keep the site up to date with the [`public-docs` repository](https://github.com/GitbookIO/public-docs) on GitHub. Any change that's reviewed, approved, and merged into the repository is deployed automatically.

#### What to contribute

* Corrections — inaccurate steps, outdated screenshots, broken links, typos.
* Clarifications — a section that's technically correct but hard to follow.
* Missing detail — an edge case or error message the page doesn't cover.

For problems with GitBook itself rather than the documentation, see Report a bug.

#### How to submit a change

1. Open a pull request against the `public-docs` repository.
2. Describe what you changed and why. Link to the published page you're editing.
3. A member of the documentation team reviews it. Once it's approved and merged, the change deploys automatically.

{% embed url="<https://github.com/GitbookIO/public-docs>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://gitbook.com/docs/help/contribute.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.