docs(usermanuals): name the real KTO columns on the alignment overview page (#972)

Fixes #965

The KTO bullet on the Alignment overview page named the fields `(prompt,
response, good?)`; the loader requires `prompt`, `completion` and a
boolean `label`. Both the English page and the Turkish mirror (same
line, same structure, only the field names and the true/false
explanation changed) now say `(prompt, completion, label)`. A `###
Fixed` entry is added under `[Unreleased]` in `CHANGELOG.md`.

Checks run, all passing with `--strict`: `check_bilingual_parity`,
`check_bilingual_code_blocks`, `check_anchor_resolution`,
`check_tr_links_prefer_mirror`, `check_usermanual_self_contained`. Docs
only, no code changed. The Turkish wording is mine and could use a
native read.

## Summary by Sourcery

Correct the documented KTO dataset fields to match the loader’s expected
prompt, completion, and label schema.

Bug Fixes:
- Correct the KTO field names and boolean label guidance on the English
and Turkish alignment overview pages.

Documentation:
- Document the KTO alignment overview correction in the unreleased
changelog.

Signed-off-by: Venius24 <WonderRebirth@mail.ru>
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>

Author: Venius24

CHANGELOG.md

@@ -59,6 +59,9 @@ All notable changes to ForgeLM are documented here.
 
 ### Fixed
 
+- Fix the KTO bullet on the Alignment overview user-manual page (English and Turkish): it named the
+  fields `(prompt, response, good?)`, but the KTO loader reads `prompt`, `completion` and a boolean
+  `label` (#965).
 - Make the site's code comments readable: `--code-comment` was `#6a6f80`, 3.8:1 on the dark code
   surface, below the 4.5:1 AA floor, and it colours code comments, terminal and code-block title bars,
   language tags, copy buttons and the wizard's YAML pane header and comment lines. It is now `#8f96a8`,

docs/usermanuals/en/concepts/alignment-overview.md

@@ -53,7 +53,7 @@ After SFT, the model produces well-formatted outputs but quality varies — some
 The differences:
 - **DPO** — learns from `(chosen, rejected)` pairs against a reference model. Best-studied, most stable.
 - **SimPO** — same as DPO but skips the reference model. Lower memory, slightly less stable.
-- **KTO** — learns from binary `(prompt, response, good?)` signals. Use when you only have thumbs-up/down feedback.
+- **KTO** — learns from binary `(prompt, completion, label)` rows, where `label` is `true` for a desirable response and `false` for an undesirable one. Use when you only have thumbs-up/down feedback.
 - **ORPO** — combines SFT and preference loss in a single pass. Faster wall-clock; less flexible than separate stages.
 
 ### Problem 3: Reasoning

docs/usermanuals/tr/concepts/alignment-overview.md

@@ -53,7 +53,7 @@ SFT'den sonra model iyi formatta çıktı üretir ama kalite değişken — baze
 Farklar:
 - **DPO** — referans modele karşı `(chosen, rejected)` çiftlerinden öğrenir. En çok çalışılmış, en kararlı.
 - **SimPO** — DPO ile aynı ama referans modeli atlar. Daha az bellek, biraz daha az kararlılık.
-- **KTO** — ikili `(prompt, response, iyi mi?)` sinyallerinden öğrenir. Sadece thumbs-up/down geri bildiriminiz varsa kullanın.
+- **KTO** — ikili `(prompt, completion, label)` satırlarından öğrenir; `label`, istenen yanıt için `true`, istenmeyen yanıt için `false` olur. Sadece thumbs-up/down geri bildiriminiz varsa kullanın.
 - **ORPO** — SFT ve tercih kaybını tek geçişte birleştirir. Daha hızlı wall-clock; ayrı aşamalardan daha az esneklik.
 
 ### Problem 3: Akıl yürütme