README.md (1)

42-42: Relative link works, but consider forward-compatibility.

docs/console-command.md is correct today, yet if the README is ever rendered inside the docs folder (e.g. a docs site generator), the link will break. Using an absolute GitHub URL or ./docs/console-command.md avoids that edge case.

docs/console-command.md (1)

13-14: Minor grammar / punctuation.

Missing period at the end of the description and “sub-directories” could be clearer.

-| `--recursive`     | `-r`     | Search for translation files recursively in subdirectories
+| `--recursive`     | `-r`     | Searches for translation files recursively in sub-directories. |

docs/validators.md (4)

228-230: Remove duplicated heading text.

HtmlTagValidator is repeated in the heading (## [...]HtmlTagValidator).
It renders oddly and breaks anchor generation in most Markdown engines.

-## [`HtmlTagValidator`](../src/Validator/HtmlTagValidator.php)HtmlTagValidator
+## [`HtmlTagValidator`](../src/Validator/HtmlTagValidator.php)

---

158-160: Grammar: “a whitespace” not “an whitespace”.

-    - Warning the translation key `contact` has an whitespace only value
+    - Warning the translation key `contact` has a whitespace-only value

---

285-287: Minor wording tweak for subject–verb agreement.

-If not configured, it try to detect the most common pattern …
+If not configured, it tries to detect the most common pattern …

---

340-350: YAML example overrides custom_pattern three times.

YAML only keeps the last key, so earlier regex examples are silently discarded. Use a list instead to avoid misleading readers:

validator-settings:
  KeyNamingConventionValidator:
    custom_pattern:
      - '/^[a-z0-9]+$/'
      - '/^app\.[a-z][a-z0-9_]*$/'
      - '/^[a-z][a-z0-9_]{0,29}$/'   # Max 30 characters

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

CONTRIBUTING.md (1)

14-16: Repository URL & directory name look correct – no further action needed.

The corrected clone URL and directory name now match the actual repository. Nice catch!

docs/config-file.md (1)

59-60: Class reference rename is consistent – good update.

All JSON/YAML examples now reference XliffSchemaValidator, matching the actual class name.
No issues spotted.

Also applies to: 68-69

docs/validators.md (1)

126-128: Malformed fenced-code block still breaks rendering

The closing delimiter has four back-ticks instead of three, so everything afterwards is rendered as code. Same issue was raised previously.

-```bash
-composer validate-translations ./translations --skip "MoveElevator\\ComposerTranslationValidator\\Validator\\DuplicateValuesValidator"
-````
+```bash
+composer validate-translations ./translations --skip "MoveElevator\\ComposerTranslationValidator\\Validator\\DuplicateValuesValidator"
+```

docs/validators.md (2)

321-324: Incorrect heading & missing fenced-code language

1. ### #Console Output has an extra #.
2. The following code block lacks a language tag, triggering MD040.

-### #Console Output
-```
+#### Console Output
+```text

---

298-300: Minor grammar fix – “it try” → “it tries”.

-If not configured, it try to detect the most common pattern used in your files and warns about inconsistencies.
+If not configured, it tries to detect the most common pattern used in your files and warns about inconsistencies.

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

docs/file-detector.md (2)

241-246: Reminder: config key rename may still be a breaking change

The docs exclusively use file-detectors: (hyphen). Unless the PHP config loader now aliases the former file_detectors key, existing user configs will break silently – this was already raised in a previous review.

Please either:

1. add backward-compatibility in the loader (file_detectors ➜ file-detectors), or
2. highlight this as a breaking change in the upgrade guide and throw a clear exception if the old key is encountered.

---

251-254: Same concern for JSON snippet

Same as above – ensure code supports both keys or document the breaking change.

docs/validators.md (3)

15-18: Grammar & redundancy in IMPORTANT call-out

“Others validators return just return a warning” – duplicated verb and wrong plural.

- - ![Warning](... ) Others validators return just return a warning. Therefore, just a warning indicates that the validation succeeded, but there are potential issues that should be addressed.
+ - ![warning](... ) Other validators only return a warning. A warning indicates that the validation succeeded, but there are potential issues that should be addressed.

---

213-218: Add language hint to console output blocks (MD040)

Markdown-lint flags these fenced blocks because no language is specified.
Use text (or console) to silence the warning and improve rendering.

-```
+```text

Repeat for similar blocks below.

---

533-540: Missing language spec on fenced block (MD040)

Add text to the opening backticks of this console output to satisfy linter and provide syntax highlighting.

-```
+```text

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

docs/validators.md (3)

50-59: Add a language identifier to console-output blocks

markdownlint flags these fences (MD040). Adding bash or console avoids the warning and enables syntax highlighting.

Example fix:

-```
+```bash
 # console output …

Do this for all four blocks highlighted above.  



Also applies to: 214-222, 321-331, 535-545

---

`299-300`: **Minor grammar tweak** — “it tries”  

```diff
-If not configured, it try to detect the most common pattern
+If not configured, it tries to detect the most common pattern

---

173-174: Article & hyphenation

-    - Warning the translation key `contact` has an whitespace only value
+    - Warning the translation key `contact` has a whitespace-only value

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