From baf8183bb74830d8498bca65c57d1f2410094b9d Mon Sep 17 00:00:00 2001 From: Dan J Miller Date: Mon, 2 Dec 2024 10:57:10 -0330 Subject: [PATCH] Update docs/translating-guide.md Co-authored-by: Mark Stacey --- docs/translating-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/translating-guide.md b/docs/translating-guide.md index bad94886fc19..8062e94ff123 100644 --- a/docs/translating-guide.md +++ b/docs/translating-guide.md @@ -10,7 +10,7 @@ The MetaMask browser extension supports new translations added in the form of ne - Inside that folder there should be a `messages.json`. - An easy way to start your translation is to first **make a copy** of `app/_locales/en/messages.json` (the English translation), and then **translate the `message` key** for each in-app message. - **The `description` key** is just to add context for what the translation is about, it **does not need to be translated**. -- Add the language to the [locales index](https://github.com/MetaMask/metamask-extension/blob/s/app/_locales/index.json) `app/_locales/index.json` +- Add the language to the [locales index](https://github.com/MetaMask/metamask-extension/blob/main/app/_locales/index.json) `app/_locales/index.json` That's it! When MetaMask is loaded on a computer with that language set as the system language, they will see your translation instead of the default one.