> For the complete documentation index, see [llms.txt](https://docs.enate.net/enate-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/enate-help/work-manager/work-manager/appendix/how-to-enable-spell-check-in-enate.md).
# How to enable spell check in Enate
To ensure that you are able to carry out your work in Enate spelling error-free, you can enable spell check in your web browser to help check your spelling as you go about your tasks.
Below are the steps to activate spell checker in three of the most popular browsers: Google Chrome, Mozilla Firefox and Microsoft Edge.
### Google Chrome
1. Open Chrome Settings:
* Click on the three vertical dots in the upper right corner.
* Select Settings.
2. Access Language Settings:
* In the settings menu, type "language" in the search box.
* Click on Languages.
3. Enable Spell Check:
* Under the Spell check section, choose between Basic spell check or Enhanced spell check.
* You can also add new languages if necessary.
### Mozilla Firefox
1. Open Firefox Menu:
* Click on the three horizontal lines in the upper right corner.
* Select Settings.
2. Navigate to Language Settings:
* In the left sidebar, select General.
* Scroll down to the Language and Appearance section.
3. Turn on Spell Check:
* Check the box next to Check my spelling as I type.
### Microsoft Edge
1. Open Edge Settings:
* Click on the three horizontal dots in the top-right corner.
* Select Settings.
2. Find Language Options:
* Scroll down and click on Languages.
3. Enable Spell Check:
* Toggle on the option for Enable spell check for your preferred languages.
---
# 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.enate.net/enate-help/work-manager/work-manager/appendix/how-to-enable-spell-check-in-enate.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.
