Ask partial guides for their GUIDE_SECTIONS anchors

docs/TRANSLATING.md

@@ -31,10 +31,14 @@ A language is three things:
    Buttons are written `{{ui:key}}`, never by hand: the guide takes their names from your sentences, so they always
    match the interface. The pictures are shared: do not copy the English ones. A language may take a set of its own from its own interface with `scripts/guide-screenshots.mjs` (Arabic has, in `docs/guide/images/ar`); a picture it lacks is taken from English. The built pages of a guide (`apps/web/public/<guide folder>/`) are generated: add that folder to `.gitignore`, as the others are, so they are not committed.
 
+   A translated heading gets an id of its own, which the question marks in the program do not know yet. With each
+   chapter you translate, add the ids of its translated headings to `GUIDE_SECTIONS` in
+   `apps/web/src/lib/guideLinks.ts`, not only once the guide is complete: Hungarian, with one chapter still in
+   English, already has them. Without them a question mark opens the right chapter but not the right heading.
+
    Once every chapter is translated, a language may give them names of its own, as German, Dutch and Slovenian do
-   (`03-vormen.md`): add the names to `GUIDE_CHAPTERS` in `apps/web/src/lib/guideLinks.ts`, and the ids of the
-   translated headings to `GUIDE_SECTIONS`, so the question marks in the program land on the right page and
-   heading. The tests in `tests/unit/guide.test.ts` check both against the chapters.
+   (`03-vormen.md`): add the names to `GUIDE_CHAPTERS`. The tests in `tests/unit/guide.test.ts` check both against
+   the chapters.
 5. **Check.**
 
    ```