> For the complete documentation index, see [llms.txt](https://docs.prestashop-project.org/translating-prestashop/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prestashop-project.org/translating-prestashop/translating-prestashop-software-basics/translating-on-crowdin/proofreading-all-you-need-to-know.md).
# Proofreading: All You Need to Know
Interested in becoming a proofreader? Here's everything you need to know.
## 🤔 What's the difference between translation and proofreading?
Proofreading and translation are two different things. While a translator translates source strings into a target language, **a proofreader checks translations to make sure they are correct.**
This means checking for **typos and vocabulary** (using the [PrestaShop Glossary](/translating-prestashop/resources/resources/prestashop-glossary.md)), but also making sure the **translations are consistent and harmonized** throughout the whole file.
Once a translation string has been checked by a proofreader, it can then be **approved.** A green checkmark (✅) appears next to translated and approved strings.
An example of translated and approved strings
You can also check if a string has been approved or not by looking at the translations section, under the string. **Two usernames will appear under an approved string**: the first username is the translator's username, while the second one is the proofreader's (along with a green checkmark):
An example of approved string.
## 🧐 How do I become a Proofreader?
It's simple: **send us a message** on the [Slack translation channel ](https://join.slack.com/t/prestashop/shared_invite/zt-dkmbz5qf-I~FlEWwmRUOXunc5ui0Ucg)or on the [Crowdin project ](https://crowdin.com/project/prestashop-official)with your request.
Proofreaders are always needed, so don't hesitate to contact us if you're interested! 🙌
---
# 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.prestashop-project.org/translating-prestashop/translating-prestashop-software-basics/translating-on-crowdin/proofreading-all-you-need-to-know.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.
