> For the complete documentation index, see [llms.txt](https://docs.airops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airops.com/actions/grids/review-content-in-the-grid.md).

# Review Content in the Grid

Review, score, edit, and collaborate on content in a Grid

AirOps Grid provides comprehensive tools for reviewing, editing, and collaborating on content directly within the interface. Whether you're working with HTML, Markdown, or comparing content differences, the Grid offers a seamless editing experience.

## Content Editors

* [**Review HTML Content**](/actions/grids/review-content-in-the-grid/review-html-content.md): View and edit HTML content with both rendered and code views
* [**Review Markdown Content**](/actions/grids/review-content-in-the-grid/review-markdown-content.md): Work with formatted Markdown text directly in the Grid
* [**Compare Content Difference**](/actions/grids/review-content-in-the-grid/compare-content-difference.md): Review and accept/reject suggested changes to your content

## Quality Scoring

* [**Content Review and Quality Scores**](/actions/grids/review-content-in-the-grid/content-review.md): Automatically check enabled Playbook and Workflow outputs for AI Discoverability and Brand Adherence

## Team Collaboration

* [**Real-time Collaboration**](/actions/grids/review-content-in-the-grid/collaboration.md): Work together with comments, suggestion mode, version history, and live presence indicators (Enterprise)


---

# 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://docs.airops.com/actions/grids/review-content-in-the-grid.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.