> For the complete documentation index, see [llms.txt](https://docs.babelshark.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.babelshark.net/proofreader/checking-translations.md).

# Checking translations

As a Proofreader, you will have to check the translated strings thoroughly and in the context of the project.&#x20;

Overtime, various projects and products adapt their own terminology, which Proofreader may understand as words of different meaning.&#x20;

BabelShark has several functions to help Proofreaders **understand** what they're translating, into what context.&#x20;

### Context hints

On the bottom left-side of the string, there is a context hint that helps better understand the context of your translation.&#x20;

<figure><img src="/files/zHnrFjyS6GrUmht1TbHZ" alt=""><figcaption></figcaption></figure>

If there's no context hint:&#x20;

1. Copy the **String ID** (You can use this for searching strings as well)<br>

   <figure><img src="/files/VRnnPPUmC0dSvZ0D0031" alt=""><figcaption></figcaption></figure>
2. Paste it to your Project Manager (The person which invited you to project, or any relevant team member)
3. Wait for Project Manager to provide context on your string

### Drawer menus

![](/files/aAdLzf46LAQ6STeDiYdm)

Every string includes a ![](/files/KwAKNsZwpo883nO9noTi)**Drawer arrow icon** on the right-side, once clicked, it provides more information on the string:&#x20;

* When it was added
* Last use of the string
* Original language
* URL of the page (Where it's located)
* Original string

Overtime, more helpful functions will be added for Proofreaders to better understand concept of every translation string.&#x20;

To finalize your knowledgebase of how to work with Babelshark as Proofreader, continue reading [Translation types](/proofreader/translation-types.md)
