[Wave 3] Medium — TR mirror: docs/usermanuals/en/evaluation/

Wave 3 · 1 finding(s) in 1 fix package(s). Mirror drift across small document pairs in this directory.

Findings

DOC-TR14-001 (TR mirror, Medium) — TR mirror drift in docs/usermanuals/en/evaluation/trend-tracking.md: There is no per-harm-category (S5, S10, ...) trend and no benchmark trend
severity Medium
Where. EN docs/usermanuals/en/evaluation/trend-tracking.md:34 · TR docs/usermanuals/en/evaluation/trend-tracking.md:34
English text. There is no per-harm-category (S5, S10, ...) trend and no benchmark trend
Turkish text. Görev-kategorisi başına (S5, S10, ...) trend yoktur ve benchmark trend'i de yoktur
Which is correct. EN. 'Görev-kategorisi' (task category) mistranslates 'per-harm-category'; S5/S10 are Llama Guard harm categories, and the TR phrasing makes the sentence collide with 'benchmark trend'.
Proposed correction (Turkish text for the -tr page). 'Zarar kategorisi başına (S5, S10, ...) trend yoktur ve benchmark trend'i de yoktur — forgelm/benchmark.py hiç trend dosyası yazmaz; yalnızca güvenlik yolu yazar.'

Done when

Every finding above is fixed or closed with a reason (tick it here).
Code fixes carry a test; doc fixes update the Turkish mirror in the same PR.

_{Found by the October 2026 ForgeLM code and documentation review against commit cab2947. Code links point at that commit; line numbers may have moved since. Finding IDs (CR-…, DOC-…, TECH-…) are stable references for this backlog.}

Where to start

Thanks for taking a look. Please confirm the issue is unassigned and comment before starting so work does not overlap.

Start with these files on development:

Replace the task-category wording with harm-category wording consistent with the English S5/S10 sentence. Preserve code literals and the page structure.

Coordinate with #884: the same document pair is touched.

Run the focused tests:

pytest tests/test_safety_advanced.py --no-cov

Run these guards/checks as applicable to the changed files:

ruff format --check tests/test_safety_advanced.py
ruff check tests/test_safety_advanced.py
python3 tools/check_bilingual_parity.py --strict
python3 tools/check_bilingual_code_blocks.py --strict
python3 tools/check_anchor_resolution.py --strict
python3 tools/check_tr_links_prefer_mirror.py --strict
python3 tools/check_usermanual_self_contained.py --strict
python3 tools/check_usermanual_schema_drift.py --strict

If user-facing documentation changes, update the existing Turkish mirror in the same PR; keep commands, code and terminal output in English and structurally aligned. English-only contributor standards need no new mirror.

Open the PR against development with Fixes #640 once every finding is resolved or explicitly closed with a reason; use Refs #640 for partial work and list the resolved finding IDs.

I'm removing good first issue here and marking this help wanted: it needs natural Turkish written or reviewed by a native or near-native speaker. docs/standards/localization.md does not accept unreviewed machine translation (see its "No machine-translation output" rule), so please only claim this issue if that describes you, and say in the PR who reviewed the Turkish text.

Navigation Menu

Repository navigation

[Wave 3] Medium — TR mirror: docs/usermanuals/en/evaluation/ #640

Findings

Done when

Where to start

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[Wave 3] Medium — TR mirror: docs/usermanuals/en/evaluation/ #640

Description

Findings

Done when

Activity

cemililik commented on Oct 11, 2026

Where to start

cemililik commented on Oct 15, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions