chore(pr-updates): updated the files based on pr feedback

Author: bp-cos

.github/workflows/review.yml

@@ -3,9 +3,7 @@ name: Require at least one approval
 
 on:
   pull_request:
-    types: [opened, reopened, ready_for_review, synchronize]
-  pull_request_review:
-    types: [submitted, edited, dismissed]
+    types: [opened, reopened, ready_for_review, synchronize, edited]
 
 jobs:
   check-approval:

docs/i18n.md

@@ -18,13 +18,13 @@ The OSF Angular project uses [`@ngx-translate/core`](https://github.com/ngx-tran
 
 All strings rendered to users—whether in HTML templates or dynamically via Angular components—must be sourced from the centralized i18n JSON files located in:
 
-**IMPORTANT**
-The OSF application must maintain 100% translation coverage, as it is a requirement of grant funding that supports a globally distributed user base.
-
 ```
 src/app/i18n/
 ```
 
+**IMPORTANT**
+The OSF application must maintain 100% translation coverage, as it is a requirement of grant funding that supports a globally distributed user base.
+
 ## Integration: `@ngx-translate/core`
 
 To support multilingual content, the following module is included globally:
@@ -74,7 +74,7 @@ The structure should be **namespaced by feature or component** for maintainabili
 {
   "home": {
     "title": "Welcome to OSF",
-    "subtTtle": "Your research. Your control."
+    "subTitle": "Your research. Your control."
   },
   "login": {
     "email": "Email Address",
@@ -85,11 +85,15 @@ The structure should be **namespaced by feature or component** for maintainabili
 
 Avoid deeply nested keys, and always use consistent camel-casing and key naming for reuse and clarity.
 
+**Note**
+
+The `common section` in the en.json file stores frequently used phrases to prevent one-off duplicate translations.
+
 ## Source of Truth: `en.json` Only
 
 All translation key additions and updates must be made **only** in the `src/app/i18n/en.json` file.
 
-> Other language files (e.g., `fr.json`, `es.json`) must **not** be modified manually. These translations will be handle internally by the OSF Angular team.
+> Other language files (e.g., `fr.json`, `es.json`) must **not** be modified by non-OSF engineers. These translations will be handle internally by the OSF Angular team.
 
 This ensures consistency across translations and prevents desynchronization between supported languages.