apps/web/public/static/locales/zh-TW/common.json (1)

1843-1844: 延伸字串同樣需保持一致用詞

這兩條權限說明仍使用「用戶端」。為保持一致，請同步改為「客戶端」。

apps/web/public/static/locales/vi/common.json (1)

1843-1845: Minor typography: missing period at sentence end

Lines 1843–1845 are full sentences but lack a terminal full-stop “.”.
Adding it keeps style identical to neighbouring admin-only notices (see Line 183-184 etc.).

-"Chỉ quản trị viên hoặc chủ sở hữu của tổ chức mới có thể quản lý cài đặt đồng bộ hóa thư mục"
+"Chỉ quản trị viên hoặc chủ sở hữu của tổ chức mới có thể quản lý cài đặt đồng bộ hóa thư mục."

(Apply same to Line 1845).

apps/web/public/static/locales/ru/common.json (1)

874-878: Consider the correct case for the direct-object form of “OAuth-client”.

In Russian UI strings the object after “создать” normally takes the accusative case.
"create_oauth_client": "Создать OAuth-клиент" should likely be
"Создать OAuth-клиента" to be grammatically correct.

-"create_oauth_client": "Создать OAuth-клиент",
+"create_oauth_client": "Создать OAuth-клиента",

apps/web/public/static/locales/uk/common.json (3)

874-877: Terminology consistency check for OAuth-related strings

Looks good overall, but double-check that the existing UI consistently uses “OAuth клієнт” (singular) vs “OAuth клієнти” (plural).
In English we often mix “OAuth app / client”, so make sure the same Ukrainian term is used everywhere to avoid UI mismatches.

No action required if the rest of the locale already follows this wording.

---

3311-3315: PBAC resource additions: keep alphabetical grouping

The new pbac_resource_attributes + description keys are appended to the block but break the existing alphabetical order of resources/descriptions set earlier in the file (event_type, organization, …).
Consider moving the four lines into the correct sorted position to keep future diffs minimal.

No functional impact – purely maintainability.

---

3319-3324: Updated “manage_*” descriptions – spelling check

Minor typo: “подій” vs “подій у”. Line 3324 currently reads
"Усі дії з типами подій у командах організації"
where “подій” already conveys genitive; “у” is OK but occasionally omitted elsewhere. Ensure wording is uniform across all pbac_desc_manage_* entries (roles, teams, event types) to avoid translator noise.

If the English originals differ, ignore.

apps/web/public/static/locales/ca/common.json (1)

3311-3316: Minor typo: atributs not attributs

atributs is already spelled correctly in the value strings, but the resource key also carries that typo (pbac_resource_attributes).
If this was copied from the English locale it is fine, but double-check—renaming later is painful.

apps/web/public/static/locales/zh-TW/common.json (1)

3311-3316: 新增 PBAC 描述請檢查標點一致性

1. Line 3313 與 3314 句尾缺少句號，而同區段其他描述多使用句號收尾。
2. Line 3315 pbac_desc_manage_roles 應與前面敘述格式一致，可改為「管理組織（團隊）中角色的所有操作。」

屬於細節但會影響文件閱讀體驗。

apps/web/public/static/locales/pl/common.json (1)

1843-1844: Keep tone consistent in admin-only messages

Strings only_admin_can_manage_directory_sync / only_admin_can_manage_oauth_clients start with “Tylko administrator lub właściciel…”.
Every other “admin-only” string in this file starts with “Tylko administrator …”.
For consistency either drop “lub właściciel” everywhere or keep it everywhere. Pick one and run i18n lint afterwards.

apps/web/public/static/locales/hu/common.json (2)

1843-1844: Consistency with existing “only_admin_can_…” strings

The newly added keys follow the existing pattern but use singular “admin” while some previous entries use plural (“admins”).
Consider renaming to only_admins_can_manage_* for consistency with siblings (only_admins_can_manage_sso_org, etc.).

---

3311-3316: Keep PBAC help-texts alphabetically grouped

New PBAC resource/description pairs for “attributes” were appended at the bottom of the block.
For easier diffing & merge-conflict avoidance place them alphabetically with the other pbac_* entries.
This repo has been bitten by duplicated keys in the past.

apps/web/public/static/locales/pt/common.json (2)

874-877: Consider adding the definite article and keeping the voice consistent

Most description strings in this file start with an imperative verb followed by the article “os” (e.g. “Gerencie os webhooks…”, “Configure as definições…”).
For consistency, prefer:

- "oauth_clients_description": "Gerencie clientes OAuth para sua organização",
+ "oauth_clients_description": "Gerencie os clientes OAuth da sua organização",

Minor, but it keeps wording uniform across the glossary.

---

1843-1844: Capitalisation & voice inconsistent with neighbouring keys

Nearly every permission-warning string starts with a capital letter and the infinitive “Gerenciar/Administrar…”.
These two new entries start with a lowercase “gerenciar”.

- "only_admin_can_manage_directory_sync": "Apenas o administrador ou proprietário da organização pode gerenciar as configurações de sincronização de diretório",
- "only_admin_can_manage_oauth_clients": "Apenas o administrador ou proprietário da organização pode gerenciar clientes OAuth",
+ "only_admin_can_manage_directory_sync": "Apenas o administrador ou o proprietário da organização pode gerenciar as configurações de sincronização de diretório",
+ "only_admin_can_manage_oauth_clients": "Apenas o administrador ou o proprietário da organização pode gerenciar os clientes OAuth",

This keeps capitalisation and the article “o” in line with the existing sentence style.

apps/web/public/static/locales/cs/common.json (1)

874-878: Ensure punctuation style consistency

Most Czech strings in this file end without a trailing period, but several neighbouring entries (e.g. "create_new_team_description") do use one.
For consistency across the locale consider either removing the full stop in

"create_oauth_client_description": "Vytvořte nového OAuth klienta pro integraci s třetími stranami"

or systematically adding a period to the other short-description keys that currently lack it.
(This is purely cosmetic; nothing is functionally wrong.)

apps/web/public/static/locales/de/common.json (1)

3311-3316: PBAC attribute entries added without placeholder/grammar issues

– Keys are unique.
– German wording (“Organisationsattribute”) matches the resource context.
– No placeholder tokens to validate.

Consider keeping these PBAC description blocks alphabetically grouped like the existing ones for easier maintenance, but that’s optional.

apps/web/public/static/locales/sk-SK/common.json (2)

874-877: Check consistency of term “OAuth klient” (singular) vs “OAuth klienti” (plural).

In the Slovak strings you mix:

• "oauth_clients" → OAuth klienti (plural, correct)
• "create_oauth_client" → Vytvoriť OAuth klienta (singular, genitive) – fine
• "create_oauth_client_description" → … klienta (singular) – also fine

However, "oauth_clients_description" reads Spravujte OAuth klientov (genitive plural). The heading is plural nominative (klienti), while the description uses genitive plural (klientov). That’s grammatically correct, but double-check the UI: if the heading appears right above the description it may read odd ( OAuth klienti – Spravujte OAuth klientov ). Consider using nominative plural in the description (Spravujte OAuth klienti vo vašej organizácii) or rewriting the heading ( Správa OAuth klientov ) so both lines do not repeat the noun back-to-back.

---

1843-1844: Minor wording alignment for admin-only notices.

Both keys are admin-gate messages; first ends with nastavenia synchronizácie adresára, second with OAuth klientov. For parallelism consider:

"Iba administrátor alebo vlastník organizácie môže spravovať synchronizáciu adresára"
"Iba administrátor alebo vlastník organizácie môže spravovať OAuth klientov"

This removes the extra word nastavenia so the two strings scan identically.

apps/web/public/static/locales/pt-BR/common.json (1)

1843-1844: Use one term for “owner” across the file

Earlier keys (e.g. only_admin_can_manage_sso_org, Line 1841) use “dono da organização”, whereas the two new strings adopt “proprietário da organização”. Mixing “dono” and “proprietário” might confuse translators and users.

- "Apenas o administrador ou proprietário da organização pode gerenciar ..."
+ "Apenas o administrador ou dono da organização pode gerenciar ..."

apps/web/public/static/locales/bg/common.json (1)

874-876: Consider keeping new OAuth-related keys grouped with existing OAuth strings for maintainability

These keys are inserted ~200 lines above the other OAuth strings that start at Line 878.
Moving them next to the existing block (or vice-versa) keeps the file logically grouped and eases future diff reviews.

apps/web/public/static/locales/sr/common.json (2)

874-878: Validate new OAuth-related keys & keep alphabetical ordering

The newly added keys (oauth_clients … create_oauth_client_description) break the existing alphabetic ordering of the JSON (they appear after nameless_team).
While order does not affect runtime, keeping the file sorted greatly reduces merge-conflicts in the enormous common.json.

-  "nameless_team": "Tim bez imena",
-  "oauth_clients": "OAuth klijenti",
-  ...
+  "nameless_team": "Tim bez imena",
+  // --- keep alphabetic ordering: place below “offer_seats” block ---

Consider moving the block accordingly before merging.
No functional issues with the Serbian strings themselves.

---

1843-1845: Plural consistency for admin-only strings

only_admin_can_manage_directory_sync and only_admin_can_manage_oauth_clients start with “Samo administrator ili vlasnik … može” (singular) but end with “mogu” (plural).
Recommend aligning the verb with the subject for readability:

- "only_admin_can_manage_directory_sync": "Samo administrator ili vlasnik organizacije može upravljati podešavanjima sinhronizacije direktorijuma",
+ "only_admin_can_manage_directory_sync": "Samo administrator ili vlasnik organizacije može da upravlja podešavanjima sinhronizacije direktorijuma",

- "only_admin_can_manage_oauth_clients": "Samo administrator ili vlasnik organizacije može upravljati OAuth klijentima"
+ "only_admin_can_manage_oauth_clients": "Samo administrator ili vlasnik organizacije može da upravlja OAuth klijentima"

apps/web/public/static/locales/ar/common.json (1)

3311-3316: PBAC attribute keys added – just verify uniqueness
Keys for the new PBAC resource (pbac_resource_attributes) and its CRUD descriptions are correct. Run a quick duplicate-key check on the whole JSON file to ensure these identifiers don’t collide with earlier ones; large locale files sometimes accumulate silent duplicates.

apps/web/public/static/locales/no/common.json (2)

874-877: Unify the Norwegian term for OAuth client

Earlier in the same file (line 240 → webhook_update_form_description) the term is written as “OAuthClient” (camel-cased, no hyphen), whereas the four new keys use “OAuth-klient”.
For consistency and to avoid confusion in the UI, stick to one variant throughout the locale file (ideally the hyphenated “OAuth-klient”, which reads better in Norwegian).

---

3311-3315: Minor formatting – last item can drop the trailing comma

Line 3315 ends with a comma while the following line already starts a new top-level key. JSON allows the extra comma in many runtimes, but pruning it prevents accidental linting errors in stricter parsers.

-  "pbac_desc_create_organization_attributes": "Opprett organisasjonsegenskaper",
+  "pbac_desc_create_organization_attributes": "Opprett organisasjonsegenskaper"

apps/web/public/static/locales/ko/common.json (1)

1842-1845: Minor wording inconsistency

Lines 1842-1845 mix “관리자 또는 소유자” with “관리자만”.
For perfect consistency with the neighbouring permission strings (e.g. 1838-1841) consider aligning the wording, e.g.

- "조직의 관리자 또는 소유자만 디렉토리 동기화 설정을 관리할 수 있습니다"
+ "조직의 관리자(소유자 포함)만 디렉토리 동기화 설정을 관리할 수 있습니다"

apps/web/public/static/locales/he/common.json (1)

1843-1845: Missing plural-gender neutrality

The two strings use “מנהל או בעלים” in singular masculine form.
Other Hebrew translations in the file avoid gendered phrasing by using neutral participles (e.g. “מנהל/ת מערכת”).
Consider aligning:

- "רק מנהל או בעלים של הארגון..."
+ "רק מנהל/ת מערכת או בעל/ת הארגון..."

apps/web/public/static/locales/es-419/common.json (1)

1843-1844: Minor consistency issue in admin-only strings
Line 1843 already says “Solo el administrador o propietario…”. At 1844 you add essentially the same pattern. Consider moving both messages into a single placeholder‐based template to avoid copy-paste drift when wording changes in the future.

apps/web/public/static/locales/es/common.json (1)

874-878: Polish OAuth-related strings for consistency and grammar

1. Use an article before “cliente” to match Spanish idiom (“Crear un cliente OAuth”).
2. Capitalise the first word in the description for consistency with neighbouring keys (“Gestiona los…” → “Gestiona los…”)
3. Consider adding “los” to keep parallelism with other descriptions (“Gestiona los clientes OAuth…”).

-"oauth_clients": "Clientes OAuth",
-"oauth_clients_description": "Gestiona los clientes OAuth para tu organización",
-"create_oauth_client": "Crear cliente OAuth",
-"create_oauth_client_description": "Crea un nuevo cliente OAuth para integraciones de terceros",
+"oauth_clients": "Clientes OAuth",
+"oauth_clients_description": "Gestiona los clientes OAuth de tu organización",
+"create_oauth_client": "Crear un cliente OAuth",
+"create_oauth_client_description": "Crea un nuevo cliente OAuth para integraciones de terceros",

apps/web/public/static/locales/km/common.json (2)

874-877: Confirm wording for “OAuth client” — current Khmer phrasing sounds like a “machine”
The term ​«ម៉ាស៊ីនភ្ញៀវ» literally means “client machine”. In most Khmer UIs we usually keep OAuth client untranslated or borrow the English word “client” (e.g. «OAuth Client» or «Client OAuth») instead of “ម៉ាស៊ីនភ្ញៀវ”.
Please double-check with your localisation guide to make sure the term is recognisable to end-users.

---

1843-1844: Minor consistency nit – reuse existing wording for “organization”
In earlier strings the project consistently uses «អង្គការ» for “organization”. Here the translation for
only_admin_can_manage_directory_sync and only_admin_can_manage_oauth_clients introduces the variant «អង្គភាព».
Consider standardising on one term (preferably the one already used elsewhere) to avoid confusion.

apps/web/public/static/locales/it/common.json (2)

874-877: Add the missing indefinite article in the new “OAuth client” strings
In Italian the action labels generally include an article (“Crea un …”) to read naturally, e.g. earlier keys such as create_webhook use “Crea un Webhook”.
Consider:

- "create_oauth_client": "Crea client OAuth",
- "create_oauth_client_description": "Crea un nuovo client OAuth per integrazioni di terze parti"
+ "create_oauth_client": "Crea un client OAuth",
+ "create_oauth_client_description": "Crea un nuovo client OAuth per integrazioni di terze parti"

---

3312-3316: Minor consistency touch-up: keep the noun order aligned with similar PBAC keys
Most existing PBAC descriptions start with the verb and keep the resource near the end, e.g. “Crea attributi dell’organizzazione”. For perfect alignment you may want to mirror the wording used for other resources (eventi, ruoli, …). Current text is already correct, so this is only stylistic.

apps/web/public/static/locales/fr/common.json (2)

1842-1843: Minor wording nit-pick

"Seul l'administrateur ou le propriétaire de l'organisation peut gérer …" reads well, but every other permission string in this file begins with “Seul l’administrateur* de l’organisation** ou son propriétaire …”* (note the extra “de l’organisation” after administrateur).

For perfect consistency you could tweak:

-"Seul l'administrateur ou le propriétaire de l'organisation peut gérer les paramètres de synchronisation d'annuaire",
-"Seul l'administrateur ou le propriétaire de l'organisation peut gérer les clients OAuth",
+"Seul l'administrateur de l'organisation ou son propriétaire peut gérer les paramètres de synchronisation d'annuaire",
+"Seul l'administrateur de l'organisation ou son propriétaire peut gérer les clients OAuth",

---

3312-3316: Uniform wording for attribute-related PBAC descriptions

Three existing PBAC descriptions use “de l'organisation” (view / update / delete) while the new one for create reads “d'organisation”.
Recommend unifying the article for searchability and visual consistency:

-"pbac_desc_create_organization_attributes": "Créer des attributs d'organisation",
+"pbac_desc_create_organization_attributes": "Créer des attributs de l'organisation",

apps/web/public/static/locales/eu/common.json (1)

874-878: Consistent naming, but singular/plural wording could be tighter

oauth_clients → “OAuth bezeroak” (plural) and create_oauth_client → “OAuth bezeroa” (singular) are correct, yet oauth_clients_description still uses the plural (“bezeroak”).
To keep the glossaries aligned with most other locales you may want to switch to the singular in the description, e.g.

-"Kudeatu zure erakundearen OAuth bezeroak"
+"Zure erakundearen OAuth bezeroa kudeatu"

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

Learnt from: bandhan-majumder
PR: calcom/cal.com#22359
File: packages/lib/server/locales/en/common.json:1336-1339
Timestamp: 2025-07-14T16:31:45.233Z
Learning: When making localization changes for new features, it's often safer to add new strings rather than modify existing ones to avoid breaking existing functionality that depends on the original strings. This approach allows for feature-specific customization while maintaining backward compatibility.

Learnt from: bandhan-majumder
PR: calcom/cal.com#22359
File: packages/lib/server/locales/en/common.json:1336-1339
Timestamp: 2025-07-14T16:31:45.233Z
Learning: When making localization changes for new features, it's often safer to add new strings rather than modify existing ones to avoid breaking existing functionality that depends on the original strings. This approach allows for feature-specific customization while maintaining backward compatibility.

Learnt from: CR
PR: calcom/cal.com#0
File: .cursor/rules/review.mdc:0-0
Timestamp: 2025-07-28T11:50:23.946Z
Learning: Applies to docs/api-reference/v2/openapi.json : When docs changes are made in `/docs/api-reference/v2/openapi.json`, ensure 'summary' fields are short, concise, do not end with a period, and are written in proper American English

apps/web/public/static/locales/bn/common.json (1)

1843-1845: Nit: finish sentences with the same punctuation as neighbours

Most neighbouring strings in this block end with a full-stop (“।”), but these two lines do not. Add the period for visual consistency.

-  "only_admin_can_manage_directory_sync": "শুধুমাত্র সংগঠনের অ্যাডমিন বা মালিক ডিরেক্টরি সিঙ্ক সেটিংস পরিচালনা করতে পারেন",
-  "only_admin_can_manage_oauth_clients": "শুধুমাত্র সংগঠনের অ্যাডমিন বা মালিক OAuth ক্লায়েন্ট পরিচালনা করতে পারেন",
+  "only_admin_can_manage_directory_sync": "শুধুমাত্র সংগঠনের অ্যাডমিন বা মালিক ডিরেক্টরি সিঙ্ক সেটিংস পরিচালনা করতে পারেন।",
+  "only_admin_can_manage_oauth_clients": "শুধুমাত্র সংগঠনের অ্যাডমিন বা মালিক OAuth ক্লায়েন্ট পরিচালনা করতে পারেন।",

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

Learnt from: bandhan-majumder
PR: calcom/cal.com#22359
File: packages/lib/server/locales/en/common.json:1336-1339
Timestamp: 2025-07-14T16:31:45.233Z
Learning: When making localization changes for new features, it's often safer to add new strings rather than modify existing ones to avoid breaking existing functionality that depends on the original strings. This approach allows for feature-specific customization while maintaining backward compatibility.

Learnt from: bandhan-majumder
PR: calcom/cal.com#22359
File: packages/lib/server/locales/en/common.json:1336-1339
Timestamp: 2025-07-14T16:31:45.233Z
Learning: When making localization changes for new features, it's often safer to add new strings rather than modify existing ones to avoid breaking existing functionality that depends on the original strings. This approach allows for feature-specific customization while maintaining backward compatibility.

apps/web/public/static/locales/he/common.json (2)

3292-3292: PBAC additions: verify EN parity and UI wiring

New PBAC resource and description keys look consistent. Ensure English locale contains matching keys and that permission matrices map to them.

#!/bin/bash
# Locate English common.json
EN=$(fd --absolute-path common.json . | rg '/locales/en/common.json$' | head -n1)
echo "Scanning: $EN"

# Verify presence of new PBAC keys in EN
rg -n '"pbac_resource_workflow"| "pbac_resource_attributes"| "pbac_desc_(create|view|update|delete|manage)_(workflows|event_types|teams|bookings)|"pbac_desc_(view|update|delete|create)_organization_attributes' "$EN" \
  || echo "One or more PBAC keys missing in EN/common.json"

Also applies to: 3315-3336, 3341-3341, 3356-3356

---

3473-3474: “stats” duplication previously flagged — appears resolved now

Earlier duplicate “stats” was reported; in this version only one “stats” key exists (Line 3473). Good fix.

apps/web/public/static/locales/zh-TW/common.json (1)

875-878: 統一為「OAuth 客戶端」：已修正且一致

此前評論提到「用戶端/客戶端」不一致，此處已統一為「客戶端」。讚。

建議快速檢查本檔其餘新/舊字串是否仍殘留「用戶端」以保持一致：

#!/bin/bash
rg -n --glob '!node_modules' $'apps/web/public/static/locales/zh-TW/common.json' -e '用戶端|客戶端' -A 1

apps/web/public/static/locales/ja/common.json (1)

123-123: Apply prior JP style tweak for natural phrasing

Past suggestion still applies: drop the extra の for consistency with nearby strings.

-  "round_robin_host_unavailable_for_booking": "ラウンドロビンのホストは予約できません。",
+  "round_robin_host_unavailable_for_booking": "ラウンドロビンホストは予約できません。",

To ensure the old plural key isn’t used anywhere:

#!/bin/bash
rg -n --hidden --glob '!.git' 'round_robin_hosts_unavailable_for_booking|roundRobinHostsUnavailableForBooking'

apps/web/public/static/locales/ca/common.json (1)

3383-3383: Use imperative for “add_group” to match dominant pattern.

Most “add_*” labels use imperative (“Afegeix …”). Align this one for consistency.

-  "add_group": "Afegir grup",
+  "add_group": "Afegeix un grup",

apps/web/public/static/locales/sr/common.json (3)

123-123: Round Robin terminology + “zakazivanje” vs “rezervacija” consistency

Mixed “Round Robin” vs localized form and “zakazivanje” vs “rezervacija.” Align with adjacent strings (Lines 121–122 use “rezervaciju”). Suggested localized phrasing:

-  "round_robin_host_unavailable_for_booking": "Round Robin domaćin nije dostupan za zakazivanje.",
+  "round_robin_host_unavailable_for_booking": "Domaćin za kružno dodeljivanje nije dostupan za rezervaciju."

---

3341-3341: Harmonize PBAC scope phrasing for teams (matches prior feedback)

Other entries use “u timovima organizacije” (e.g., roles and event types). Align “manage teams” to the same scope phrasing:

-  "pbac_desc_manage_teams": "Sve akcije nad timovima u organizaciji",
+  "pbac_desc_manage_teams": "Sve akcije nad timovima u timovima organizacije"

If the broader “u organizaciji” scope was intentional, please confirm and keep as-is.

---

3366-3366: RR groups balancing: apply terminology decision consistently

Make RR term consistent across file (English “Round Robin” vs “kružno dodeljivanje”). If localizing, suggest:

-  "rr_load_balancing_disabled_with_groups": "Balansiranje opterećenja nije dostupno sa Round Robin grupama",
+  "rr_load_balancing_disabled_with_groups": "Balansiranje opterećenja nije dostupno sa kružnim dodeljivanjem grupa"

Run a quick sweep to unify the chosen term across all RR strings.

apps/web/public/static/locales/no/common.json (2)

123-123: Use Norwegian “bestilling” for consistency (past request not reflected).

Switch “booking” → “bestilling” to align with Norwegian style used elsewhere and prior guidance.

-  "round_robin_host_unavailable_for_booking": "Round Robin-vert er ikke tilgjengelig for booking.",
+  "round_robin_host_unavailable_for_booking": "Round Robin-vert er ikke tilgjengelig for bestilling.",

Optional: verify no stale references to the old plural key remain outside locales:

#!/bin/bash
set -euo pipefail
echo "Searching for old key in source (excluding locales)..."
rg -n -S "round_robin_hosts_unavailable_for_booking" --glob '!apps/web/public/static/locales/**' || true

---

3324-3324: Align PBAC phrasing: “organisasjonens team” and “hendelsestyper” (as previously requested).

Consistently use “hendelsestyper” and “på tvers av organisasjonens team”.

-  "pbac_desc_manage_roles": "Alle handlinger på roller på tvers av organisasjonsteam",
+  "pbac_desc_manage_roles": "Alle handlinger på roller på tvers av organisasjonens team",

-  "pbac_desc_manage_event_types": "Alle handlinger på arrangementstyper på tvers av organisasjonsteam",
+  "pbac_desc_manage_event_types": "Alle handlinger på hendelsestyper på tvers av organisasjonens team",

-  "pbac_desc_manage_teams": "Alle handlinger på team på tvers av organisasjonsteam",
+  "pbac_desc_manage_teams": "Alle handlinger på team på tvers av organisasjonens team",

-  "pbac_desc_manage_bookings": "Alle handlinger på bookinger på tvers av organisasjonsteam",
+  "pbac_desc_manage_bookings": "Alle handlinger på bookinger på tvers av organisasjonens team",

Also applies to: 3333-3333, 3342-3342, 3356-3356

apps/web/public/static/locales/ru/common.json (1)

123-123: Unify “организатор” and replace “Round Robin” with “по очереди”

Keep terminology consistent with the rest of the RU locale.

-  "round_robin_host_unavailable_for_booking": "Хост Round Robin недоступен для бронирования.",
+  "round_robin_host_unavailable_for_booking": "Организатор по очереди недоступен для бронирования."

apps/web/public/static/locales/fi/common.json (1)

123-123: Hyphenation: prefer “Round-robin” without spaces around the hyphen

Use “Round-robin-isäntä” for proper Finnish hyphenation and consistency with prior guidance.

-  "round_robin_host_unavailable_for_booking": "Round Robin -isäntä ei ole varattavissa.",
+  "round_robin_host_unavailable_for_booking": "Round-robin-isäntä ei ole varattavissa.",

apps/web/public/static/locales/vi/common.json (1)

875-878: Unify terminology: use “OAuth Client(s)” consistently across vi locale

These four new entries currently use “Ứng dụng OAuth” while other strings in this file already use “OAuth Client” (e.g., admin_oAuth_description, oAuth_client_* forms). Align for consistency.

-  "oauth_clients": "Ứng dụng OAuth",
-  "oauth_clients_description": "Quản lý ứng dụng OAuth cho tổ chức của bạn",
-  "create_oauth_client": "Tạo ứng dụng OAuth",
-  "create_oauth_client_description": "Tạo một ứng dụng OAuth mới cho tích hợp bên thứ ba",
+  "oauth_clients": "OAuth Clients",
+  "oauth_clients_description": "Quản lý OAuth Clients cho tổ chức của bạn",
+  "create_oauth_client": "Tạo OAuth Client",
+  "create_oauth_client_description": "Tạo OAuth Client mới cho tích hợp bên thứ ba",

Also update nearby strings (outside this hunk) for consistency:

• Line 879: "oauth_client_deletion_message": change to “Đã xóa thành công OAuth Client”
• Line 240: "webhook_update_form_description": add space → “OAuth Client”

Would you like me to open a follow-up to sweep all vi/common.json keys for consistent “OAuth Client(s)” usage?

apps/web/public/static/locales/ko/common.json (2)

875-878: Use “타사” (preferred) and keep style consistent with surrounding descriptions

Replace “서드파티” with the more standard “타사”. Optional: if you prefer sentence-style, consider “…를 생성합니다” to match other descriptions nearby.

-  "create_oauth_client_description": "서드파티 통합을 위한 새 OAuth 클라이언트 생성",
+  "create_oauth_client_description": "타사 통합을 위한 새 OAuth 클라이언트 생성",

---

123-123: Repo-wide verification of new/renamed keys

This was already flagged in earlier review; ensure the newly added keys exist across all locales and the old key round_robin_hosts_unavailable_for_booking is not referenced anywhere.

apps/web/public/static/locales/pl/common.json (1)

3473-3474: Duplicate key: stats will overwrite earlier value

Key stats already exists earlier in this file; redefining it will shadow the first on load. Rename this new one to avoid collision, e.g., booking_stats.

Apply this minimal fix:

-  "stats": "Statystyki",
+  "booking_stats": "Statystyki",

Detect duplicate keys programmatically:

#!/bin/bash
python - << 'PY'
import json, sys, collections
path = "apps/web/public/static/locales/pl/common.json"
pairs = []
with open(path, 'r', encoding='utf-8') as f:
    # Load raw text to capture duplicates
    text = f.read()
# Simple duplicate detector by scanning lines
from collections import defaultdict
counts = defaultdict(int)
for line in text.splitlines():
    line=line.strip()
    if line.startswith('"'):
        key=line.split('"',2)[1]
        counts[key]+=1
dups=[k for k,v in counts.items() if v>1]
print("DUPLICATE_KEYS:", ", ".join(sorted(dups)) if dups else "NONE")
PY

apps/web/public/static/locales/da/common.json (1)

123-123: Danish phrasing tweak for natural tone

Prefer “til booking” over “for booking”.

-  "round_robin_host_unavailable_for_booking": "Round Robin-værten er ikke tilgængelig for booking.",
+  "round_robin_host_unavailable_for_booking": "Round Robin-værten er ikke tilgængelig til booking.",

apps/web/public/static/locales/de/common.json (1)

123-123: Standardize “Round‑Robin” and prefer “Veranstalter”

Align with project terminology and hyphenation.

-  "round_robin_host_unavailable_for_booking": "Round Robin-Gastgeber ist für Buchungen nicht verfügbar.",
+  "round_robin_host_unavailable_for_booking": "Round-Robin-Veranstalter ist für Buchungen nicht verfügbar.",

apps/web/public/static/locales/pt/common.json (1)

123-123: PT-PT consistency: use “reserva” and preposition “de”

Aligns with earlier PT-PT usage and avoids BR-PT “agendamento”.

-  "round_robin_host_unavailable_for_booking": "O anfitrião do Round Robin não está disponível para agendamento.",
+  "round_robin_host_unavailable_for_booking": "O anfitrião de Round Robin não está disponível para reserva.",

apps/web/public/static/locales/it/common.json (2)

123-123: Normalize “host Round Robin” to established terminology

Use “organizzatore round robin” to match existing usage and casing in this file.

-  "round_robin_host_unavailable_for_booking": "L'host Round Robin non è disponibile per la prenotazione.",
+  "round_robin_host_unavailable_for_booking": "L'organizzatore round robin non è disponibile per la prenotazione.",

---

3366-3367: Uniformare “Round Robin” → “round robin”

Capitalize consistently as lowercase “round robin” throughout this file.

-  "rr_load_balancing_disabled_with_groups": "Il bilanciamento del carico non è disponibile con i gruppi Round Robin",
+  "rr_load_balancing_disabled_with_groups": "Il bilanciamento del carico non è disponibile con i gruppi round robin",

apps/web/public/static/locales/fr/common.json (1)

123-123: Standardize “round-robin” casing/hyphenation

Use lowercase with hyphen for consistency with the rest of the file (see Line 1951: “Hôtes round-robin”).

-  "round_robin_host_unavailable_for_booking": "L'hôte Round Robin n'est pas disponible pour la réservation.",
+  "round_robin_host_unavailable_for_booking": "L'hôte round-robin n'est pas disponible pour la réservation.",

apps/web/public/static/locales/bg/common.json (1)

123-123: Align Round‑Robin branding and verify singular rename usage

Use consistent “Round‑Robin” branding across BG locale. Also, since this is a singularized key rename, re-verify no usages of the old plural key remain.

Apply:

-  "round_robin_host_unavailable_for_booking": "Домакинът на ротационния принцип не е наличен за резервация.",
+  "round_robin_host_unavailable_for_booking": "Round‑Robin домакинът не е наличен за резервация.",

Run to verify:

#!/bin/bash
# Should be zero matches for the deprecated key, and matches for the new one.
rg -n --hidden --glob '!*node_modules*' $'round_robin_hosts_unavailable_for_booking|round_robin_host_unavailable_for_booking'

apps/web/public/static/locales/es/common.json (4)

123-123: Spanish phrasing tweak for naturalness

Prefer “para la reserva” over “para reservas”.

-"round_robin_host_unavailable_for_booking": "El anfitrión de Round Robin no está disponible para reservas.",
+"round_robin_host_unavailable_for_booking": "El anfitrión de round robin no está disponible para la reserva.",

---

875-878: Tone consistency (Administra vs Gestiona) — optional

Elsewhere we often use “Administra …”. If you want consistent tone, prefer “Administra”.

 "oauth_clients": "Clientes OAuth",
-"oauth_clients_description": "Gestiona los clientes OAuth para tu organización",
+"oauth_clients_description": "Administra los clientes OAuth para tu organización",
 "create_oauth_client": "Crear cliente OAuth",
 "create_oauth_client_description": "Crea un nuevo cliente OAuth para integraciones de terceros",

---

3325-3329: Unify Spanish wording for workflow descriptors

Prefer singular “configuración” and improved word order for readability.

-"pbac_desc_view_workflows": "Ver flujos de trabajo existentes y sus configuraciones",
-"pbac_desc_update_workflows": "Editar y modificar configuraciones de flujos de trabajo",
-"pbac_desc_manage_workflows": "Acceso completo de gestión a todos los flujos de trabajo",
+"pbac_desc_view_workflows": "Ver flujos de trabajo existentes y su configuración",
+"pbac_desc_update_workflows": "Editar y modificar la configuración de los flujos de trabajo",
+"pbac_desc_manage_workflows": "Acceso de gestión completo a todos los flujos de trabajo",

---

3416-3416: New analytics label — LGTM; ensure cross-locale coverage

Spanish looks good here. Confirm presence across locales to avoid fallback.

You can verify coverage with:

#!/bin/bash
set -euo pipefail
locales=$(fd -t d . apps/web/public/static/locales -d 1 | wc -l)
for k in "failed_bookings" "stats" "booking_status"; do
  present=$(rg -l "\"$k\"" apps/web/public/static/locales/*/common.json | wc -l)
  echo "$k -> $present/$locales"
done

apps/web/public/static/locales/et/common.json (2)

123-123: Normalize “host” → “võõrustaja” (consistent terminology).

Same issue noted previously. Use “võõrustaja” across Estonian locale.

-  "round_robin_host_unavailable_for_booking": "Round Robin'i host ei ole broneerimiseks saadaval.",
+  "round_robin_host_unavailable_for_booking": "Round Robin'i võõrustaja ei ole broneerimiseks saadaval."

---

2255-2256: Use “marsruutimine” consistently for “routing”.

Line 2255 is fine. For 2256, replace “suunamise” with “marsruutimise” per locale convention.

-  "use_our_headless_routing_api": "Kasuta meie peata suunamise API-t ja omaenda vormi esitamiseks.",
+  "use_our_headless_routing_api": "Kasuta meie peata marsruutimise API-t ning esita oma vorm otse."

apps/web/public/static/locales/eu/common.json (2)

875-879: Namespace mismatch: rename oauth_ keys to match existing oAuth_ usage in code**

Components reference oAuth_; these new keys use oauth_ and won’t resolve. Standardize by renaming.

-"oauth_clients": "OAuth bezeroak",
-"oauth_clients_description": "Kudeatu zure erakundearen OAuth bezeroak",
-"create_oauth_client": "Sortu OAuth bezeroa",
-"create_oauth_client_description": "Sortu OAuth bezero berri bat hirugarrenen integrazioetarako",
-"oauth_client_deletion_message": "OAuth bezeroa behar bezala ezabatu da",
+"oAuth_clients": "OAuth bezeroak",
+"oAuth_clients_description": "Kudeatu zure erakundearen OAuth bezeroak",
+"create_oAuth_client": "Sortu OAuth bezeroa",
+"create_oAuth_client_description": "Sortu OAuth bezero berri bat hirugarrenen integrazioetarako",
+"oAuth_client_deletion_message": "OAuth bezeroa behar bezala ezabatu da",

---

3315-3320: Missing manage permission: add pbac_desc_manage_organization_attributes

Downstream UIs expect a “manage” descriptor for symmetry with create/read/update/delete. Without it, the label for “Manage attributes” renders undefined.

   "pbac_desc_view_organization_attributes": "Ikusi erakundearen atributuak",
   "pbac_desc_update_organization_attributes": "Eguneratu erakundearen atributuak",
   "pbac_desc_delete_organization_attributes": "Ezabatu erakundearen atributuak",
   "pbac_desc_create_organization_attributes": "Sortu erakundearen atributuak",
+  "pbac_desc_manage_organization_attributes": "Erakundeko atributuetan ekintza guztiak",

apps/web/public/static/locales/ar/common.json (7)

875-878: OAuth microcopy + terminology consistency (“المنظمة”)

Reuse the established term “المنظمة” and tighten phrasing for clarity.

   "oauth_clients": "عملاء OAuth",
-  "oauth_clients_description": "إدارة عملاء OAuth لمؤسستك",
+  "oauth_clients_description": "إدارة عملاء OAuth لمنظمتك",
   "create_oauth_client": "إنشاء عميل OAuth",
-  "create_oauth_client_description": "إنشاء عميل OAuth جديد للتكاملات مع الأطراف الثالثة",
+  "create_oauth_client_description": "إنشاء عميل OAuth جديد للتكامل مع جهات خارجية"

---

1844-1845: Standardize “Organization” as “المنظمة” in admin notices

Align with the file’s chosen terminology.

-  "only_admin_can_manage_directory_sync": "يمكن لمسؤول المؤسسة أو مالكها فقط إدارة إعدادات مزامنة الدليل",
-  "only_admin_can_manage_oauth_clients": "يمكن لمسؤول المؤسسة أو مالكها فقط إدارة عملاء OAuth",
+  "only_admin_can_manage_directory_sync": "يمكن لمسؤول المنظمة أو مالكها فقط إدارة إعدادات مزامنة الدليل",
+  "only_admin_can_manage_oauth_clients": "يمكن لمسؤول المنظمة أو مالكها فقط إدارة عملاء OAuth",

---

3315-3319: PBAC attribute permissions: use “المنظمة”

Keep “Organization” consistent.

   "pbac_resource_attributes": "السمات",
-  "pbac_desc_view_organization_attributes": "عرض سمات المؤسسة",
-  "pbac_desc_update_organization_attributes": "تحديث سمات المؤسسة",
-  "pbac_desc_delete_organization_attributes": "حذف سمات المؤسسة",
-  "pbac_desc_create_organization_attributes": "إنشاء سمات المؤسسة",
+  "pbac_desc_view_organization_attributes": "عرض سمات المنظمة",
+  "pbac_desc_update_organization_attributes": "تحديث سمات المنظمة",
+  "pbac_desc_delete_organization_attributes": "حذف سمات المنظمة",
+  "pbac_desc_create_organization_attributes": "إنشاء سمات المنظمة",

---

3323-3329: PBAC scope strings: standardize “فرق المنظمة”

Replace “المؤسسة” with “المنظمة” across scope descriptions.

-  "pbac_desc_manage_roles": "جميع الإجراءات على الأدوار عبر فرق المؤسسة",
+  "pbac_desc_manage_roles": "جميع الإجراءات على الأدوار عبر فرق المنظمة",
   "pbac_desc_create_workflows": "إنشاء وإعداد سير عمل جديد",
   "pbac_desc_view_workflows": "عرض سير العمل الحالي وإعداداته",
   "pbac_desc_update_workflows": "تعديل وتغيير إعدادات سير العمل",
   "pbac_desc_delete_workflows": "إزالة سير العمل من النظام",
   "pbac_desc_manage_workflows": "وصول كامل لإدارة جميع سير العمل",

---

3333-3333: PBAC scope: event types across org teams

Use “فرق المنظمة”.

-  "pbac_desc_manage_event_types": "جميع الإجراءات على أنواع الفعاليات عبر فرق المؤسسة",
+  "pbac_desc_manage_event_types": "جميع الإجراءات على أنواع الفعاليات عبر فرق المنظمة",

---

3341-3341: PBAC scope: teams across org

Use “فرق المنظمة”.

-  "pbac_desc_manage_teams": "جميع الإجراءات على الفرق عبر فرق المؤسسة",
+  "pbac_desc_manage_teams": "جميع الإجراءات على الفرق عبر فرق المنظمة",

---

3356-3356: PBAC scope: bookings across org

Use “فرق المنظمة”.

-  "pbac_desc_manage_bookings": "جميع الإجراءات على الحجوزات عبر فرق المؤسسة",
+  "pbac_desc_manage_bookings": "جميع الإجراءات على الحجوزات عبر فرق المنظمة",

apps/web/public/static/locales/pt-BR/common.json (1)

1844-1845: Terminologia “proprietário” vs “dono” (manter consistência)

Estes novos textos usam “proprietário” (correto), mas linhas próximas ainda usam “dono”:

• Line 1842: only_admin_can_manage_sso_org
• Line 1843: only_admin_can_manage_sso_org (exibição aqui mostra uma, mas valide ambas)

Padronize para “proprietário”.

Posso abrir um patch para trocar “dono” por “proprietário” nessas entradas remanescentes.

apps/web/public/static/locales/ro/common.json (2)

3416-3416: Good fix: “Rezervări eșuate” aligns with preferred terminology

This implements the earlier consistency request to use “Rezervări” over “Programări”.

---

3474-3475: Use “Starea rezervării” instead of “Status programare”

Prefer native “Stare” and “rezervării” per prior guidance. Also plural vs singular mismatch in current text.

-  "booking_status": "Status programare",
+  "booking_status": "Starea rezervării",

apps/web/public/static/locales/tr/common.json (1)

123-123: Align RR terminology to “Döngüsel organizatör”.

Use the established in-product term for consistency with other RR strings.

-  "round_robin_host_unavailable_for_booking": "Sıralı ev sahibi rezervasyon için uygun değil.",
+  "round_robin_host_unavailable_for_booking": "Döngüsel organizatör rezervasyon için uygun değil."

apps/web/public/static/locales/bn/common.json (1)

123-123: Fix BN possessive and hyphenation for consistency

Use the contracted possessive and consistent hyphenation (“রাউন্ড-রবিন”).

-  "round_robin_host_unavailable_for_booking": "রাউন্ড রবিন হোস্ট বুকিং এর জন্য অনুপলব্ধ।",
+  "round_robin_host_unavailable_for_booking": "রাউন্ড-রবিন হোস্ট বুকিংয়ের জন্য অনুপলব্ধ।",

apps/web/public/static/locales/km/common.json (7)

875-878: Use consistent term for “Organization” in Khmer

Replace “អង្គភាព” with “អង្គការ” for consistency with the rest of the locale.

 "oauth_clients": "កម្មវិធី OAuth",
-"oauth_clients_description": "គ្រប់គ្រងកម្មវិធី OAuth សម្រាប់អង្គភាពរបស់អ្នក",
+"oauth_clients_description": "គ្រប់គ្រងកម្មវិធី OAuth សម្រាប់អង្គការរបស់អ្នក",
 "create_oauth_client": "បង្កើតកម្មវិធី OAuth",
 "create_oauth_client_description": "បង្កើតកម្មវិធី OAuth ថ្មីសម្រាប់ការតភ្ជាប់ជាមួយកម្មវិធីភាគីទីបី",

---

1844-1845: Admin-only notices: replace “អង្គភាព” with “អង្គការ”

These two strings still use “អង្គភាព”. Switch to “អង្គការ”.

-"only_admin_can_manage_directory_sync": "មានតែអ្នកគ្រប់គ្រងឬម្ចាស់អង្គភាពប៉ុណ្ណោះដែលអាចគ្រប់គ្រងការកំណត់ការធ្វើសមកាលកម្មថត",
-"only_admin_can_manage_oauth_clients": "មានតែអ្នកគ្រប់គ្រងឬម្ចាស់អង្គភាពប៉ុណ្ណោះដែលអាចគ្រប់គ្រងកម្មវិធី OAuth",
+"only_admin_can_manage_directory_sync": "មានតែអ្នកគ្រប់គ្រងឬម្ចាស់អង្គការប៉ុណ្ណោះដែលអាចគ្រប់គ្រងការកំណត់ការធ្វើសមកាលកម្មថត",
+"only_admin_can_manage_oauth_clients": "មានតែអ្នកគ្រប់គ្រងឬម្ចាស់អង្គការប៉ុណ្ណោះដែលអាចគ្រប់គ្រងកម្មវិធី OAuth",

---

3315-3319: PBAC attribute descriptors: switch “អង្គភាព” → “អង្គការ”

Align with established term.

 "pbac_resource_attributes": "គុណលក្ខណៈ",
-"pbac_desc_view_organization_attributes": "មើលគុណលក្ខណៈអង្គភាព",
+"pbac_desc_view_organization_attributes": "មើលគុណលក្ខណៈអង្គការ",
-"pbac_desc_update_organization_attributes": "ធ្វើបច្ចុប្បន្នភាពគុណលក្ខណៈអង្គភាព",
+"pbac_desc_update_organization_attributes": "ធ្វើបច្ចុប្បន្នភាពគុណលក្ខណៈអង្គការ",
-"pbac_desc_delete_organization_attributes": "លុបគុណលក្ខណៈអង្គភាព",
+"pbac_desc_delete_organization_attributes": "លុបគុណលក្ខណៈអង្គការ",
-"pbac_desc_create_organization_attributes": "បង្កើតគុណលក្ខណៈអង្គភាព",
+"pbac_desc_create_organization_attributes": "បង្កើតគុណលក្ខណៈអង្គការ",

---

3323-3323: PBAC roles descriptor: use “អង្គការ”

-"pbac_desc_manage_roles": "សកម្មភាពទាំងអស់លើតួនាទីក្នុងក្រុមអង្គភាពទាំងអស់",
+"pbac_desc_manage_roles": "សកម្មភាពទាំងអស់លើតួនាទីក្នុងក្រុមអង្គការទាំងអស់",

---

3333-3333: PBAC event-types descriptor: use “អង្គការ”

-"pbac_desc_manage_event_types": "សកម្មភាពទាំងអស់លើប្រភេទព្រឹត្តិការណ៍ក្នុងក្រុមអង្គភាពទាំងអស់",
+"pbac_desc_manage_event_types": "សកម្មភាពទាំងអស់លើប្រភេទព្រឹត្តិការណ៍ក្នុងក្រុមអង្គការទាំងអស់",

---

3341-3341: PBAC teams descriptor: use “អង្គការ”

-"pbac_desc_manage_teams": "សកម្មភាពទាំងអស់លើក្រុមក្នុងក្រុមអង្គភាពទាំងអស់",
+"pbac_desc_manage_teams": "សកម្មភាពទាំងអស់លើក្រុមក្នុងក្រុមអង្គការទាំងអស់",

---

3356-3356: PBAC bookings descriptor: remove “ក្រុម” and use “អង្គការ”

Use “ក្នុងអង្គការ”.

-"pbac_desc_manage_bookings": "សកម្មភាពទាំងអស់លើការកក់ក្នុងក្រុមអង្គភាពទាំងអស់",
+"pbac_desc_manage_bookings": "សកម្មភាពទាំងអស់លើការកក់ក្នុងអង្គការ",

apps/web/public/static/locales/fi/common.json (1)

1-3476: Unify “round robin” hyphenation to “round-robin” throughout fi/common.json

Standardize all instances of “round robin” with hyphens. For example:

• event_reassigned_subtitle
  from
  “… round robin -todennäköisyyteesi”
  to
  “… round-robin-todennäköisyyteesi”

• round_robin_host_unavailable_for_booking
  from
  “Round Robin -isäntä ei ole varattavissa.”
  to
  “Round-robin-isäntä ei ole varattavissa.”

• add_one_fixed_attendee
  from
  “… kierrätä round robin -tyyliin …”
  to
  “… kierrätä round-robin-tyyliin …”

• add_your_team_members
  from
  “… round robin -aikataulutuksella”
  to
  “… round-robin-aikataulutuksella”

• skip_rr_assignment_label
  from
  “Ohita round robin -jako …”
  to
  “Ohita round-robin-jako …”

• reassign_to_another_rr_host
  from
  “… round robin -isännälle”
  to
  “… round-robin-isännälle”

• reassign_round_robin_host
  from
  “Uudelleenmääritä round robin -isäntä”
  to
  “Uudelleenmääritä round-robin-isäntä”

• team_member_round_robin_reassign(_description)
  from
  “… round robin -järjestäjä …”
  to
  “… round-robin-järjestäjä …”

• invalid_round_robin_host
  from
  “… ei ole kelvollinen round robin -järjestäjä …”
  to
  “… ei ole kelvollinen round-robin-järjestäjä …”

• salesforce_route_to_owner / salesforce_do_not_route_to_owner / salesforce_if_free_email_domain_skip_owner_check
  replace “Round Robin -” or “round robin -” with “round-robin-”

• rr_reset_interval_description
  from
  “… round robin -varauslaskuri …”
  to
  “… round-robin-varauslaskuri …”

• include_no_show_in_rr_calculation
  from
  “… round robin -laskelmiin”
  to
  “… round-robin-laskelmiin”

• load_balancing_warning
  from
  “… round robin -tapahtumatyypeistäsi”
  to
  “… round-robin-tapahtumatyypeistäsi”

• rr_load_balancing_disabled_with_groups
  from
  “… round robin -ryhmien kanssa”
  to
  “… round-robin-ryhmien kanssa”

Please update each key’s translation accordingly to use “round-robin” as a single hyphenated term.

apps/web/public/static/locales/bn/common.json (1)

123-123: Fix BN possessive contraction (“বুকিংয়ের”).

Use the contracted possessive form to match common BN usage and nearby strings.

-  "round_robin_host_unavailable_for_booking": "রাউন্ড রবিন হোস্ট বুকিং এর জন্য অনুপলব্ধ।",
+  "round_robin_host_unavailable_for_booking": "রাউন্ড রবিন হোস্ট বুকিংয়ের জন্য অনুপলব্ধ।",

apps/web/public/static/locales/no/common.json (2)

123-123: Norwegian wording consistency: booking → bestilling

Align with nearby keys (Line 121 uses “bestilling”). Recommend Norwegian “bestilling” over “booking”.

-  "round_robin_host_unavailable_for_booking": "Round Robin-vert er ikke tilgjengelig for booking.",
+  "round_robin_host_unavailable_for_bestilling": "Round Robin-vert er ikke tilgjengelig for bestilling.",

Note: For full consistency, also consider updating Line 122 (“booking”) to “bestilling”.

---

3324-3329: Unresolved terminology consistency: “organisasjonsteam” and “arrangementstyper”

Use “organisasjonens team” and “hendelsestyper” consistently (matches usage elsewhere in file).

Run this to surface remaining inconsistent terms:

#!/bin/bash
rg -n -S "organisasjonsteam|arrangementstype" apps/web/public/static/locales/no/common.json

Apply:

-  "pbac_desc_manage_roles": "Alle handlinger på roller på tvers av organisasjonsteam",
+  "pbac_desc_manage_roles": "Alle handlinger på roller på tvers av organisasjonens team",

-  "pbac_desc_manage_event_types": "Alle handlinger på arrangementstyper på tvers av organisasjonsteam",
+  "pbac_desc_manage_event_types": "Alle handlinger på hendelsestyper på tvers av organisasjonens team",

-  "pbac_desc_manage_teams": "Alle handlinger på team på tvers av organisasjonsteam",
+  "pbac_desc_manage_teams": "Alle handlinger på team på tvers av organisasjonens team",

-  "pbac_desc_manage_bookings": "Alle handlinger på bookinger på tvers av organisasjonsteam",
+  "pbac_desc_manage_bookings": "Alle handlinger på bookinger på tvers av organisasjonens team",

Also applies to: 3333-3333, 3341-3342, 3356-3356

apps/web/public/static/locales/ca/common.json (2)

3383-3383: Use imperative mood consistently for “add_*”.

Align with dominant pattern (“Afegeix …”).

-  "add_group": "Afegir grup",
+  "add_group": "Afegeix un grup",

---

2255-2256: Fix terminology and grammar (“routing” → “encaminament”, “headless” → “sense interfície”, article “els enviaments”).

Use established terms and correct article agreement.

-  "use_our_headless_routing_api": "Utilitza la nostra API de routing headless i fes servir el teu propi formulari per a les enviaments.",
+  "use_our_headless_routing_api": "Utilitza la nostra API d'encaminament sense interfície i fes servir el teu propi formulari per als enviaments.",

apps/web/public/static/locales/tr/common.json (3)

123-123: RR terminology: use “Döngüsel organizatör” (consistent in-product).

Align with existing RR phrasing used elsewhere in TR locale.

-  "round_robin_host_unavailable_for_booking": "Sıralı ev sahibi rezervasyon için uygun değil.",
+  "round_robin_host_unavailable_for_booking": "Döngüsel organizatör rezervasyon için uygun değil."

---

1844-1845: Standardize “Kuruluş” vs. “Organizasyon” (admin-only notices).

Apply the previously suggested terminology.

-  "only_admin_can_manage_directory_sync": "Dizin senkronizasyon ayarlarını yalnızca organizasyonun yöneticisi veya sahibi yönetebilir",
-  "only_admin_can_manage_oauth_clients": "OAuth istemcilerini yalnızca organizasyonun yöneticisi veya sahibi yönetebilir",
+  "only_admin_can_manage_directory_sync": "Dizin senkronizasyonu ayarlarını yalnızca kuruluşun yöneticisi veya sahibi yönetebilir",
+  "only_admin_can_manage_oauth_clients": "OAuth istemcilerini yalnızca kuruluşun yöneticisi veya sahibi yönetebilir"

---

3315-3334: PBAC descriptions: replace “Organizasyon” → “Kuruluş” for consistency.

Keep role/resource phrasing intact, just align the noun.

   "pbac_resource_attributes": "Öznitelikler",
-  "pbac_desc_view_organization_attributes": "Organizasyon özniteliklerini görüntüle",
-  "pbac_desc_update_organization_attributes": "Organizasyon özniteliklerini güncelle",
-  "pbac_desc_delete_organization_attributes": "Organizasyon özniteliklerini sil",
-  "pbac_desc_create_organization_attributes": "Organizasyon öznitelikleri oluştur",
+  "pbac_desc_view_organization_attributes": "Kuruluş özniteliklerini görüntüle",
+  "pbac_desc_update_organization_attributes": "Kuruluş özniteliklerini güncelle",
+  "pbac_desc_delete_organization_attributes": "Kuruluş özniteliklerini sil",
+  "pbac_desc_create_organization_attributes": "Kuruluş öznitelikleri oluştur",

-  "pbac_desc_manage_roles": "Organizasyon ekipleri genelinde roller üzerindeki tüm işlemler",
+  "pbac_desc_manage_roles": "Kuruluş ekipleri genelinde roller üzerindeki tüm işlemler",

-  "pbac_desc_manage_event_types": "Organizasyon ekipleri genelinde etkinlik türleri üzerindeki tüm işlemler",
+  "pbac_desc_manage_event_types": "Kuruluş ekipleri genelinde etkinlik türleri üzerindeki tüm işlemler",

-  "pbac_desc_manage_teams": "Organizasyon ekipleri genelinde ekipler üzerindeki tüm işlemler",
+  "pbac_desc_manage_teams": "Kuruluş ekipleri genelinde ekipler üzerindeki tüm işlemler",

-  "pbac_desc_manage_bookings": "Organizasyon ekipleri genelinde rezervasyonlar üzerindeki tüm işlemler",
+  "pbac_desc_manage_bookings": "Kuruluş ekipleri genelinde rezervasyonlar üzerindeki tüm işlemler"

Also applies to: 3356-3356

apps/web/public/static/locales/ko/common.json (1)

875-878: Use “타사” instead of “서드파티” (consistency with standard Korean diction).

Prefer “타사” in place of “서드파티”.

   "create_oauth_client": "OAuth 클라이언트 생성",
-  "create_oauth_client_description": "서드파티 통합을 위한 새 OAuth 클라이언트 생성"
+  "create_oauth_client_description": "타사 통합을 위한 새 OAuth 클라이언트 생성"

Also ensure these OAuth keys exist across all locales to avoid fallback-to-English.

#!/bin/bash
set -euo pipefail

locales_root='apps/web/public/static/locales'
keys=(oauth_clients oauth_clients_description create_oauth_client create_oauth_client_description)

missing=0
fd common.json "$locales_root" -t f | while read -r f; do
  for k in "${keys[@]}"; do
    if ! jq -e --arg k "$k" 'has($k)' "$f" >/dev/null 2>&1; then
      echo "MISSING: $f → $k"
      missing=1
    fi
  done
done

exit $missing

apps/web/public/static/locales/ru/common.json (1)

123-123: Unify “host” terminology and Round Robin phrasing (duplicate of prior suggestion)

Prefer “организатор” and translate “Round Robin” as “по очереди” for consistency across RU locale.

-  "round_robin_host_unavailable_for_booking": "Хост Round Robin недоступен для бронирования.",
+  "round_robin_host_unavailable_for_booking": "Организатор по очереди недоступен для бронирования."

apps/web/public/static/locales/eu/common.json (2)

875-878: Inconsistent OAuth key casing vs existing UI references (oAuth_*). Standardize.

New keys use oauth_* while existing components and other keys use oAuth_*. This will result in missing strings at runtime unless code is updated.

Option A (rename keys here to match existing code):

-  "oauth_clients": "OAuth bezeroak",
-  "oauth_clients_description": "Kudeatu zure erakundearen OAuth bezeroak",
-  "create_oauth_client": "Sortu OAuth bezeroa",
-  "create_oauth_client_description": "Sortu OAuth bezero berri bat hirugarrenen integrazioetarako"
+  "oAuth_clients": "OAuth bezeroak",
+  "oAuth_clients_description": "Kudeatu zure erakundearen OAuth bezeroak",
+  "create_oAuth_client": "Sortu OAuth bezeroa",
+  "create_oAuth_client_description": "Sortu OAuth bezero berri bat hirugarrenen integrazioetarako"

Option B: update all component references to the new lowercase oauth_* namespace. Pick one approach and make keys and code consistent.

---

3315-3319: Missing manage-level PBAC descriptor for organization attributes causes blank labels

For symmetry with other resources (roles, teams, event types, bookings, workflows), add the manage descriptor. Dynamic permission-label UIs will otherwise render undefined.

Apply:

   "pbac_desc_view_organization_attributes": "Ikusi erakundearen atributuak",
   "pbac_desc_update_organization_attributes": "Eguneratu erakundearen atributuak",
   "pbac_desc_delete_organization_attributes": "Ezabatu erakundearen atributuak",
   "pbac_desc_create_organization_attributes": "Sortu erakundearen atributuak",
+  "pbac_desc_manage_organization_attributes": "Erakundeko atributuetan ekintza guztiak",

apps/web/public/static/locales/hu/common.json (3)

123-123: Unify Round‑Robin terminology and grammar

Replace localized “körforgó” with consistent “Round‑Robin” and fix “nem elérhető/érhető” agreement.

-  "round_robin_host_unavailable_for_booking": "A körforgó házigazda nem elérhető foglalásra.",
+  "round_robin_host_unavailable_for_booking": "A Round‑Robin házigazda nem érhető el foglalásra."

To find other occurrences to align:

#!/bin/bash
rg -n $'körforgó|Körmérkőzés|Round Robin' apps/web/public/static/locales/hu/common.json

---

875-878: Use consistent formal tone in OAuth client section

Align with formal address used in this locale.

   "oauth_clients": "OAuth kliensek",
-  "oauth_clients_description": "Kezeld szervezeted OAuth klienseit",
+  "oauth_clients_description": "Kezelje szervezete OAuth klienseit",
   "create_oauth_client": "OAuth kliens létrehozása",
-  "create_oauth_client_description": "Új OAuth kliens létrehozása harmadik féltől származó integrációkhoz",
+  "create_oauth_client_description": "Új OAuth kliens létrehozása harmadik féltől származó integrációk számára"

---

2255-2256: Fix tone and clarity for headless routing API option

Use formal address and avoid repetition.

   "use_my_own_form": "Saját űrlap használata",
-  "use_our_headless_routing_api": "Használd a headless routing API-nkat és használd saját űrlapodat a beküldésekhez.",
+  "use_our_headless_routing_api": "Használja headless útválasztó API‑nkat, és használja saját űrlapját a beküldésekhez."

apps/web/public/static/locales/pl/common.json (1)

3473-3474: Re-verify potential ‘stats’ key duplication

Past commits said duplication was resolved; ensure there’s only one "stats" key in this file now.

#!/bin/bash
# Count occurrences of "stats" key in this file
rg -n '^\s*"stats"\s*:' apps/web/public/static/locales/pl/common.json

apps/web/public/static/locales/he/common.json (1)

875-878: Unify OAuth key casing (use oauth_ consistently)*

New keys use oauth_* while existing keys still use oAuth_*. Mixed casing risks lookup bugs. Standardize to oauth_* and update code references accordingly.

Apply this diff in this file:

-  "oAuth": "OAuth",
-  "oAuth_client_creation_form": "טופס יצירת לקוח OAuth",
-  "oAuth_client_creation_form_description": "זהו הטופס ליצירת לקוח OAuth חדש",
-  "oAuth_client_updation_form": "טופס עדכון לקוח OAuth",
-  "oAuth_client_updation_form_description": "זהו הטופס לעריכת לקוח OAuth קיים",
+  "oauth": "OAuth",
+  "oauth_client_creation_form": "טופס יצירת לקוח OAuth",
+  "oauth_client_creation_form_description": "זהו הטופס ליצירת לקוח OAuth חדש",
+  "oauth_client_updation_form": "טופס עדכון לקוח OAuth",
+  "oauth_client_updation_form_description": "זהו הטופס לעריכת לקוח OAuth קיים",

Also update code usages:

• t("oAuth_client_creation_form") → t("oauth_client_creation_form")
• t("oAuth_client_creation_form_description") → t("oauth_client_creation_form_description")
• t("oAuth_client_updation_form") → t("oauth_client_updation_form")
• t("oAuth_client_updation_form_description") → t("oauth_client_updation_form_description")

Also applies to: 2441-2446

apps/web/public/static/locales/bg/common.json (1)

123-123: Use consistent “Round‑Robin” branding and fix phrasing

Prefer the established “Round‑Robin” term in BG locale and more natural word order.

-  "round_robin_host_unavailable_for_booking": "Домакинът на Round Robin не е наличен за резервация.",
+  "round_robin_host_unavailable_for_booking": "Round‑Robin домакинът не е наличен за резервация.",

Run to ensure only the new singular key is referenced and the old plural isn’t:

#!/bin/bash
set -euo pipefail
echo "Usages of new key:"
rg -n --hidden --glob '!*node_modules*' $'round_robin_host_unavailable_for_booking' || true
echo
echo "Usages of old plural key (should be 0):"
rg -n --hidden --glob '!*node_modules*' $'round_robin_hosts_unavailable_for_booking' || true
echo
echo "Check all locales define the new key:"
total_locales=$(fd -t f 'common.json' apps/web/public/static/locales | wc -l | tr -d ' ')
with_key=$(rg -n $'"round_robin_host_unavailable_for_booking"' apps/web/public/static/locales | awk -F: '{print $1}' | sort -u | wc -l | tr -d ' ')
echo "Locales with key: $with_key / $total_locales"
if [ "$with_key" -ne "$total_locales" ]; then
  echo "Missing locales:"
  comm -23 <(fd -t f 'common.json' apps/web/public/static/locales | sort) <(rg -n $'"round_robin_host_unavailable_for_booking"' apps/web/public/static/locales | awk -F: '{print $1}' | sort -u)
fi

apps/web/public/static/locales/km/common.json (9)

352-352: Fix Khmer phrasing for “take turns” in round-robin groups helper

Use “វេនគ្នា” instead of “លើកដៃ” for “take turns”.

-  "round_robin_groups_helper": "មនុស្សក្នុងក្រុមនឹងលើកដៃជាបន្តបន្ទាប់ ហើយមនុស្សម្នាក់ពីក្រុមនីមួយៗនឹងចូលរួមក្នុងព្រឹត្តិការណ៍។",
+  "round_robin_groups_helper": "មនុស្សក្នុងក្រុមនឹងវេនគ្នា ហើយមនុស្សម្នាក់ពីក្រុមនីមួយៗនឹងចូលរួមក្នុងព្រឹត្តិការណ៍។",

---

2255-2256: Use “Headless” in English for clarity

Avoid literal “ដោយគ្មានចំណងជើង”; keep “Headless” in English.

-  "use_our_headless_routing_api": "ប្រើ API ដឹកនាំដោយគ្មានចំណងជើងរបស់យើង និងប្រើទម្រង់ផ្ទាល់ខ្លួនរបស់អ្នកសម្រាប់ការដាក់ស្នើ។",
+  "use_our_headless_routing_api": "ប្រើ API Routing (Headless) របស់យើង ហើយប្រើទម្រង់ផ្ទាល់ខ្លួនរបស់អ្នកសម្រាប់ការដាក់ស្នើ។",

---

875-878: Use consistent term for “Organization”: replace “អង្គភាព” with “អង្គការ”

Maintain consistency across the km locale.

-  "oauth_clients_description": "គ្រប់គ្រងកម្មវិធី OAuth សម្រាប់អង្គភាពរបស់អ្នក",
+  "oauth_clients_description": "គ្រប់គ្រងកម្មវិធី OAuth សម្រាប់អង្គាររបស់អ្នក",

---

1844-1845: Admin-only notices: “អង្គភាព” → “អង្គការ”

Apply the preferred term “អង្គការ”.

-  "only_admin_can_manage_directory_sync": "មានតែអ្នកគ្រប់គ្រងឬម្ចាស់អង្គភាពប៉ុណ្ណោះដែលអាចគ្រប់គ្រងការកំណត់ការធ្វើសមកាលកម្មថត",
+  "only_admin_can_manage_directory_sync": "មានតែអ្នកគ្រប់គ្រងឬម្ចាស់អង្គការប៉ុណ្ណោះដែលអាចគ្រប់គ្រងការកំណត់ការធ្វើសមកាលកម្មថត",
-  "only_admin_can_manage_oauth_clients": "មានតែអ្នកគ្រប់គ្រងឬម្ចាស់អង្គភាពប៉ុណ្ណោះដែលអាចគ្រប់គ្រងកម្មវិធី OAuth",
+  "only_admin_can_manage_oauth_clients": "មានតែអ្នកគ្រប់គ្រងឬម្ចាស់អង្គការប៉ុណ្ណោះដែលអាចគ្រប់គ្រងកម្មវិធី OAuth",

---

3315-3319: PBAC descriptors: use “អង្គការ” for Organization

Align terminology in the four attribute descriptors.

   "pbac_resource_attributes": "គុណលក្ខណៈ",
-  "pbac_desc_view_organization_attributes": "មើលគុណលក្ខណៈអង្គភាព",
+  "pbac_desc_view_organization_attributes": "មើលគុណលក្ខណៈអង្គការ",
-  "pbac_desc_update_organization_attributes": "ធ្វើបច្ចុប្បន្នភាពគុណលក្ខណៈអង្គភាព",
+  "pbac_desc_update_organization_attributes": "ធ្វើបច្ចុប្បន្នភាពគុណលក្ខណៈអង្គការ",
-  "pbac_desc_delete_organization_attributes": "លុបគុណលក្ខណៈអង្គភាព",
+  "pbac_desc_delete_organization_attributes": "លុបគុណលក្ខណៈអង្គការ",
-  "pbac_desc_create_organization_attributes": "បង្កើតគុណលក្ខណៈអង្គភាព",
+  "pbac_desc_create_organization_attributes": "បង្កើតគុណលក្ខណៈអង្គការ",

To ensure no remaining “អង្គភាព” instances linger in this locale, run:

#!/bin/bash
rg -n $'អង្គភាព' apps/web/public/static/locales/km/common.json

---

3323-3323: PBAC manage roles: replace “ក្រុមអង្គភាព”

Use the consistent “អង្គការ”.

-  "pbac_desc_manage_roles": "សកម្មភាពទាំងអស់លើតួនាទីក្នុងក្រុមអង្គភាព",
+  "pbac_desc_manage_roles": "សកម្មភាពទាំងអស់លើតួនាទីក្នុងអង្គការ",

---

3333-3333: PBAC manage event types: use “អង្គការ”

Replace “ក្រុមអង្គភាព” with “អង្គការ”.

-  "pbac_desc_manage_event_types": "សកម្មភាពទាំងអស់លើប្រភេទព្រឹត្តិការណ៍ក្នុងក្រុមអង្គភាព",
+  "pbac_desc_manage_event_types": "សកម្មភាពទាំងអស់លើប្រភេទព្រឹត្តិការណ៍ក្នុងអង្គការ",

---

3341-3341: PBAC manage teams: use “អង្គការ”

Consistent organization term.

-  "pbac_desc_manage_teams": "សកម្មភាពទាំងអស់លើក្រុមក្នុងក្រុមអង្គភាព",
+  "pbac_desc_manage_teams": "សកម្មភាពទាំងអស់លើក្រុមក្នុងអង្គការ",

---

3356-3356: PBAC bookings descriptor: replace “ក្រុមអង្គភាព”

Adopt the prior suggested phrasing.

-  "pbac_desc_manage_bookings": "សកម្មភាពទាំងអស់លើការកក់ក្នុងក្រុមអង្គភាព",
+  "pbac_desc_manage_bookings": "សកម្មភាពទាំងអស់លើការកក់ក្នុងអង្គការ",

apps/web/public/static/locales/uk/common.json (1)

123-123: Key rename present; ensure all locales updated.

The new key exists here. Cross-check other locales for the same addition to prevent fallback-to-English at runtime. See earlier reviewer’s report listing missing locales.

If helpful, re-run the repo-wide scan from the earlier comment to confirm no lingering references to the old plural key and that all locales now include the new singular key.

apps/web/public/static/locales/it/common.json (2)

123-123: Normalize terminology: “organizzatore” and lowercase “round robin”.

Use the established phrasing used elsewhere in Italian locale.

Consider running the script below to ensure no lingering references to the old key remain.

-  "round_robin_host_unavailable_for_booking": "L'host Round Robin non è disponibile per la prenotazione.",
+  "round_robin_host_unavailable_for_booking": "L'organizzatore round robin non è disponibile per la prenotazione.",

To verify old vs new key usage across the repo:

#!/bin/bash
set -euo pipefail
echo "Old key occurrences:"
rg -n --hidden --glob '!.git' 'round_robin_hosts_unavailable_for_booking' || true
echo
echo "New key occurrences:"
rg -n --hidden --glob '!.git' 'round_robin_host_unavailable_for_booking' || true

---

3366-3366: Uniformare “Round Robin” → “round robin”.

Keep capitalization consistent with the rest of the file.

-  "rr_load_balancing_disabled_with_groups": "Il bilanciamento del carico non è disponibile con i gruppi Round Robin",
+  "rr_load_balancing_disabled_with_groups": "Il bilanciamento del carico non è disponibile con i gruppi round robin",

apps/web/public/static/locales/fi/common.json (2)

123-123: Finnish hyphenation: prefer “Round-robin” compound

Use the hyphenated compound without the spaced hyphen.

-  "round_robin_host_unavailable_for_booking": "Round Robin -isäntä ei ole varattavissa.",
+  "round_robin_host_unavailable_for_booking": "Round-robin-isäntä ei ole varattavissa."

---

3445-3475: Clarify “created_at” semantics

Use a wording that explicitly denotes creation time.

-  "webhook_created_at": "Webhookin aika",
+  "webhook_created_at": "Webhookin luontiaika",

apps/web/public/static/locales/ar/common.json (5)

875-878: Use the glossary term “المنظمة” and tighten OAuth microcopy

Same request was raised previously and remains unresolved here.

   "oauth_clients": "عملاء OAuth",
-  "oauth_clients_description": "إدارة عملاء OAuth لمؤسستك",
+  "oauth_clients_description": "إدارة عملاء OAuth لمنظمتك",
   "create_oauth_client": "إنشاء عميل OAuth",
-  "create_oauth_client_description": "إنشاء عميل OAuth جديد للتكاملات مع الأطراف الثالثة",
+  "create_oauth_client_description": "إنشاء عميل OAuth جديد للتكامل مع جهات خارجية"

---

1844-1845: Terminology consistency: “المنظمة” instead of “المؤسسة”

Matches existing usage elsewhere in this file.

-  "only_admin_can_manage_directory_sync": "يمكن لمسؤول المؤسسة أو مالكها فقط إدارة إعدادات مزامنة الدليل",
-  "only_admin_can_manage_oauth_clients": "يمكن لمسؤول المؤسسة أو مالكها فقط إدارة عملاء OAuth",
+  "only_admin_can_manage_directory_sync": "يمكن لمسؤول المنظمة أو مالكها فقط إدارة إعدادات مزامنة الدليل",
+  "only_admin_can_manage_oauth_clients": "يمكن لمسؤول المنظمة أو مالكها فقط إدارة عملاء OAuth"

---

3315-3320: PBAC attribute permissions: use “المنظمة” consistently

Prior suggestion still applies.

   "pbac_resource_attributes": "السمات",
-  "pbac_desc_view_organization_attributes": "عرض سمات المؤسسة",
-  "pbac_desc_update_organization_attributes": "تحديث سمات المؤسسة",
-  "pbac_desc_delete_organization_attributes": "حذف سمات المؤسسة",
-  "pbac_desc_create_organization_attributes": "إنشاء سمات المؤسسة",
+  "pbac_desc_view_organization_attributes": "عرض سمات المنظمة",
+  "pbac_desc_update_organization_attributes": "تحديث سمات المنظمة",
+  "pbac_desc_delete_organization_attributes": "حذف سمات المنظمة",
+  "pbac_desc_create_organization_attributes": "إنشاء سمات المنظمة",

---

3324-3334: PBAC scopes: replace “المؤسسة” with “المنظمة” across scopes

Keep the same entity term across all organization-scoped strings.

-  "pbac_desc_manage_roles": "جميع الإجراءات على الأدوار عبر فرق المؤسسة",
+  "pbac_desc_manage_roles": "جميع الإجراءات على الأدوار عبر فرق المنظمة",
   "pbac_desc_create_workflows": "إنشاء وإعداد سير عمل جديد",
   "pbac_desc_view_workflows": "عرض سير العمل الحالي وإعداداته",
   "pbac_desc_update_workflows": "تعديل وتغيير إعدادات سير العمل",
   "pbac_desc_delete_workflows": "إزالة سير العمل من النظام",
   "pbac_desc_manage_workflows": "وصول كامل لإدارة جميع سير العمل",
-  "pbac_desc_manage_event_types": "جميع الإجراءات على أنواع الفعاليات عبر فرق المؤسسة",
+  "pbac_desc_manage_event_types": "جميع الإجراءات على أنواع الفعاليات عبر فرق المنظمة",
-  "pbac_desc_manage_teams": "جميع الإجراءات على الفرق عبر فرق المؤسسة",
+  "pbac_desc_manage_teams": "جميع الإجراءات على الفرق عبر فرق المنظمة",
-  "pbac_desc_manage_bookings": "جميع الإجراءات على الحجوزات عبر فرق المؤسسة",
+  "pbac_desc_manage_bookings": "جميع الإجراءات على الحجوزات عبر فرق المنظمة"

Also applies to: 3341-3341, 3356-3356

---

3445-3472: Fix webhook metadata microcopy and standardize “ويبهوك”

Previous suggestions remain unaddressed. Use “ويبهوك” consistently and correct meanings.

-  "webhook_trigger_event": "اسم حدث المشغل (مثل BOOKING_CREATED، BOOKING_CANCELLED)",
-  "webhook_created_at": "وقت الويب هوك",
-  "webhook_type": "رابط نوع الحدث",
-  "webhook_title": "اسم نوع الحدث",
+  "webhook_trigger_event": "اسم حدث المشغِّل (مثل BOOKING_CREATED، BOOKING_CANCELLED)",
+  "webhook_created_at": "وقت إنشاء الويبهوك",
+  "webhook_type": "نوع الحدث",
+  "webhook_title": "عنوان الحدث",
   "webhook_start_time": "وقت بدء الحدث",
   "webhook_end_time": "وقت انتهاء الحدث",
   "webhook_description": "وصف الحدث كما هو موضح في إعدادات نوع الحدث",
   "webhook_location": "موقع الحدث",
   "webhook_uid": "معرف الحجز",
   "webhook_reschedule_uid": "المعرف الفريد لإعادة الجدولة",
   "webhook_cancellation_reason": "سبب الإلغاء",
   "webhook_rejection_reason": "سبب الرفض",
   "webhook_organizer_name": "اسم المنظم",
   "webhook_organizer_email": "البريد الإلكتروني للمنظم",
   "webhook_organizer_timezone": "المنطقة الزمنية للمنظم (مثل 'America/New_York'، 'Asia/Kolkata')",
   "webhook_organizer_locale": "لغة المنظم (مثل 'en'، 'fr')",
   "webhook_attendee_name": "اسم الحاضر الأول",
   "webhook_attendee_email": "البريد الإلكتروني للحاضر الأول",
   "webhook_attendee_timezone": "المنطقة الزمنية للحاضر الأول",
   "webhook_attendee_locale": "لغة الحاضر الأول",
   "webhook_team_name": "اسم الفريق المحجوز",
   "webhook_team_members": "أعضاء الفريق المحجوز",
   "webhook_video_call_url": "رابط مكالمة الفيديو للاجتماع",
-  "webhook_hide_variables": "إخفاء المتغيرات",
-  "webhook_show_variable": "إظهار المتغيرات المتاحة",
+  "webhook_hide_variables": "إخفاء المتغيرات",
+  "webhook_show_variable": "إظهار المتغير المتاح",
   "webhook_event_and_booking": "الفعالية والحجز",
   "webhook_people": "الأشخاص",
   "webhook_teams": "الفرق",
   "webhook_metadata": "البيانات الوصفية",

If “webhook_type” intended “Webhook type” (not the event type), use:

-  "webhook_type": "رابط نوع الحدث",
+  "webhook_type": "نوع الويبهوك"

apps/web/public/static/locales/ro/common.json (2)

875-878: Switch to polite/plural tone (“dvs.”) for OAuth strings

Align with UI tone guidance used across the file.

-  "oauth_clients": "Clienți OAuth",
-  "oauth_clients_description": "Gestionează clienții OAuth pentru organizația ta",
-  "create_oauth_client": "Creează un client OAuth",
-  "create_oauth_client_description": "Creează un nou client OAuth pentru integrări terțe",
+  "oauth_clients": "Clienți OAuth",
+  "oauth_clients_description": "Gestionați clienții OAuth pentru organizația dvs.",
+  "create_oauth_client": "Creați un client OAuth",
+  "create_oauth_client_description": "Creați un nou client OAuth pentru integrări terțe",

---

3475-3475: Use “Starea rezervării” (terminology consistency)

Follow prior guidance for booking state terminology.

-  "booking_status": "Status programare",
+  "booking_status": "Starea rezervării",

apps/web/public/static/locales/ja/common.json (1)

123-123: JP phrasing nit: drop the extra “の”

More natural and consistent with nearby strings.

-  "round_robin_host_unavailable_for_booking": "ラウンドロビンのホストは予約できません。",
+  "round_robin_host_unavailable_for_booking": "ラウンドロビンホストは予約できません。",

apps/web/public/static/locales/pt/common.json (1)

123-123: PT-PT phrasing for Round Robin host unavailability

Align with PT-PT and past guidance: prefer “reserva” and “de Round Robin”.

-  "round_robin_host_unavailable_for_booking": "O anfitrião do Round Robin não está disponível para agendamento.",
+  "round_robin_host_unavailable_for_booking": "O anfitrião de Round Robin não está disponível para reserva.",

apps/web/public/static/locales/es/common.json (7)

123-123: Spanish phrasing tweak (singular article sounds more natural).
El anfitrión de Round Robin no está disponible para la reserva.

Apply:

-"round_robin_host_unavailable_for_booking": "El anfitrión de Round Robin no está disponible para reservas.",
+"round_robin_host_unavailable_for_booking": "El anfitrión de Round Robin no está disponible para la reserva.",

---

875-878: Tone consistency: prefer “Administra” over “Gestiona”.
To match prevalent tone elsewhere in this file.

 "oauth_clients": "Clientes OAuth",
-"oauth_clients_description": "Gestiona los clientes OAuth para tu organización",
+"oauth_clients_description": "Administra los clientes OAuth para tu organización",
 "create_oauth_client": "Crear cliente OAuth",
 "create_oauth_client_description": "Crea un nuevo cliente OAuth para integraciones de terceros",

---

1844-1845: Admin-only restriction strings — LGTM; ensure cross-locale coverage.
Spanish reads well and matches similar patterns. Verify these keys exist in all locales to avoid English fallbacks.

#!/bin/bash
set -euo pipefail
keys=(
  "only_admin_can_manage_directory_sync"
  "only_admin_can_manage_oauth_clients"
)
locales=$(fd -t d . apps/web/public/static/locales -d 1 | wc -l)
echo "Locales: $locales"
for k in "${keys[@]}"; do
  present=$(rg -l "\"$k\"" apps/web/public/static/locales/*/common.json | wc -l)
  echo "$k -> $present/$locales"
  if [ "$present" -ne "$locales" ]; then
    echo "Missing $k in:"
    for d in $(fd -t d . apps/web/public/static/locales -d 1); do
      f="$d/common.json"
      rg -q "\"$k\"" "$f" || echo "  - $f"
    done
  fi
done

---

3292-3292: PBAC workflows: unify wording (“configuración” singular; word order).
Apply consistent style in Spanish as previously suggested.

 "pbac_resource_workflow": "Flujos de trabajo",
 "pbac_desc_create_workflows": "Crear y configurar nuevos flujos de trabajo",
-"pbac_desc_view_workflows": "Ver flujos de trabajo existentes y sus configuraciones",
-"pbac_desc_update_workflows": "Editar y modificar configuraciones de flujos de trabajo",
-"pbac_desc_delete_workflows": "Eliminar flujos de trabajo del sistema",
-"pbac_desc_manage_workflows": "Acceso completo de gestión a todos los flujos de trabajo",
+"pbac_desc_view_workflows": "Ver flujos de trabajo existentes y su configuración",
+"pbac_desc_update_workflows": "Editar y modificar la configuración de los flujos de trabajo",
+"pbac_desc_delete_workflows": "Eliminar flujos de trabajo del sistema",
+"pbac_desc_manage_workflows": "Acceso de gestión completo a todos los flujos de trabajo",

Also applies to: 3325-3329

---

3324-3324: PBAC “manage … across org teams” — LGTM; ensure cross-locale presence.
Spanish scope “a través de los equipos de la organización” matches prior PBAC entries. Confirm these keys exist in all locales.

#!/bin/bash
keys=(
  "pbac_desc_manage_roles"
  "pbac_desc_manage_event_types"
  "pbac_desc_manage_teams"
  "pbac_desc_manage_bookings"
)
locales=$(fd -t d . apps/web/public/static/locales -d 1 | wc -l)
echo "Locales: $locales"
for k in "${keys[@]}"; do
  present=$(rg -l "\"$k\"" apps/web/public/static/locales/*/common.json | wc -l)
  echo "$k -> $present/$locales"
done

Also applies to: 3333-3333, 3341-3341, 3356-3356

---

3416-3416: Analytics/status keys — LGTM; verify cross-locale coverage to avoid fallbacks.
Spanish terms are correct. Ensure all locales define these keys.

#!/bin/bash
set -euo pipefail
keys=("failed_bookings" "stats" "booking_status")
locales=$(fd -t d . apps/web/public/static/locales -d 1 | wc -l)
echo "Locales: $locales"
for k in "${keys[@]}"; do
  present=$(rg -l "\"$k\"" apps/web/public/static/locales/*/common.json | wc -l)
  echo "$k -> $present/$locales"
  if [ "$present" -ne "$locales" ]; then
    echo "Missing $k in:"
    for d in $(fd -t d . apps/web/public/static/locales -d 1); do
      f="$d/common.json"
      rg -q "\"$k\"" "$f" || echo "  - $f"
    done
  fi
done

Also applies to: 3473-3475

---

3292-3292: Cross-locale coverage for PBAC workflow keys.
Spanish additions look good; ensure the following keys exist in all locales to avoid regressions:

• pbac_resource_workflow
• pbac_desc_create_workflows
• pbac_desc_view_workflows
• pbac_desc_update_workflows
• pbac_desc_delete_workflows
• pbac_desc_manage_workflows

#!/bin/bash
set -euo pipefail
keys=(
  "pbac_resource_workflow"
  "pbac_desc_create_workflows"
  "pbac_desc_view_workflows"
  "pbac_desc_update_workflows"
  "pbac_desc_delete_workflows"
  "pbac_desc_manage_workflows"
)
locales=$(fd -t d . apps/web/public/static/locales -d 1 | wc -l)
for k in "${keys[@]}"; do
  present=$(rg -l "\"$k\"" apps/web/public/static/locales/*/common.json | wc -l)
  echo "$k -> $present/$locales"
done

apps/web/public/static/locales/sk-SK/common.json (2)

123-123: Duplicate comment: "Round Robin" casing still inconsistent

The translation still uses capitalized "Round Robin" which is inconsistent with the lowercase usage elsewhere in the file. This matches the previous review feedback.

---

2255-2256: Duplicate comment: "headless" mistranslation persists

The translation still uses "headless smerovanie API" which maintains the English term "headless" but the description on line 2256 may still have the "bezstavové" (stateless) issue mentioned in previous reviews. The current text needs verification for technical accuracy.

apps/web/public/static/locales/de/common.json (1)

123-123: Previous review issue not addressed - standardize Round-Robin terminology

The same issue identified in the previous review remains unresolved. The translation should use consistent terminology and proper hyphenation.

Apply the previously suggested fix:

-  "round_robin_host_unavailable_for_booking": "Round Robin-Gastgeber ist für Buchungen nicht verfügbar.",
+  "round_robin_host_unavailable_for_booking": "Round-Robin-Veranstalter ist für Buchungen nicht verfügbar.",

apps/web/public/static/locales/vi/common.json (1)

879-879: Unify OAuth term with the rest of the file

This mixes English “OAuth client” with the chosen Vietnamese phrasing “Ứng dụng OAuth”.

-  "oauth_client_deletion_message": "Đã xóa thành công OAuth client",
+  "oauth_client_deletion_message": "Đã xóa thành công Ứng dụng OAuth",

To spot any remaining mixed terms in vi locale:

#!/bin/bash
rg -n --hidden '"oauth_client[^"]*"|OAuth client|Ứng dụng OAuth' apps/web/public/static/locales/vi/common.json -A 0 -B 0