From 520aacc246ce01ae71c1ffeaf289967780f30d21 Mon Sep 17 00:00:00 2001
From: David Martinez <47610359+dvdmrtnz@users.noreply.github.com>
Date: Sun, 10 Apr 2022 17:35:22 +0200
Subject: [PATCH] [docs] Fix folder name

Signed-off-by: David Martinez <47610359+dvdmrtnz@users.noreply.github.com>
---
 docs/TRANSLATIONS.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/TRANSLATIONS.md b/docs/TRANSLATIONS.md
index 6920d159fa..7b2c8ce051 100644
--- a/docs/TRANSLATIONS.md
+++ b/docs/TRANSLATIONS.md
@@ -7,7 +7,7 @@ Adding and updating translations is easy!
 
 Please prepend `[strings]` to your commit message and add [Developers Certificate of Origin](CONTRIBUTING.md#legal-requirements) to it.
 
-Then run a `utils/unix/generate_localizations.sh` script and add the changes as a separate `[strings] Regenerated` commit.
+Then run a `tools/unix/generate_localizations.sh` script and add the changes as a separate `[strings] Regenerated` commit.
 But if you can't run it - don't worry, its not mandatory!
 
 ## Translation files
@@ -60,7 +60,7 @@ OM uses a custom version of the [Twine](https://github.com/organicmaps/twine)
 tool (resides in `tools/twine/` submodule) to generate platfrom-native (Android, iOS)
 localization files from a single translation file.
 
-The `utils/unix/generate_localizations.sh` script launches this conversion
+The `tools/unix/generate_localizations.sh` script launches this conversion
 (and installs Twine beforehand if necessary).
 
 Search keywords translation files use a custom format described in the beginning of `data/categories.txt`.