> For the complete documentation index, see [llms.txt](https://docs.openreview.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openreview.net/v1/how-to-guides/submissions-comments-reviews-and-decisions/how-to-submit-a-review-revision.md).
# How to submit a Review Revision
If the PCs have activated the Review Revision Stage, reviewers will be able to edit their posted reviews. Reviewers will be able to submit multiple Review Revisions, with the last one being the final one shown in the Official Review.
To post a review revision:
1. Click on the "Edit" button, found next to the title of the review note.
2. Click on "Review Revision". This will open the note editor, where you will be able to edit the review. Note you will only be able to edit the fields that the PCs allow to be edited (so you might not be able to edit all the original fields of your review)
3. Edit the fields and then save your changes.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.openreview.net/v1/how-to-guides/submissions-comments-reviews-and-decisions/how-to-submit-a-review-revision.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 `build a script that syncs our docs to a CMS` 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.
