> For the complete documentation index, see [llms.txt](https://help.kenyalaw.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.kenyalaw.org/personalised-research/commenting-in-a-document.md).
# Commenting in a document
Follow the steps below to make private comments on a document.
1. Open the document you want to work on.
2. Ensure you are logged into your account to enable the commenting feature.
3. Navigate through the document and locate the section you want to comment on.
4. Click and drag your cursor over the specific text to highlight it, a pop-up menu appears next to the highlighted text.
5. Click the"**Comment**" option in the pop-up.
6. Type your comment in the text box.
7. Click "Save" to confirm your comment and ensure the document is saved if it has not already been saved.
8. Click the dropdown menu to access the "**Edit**" or "**Delete**" options, allowing you to modify or remove your comment as needed.
9. To view all your annotated documents, navigate to the "Saved Documents" section of your profile. Look for documents with the **comment icon**, which indicates annotations.
10. Click the comment icons to view, edit, or delete annotations on your saved documents.
### Tip:
Deleting all comments from a saved document does not remove the document from your saved list. If you want to see the number of comments on a document, check the comment icons—they display the count.
---
# 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.kenyalaw.org/personalised-research/commenting-in-a-document.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.
