diff --git a/packages/noco-docs/content/en/engineering/translation.md b/packages/noco-docs/content/en/engineering/translation.md
index 53fc1d0af1..9f39dffaac 100644
--- a/packages/noco-docs/content/en/engineering/translation.md
+++ b/packages/noco-docs/content/en/engineering/translation.md
@@ -12,26 +12,32 @@ NocoDB supports tool localization & relies on Google translation for first versi
> [Master i18n spreadsheet](https://docs.google.com/spreadsheets/d/1kGp92yLwhs1l7lwwgeor3oN1dFl7JZWuQOa4WSeZ0TE/edit#gid=2076107172)
> [Google language code](https://developers.google.com/admin-sdk/directory/v1/languages)
-## 1. Requesting support for a `new language`
+## For Application User
+
+### 1. Changing `existing language` translation text
+
+Your help in identifying language translation anomalies & helping it fix helps in big way building/scaling NocoDB to next level. Please follow below simple procedure to request corrections to existing translation errors.
- Make a copy of [Google spreadsheet](https://docs.google.com/spreadsheets/d/1kGp92yLwhs1l7lwwgeor3oN1dFl7JZWuQOa4WSeZ0TE/edit#gid=2076107172)
- Find your language code [here](https://developers.google.com/admin-sdk/directory/v1/languages)
-- Replace cell $AB$1 (rightmost, containing text `en`) with language code obtained above.
-- Google will generate first version translation in column AB. Review. Make changes as you find appropriate for various items listed. Origin text in ENGLISH can be found in `Column B` of master spreadsheet.
+- Go to the column containing your language code derived above. Make changes as you find appropriate for various items listed. Origin text in ENGLISH can be found in `Column B` of master spreadsheet.
- Download spreadsheet as .csv (`File > Download > Comma-seperated values (.csv)`).
- Create new [issue](https://github.com/nocodb/nocodb/issues/new?assignees=dstala&labels=i18n+translation&template=i18n-translation-request.md&title=%5Bi18n%5D+Language+support+extension-+%3Clanguage+code%3E) request with a link to your spreadsheet from Step-1 (for us to verify & update master spreadsheet).
-## 2. Making contributions to `existing language` translations
+### 2. Requesting support for a `new language`
+
+Your native language not in list, we will be glad to support with your help! Please follow below steps
- Make a copy of [Google spreadsheet](https://docs.google.com/spreadsheets/d/1kGp92yLwhs1l7lwwgeor3oN1dFl7JZWuQOa4WSeZ0TE/edit#gid=2076107172)
- Find your language code [here](https://developers.google.com/admin-sdk/directory/v1/languages)
-- Go to the column containing your language code derived above. Make changes as you find appropriate for various items listed. Origin text in ENGLISH can be found in `Column B` of master spreadsheet.
+- Replace cell $AB$1 (rightmost, containing text `en`) with language code obtained above.
+- Google will generate first version translation in column AB. Review. Make changes as you find appropriate for various items listed. Origin text in ENGLISH can be found in `Column B` of master spreadsheet.
- Download spreadsheet as .csv (`File > Download > Comma-seperated values (.csv)`).
@@ -39,9 +45,11 @@ NocoDB supports tool localization & relies on Google translation for first versi
---
+## For NocoDB Moderators
+
> **_This is exclusive to NocoDB team members/ moderators only_**
-## 3. Adding/ updating KEY.STRING
+### 1. Adding/ updating KEY.STRING
- Open master [Spreadsheet](https://docs.google.com/spreadsheets/d/1kGp92yLwhs1l7lwwgeor3oN1dFl7JZWuQOa4WSeZ0TE/edit#gid=2076107172)
- For the string/ text under consideration, look-up in existing sheet if it exists already
@@ -51,7 +59,7 @@ NocoDB supports tool localization & relies on Google translation for first versi
- Use noco-i18n-from-cli to generate new language JSON file
- Copy respective i18n/\*.json files to `nocodb/packages/nc-gui/lang`
-## 4. String KEY Categories
+### 2. String KEY Categories
- **General**: simple & common tokens (save, cancel, submit, open, close, home, and such)
- **Objects**: objects from NocoDB POV (project, table, field, column, view, page, and such)