> For the complete documentation index, see [llms.txt](https://help.brieftech.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.brieftech.ai/how-to-guides/review.md).
# Review Documents
The human-review pass: verify and correct what the AI produced before building the index.
{% hint style="info" %}
**New to reviewing?** Walk through a full review pass end to end in the [Review an AI-Analysed Matter](/get-started/review-an-ai-analysed-matter.md) tutorial, then use the how-tos below for individual tasks.
{% endhint %}
* [Bulk-edit metadata across many documents](/how-to-guides/review/bulk-edit-metadata.md) — Update a metadata field on many documents at once instead of one by one.
* [Refine descriptions using your own edits as examples](/how-to-guides/review/refine-descriptions-from-examples.md) — Edit a few descriptions the way you want them, then have BriefTech rewrite the rest of the selection to match.
* [Translate document descriptions](/how-to-guides/review/translate-document-descriptions.md) — Translate one or many descriptions into Bahasa Malaysia, Chinese (Simplified), French, or English in one step.
* [Customise the file-list columns](/how-to-guides/review/customize-file-list-columns.md) — Show, hide, and reorder the columns in the on-screen document list.
* To correct a single document, edit inline in the 
tab — see [Document metadata fields](/reference/document-metadata-fields.md).
* To narrow the list to one kind of document, tick a class in the **Classes** group of the left-hand panel in the tab — the classes, and what each covers, are listed in [Document classes](/reference/document-classes.md).
***
**Next step:** with the details reviewed, move on to the [Document Index](/how-to-guides/index.md). BriefTech builds it for you from the documents in your matter — your job there is to refine it into the ordered spine of your court bundle.
---
# 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://help.brieftech.ai/how-to-guides/review.md?ask=&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.