Update checklist-for-pourover-creation.md

Author: aphillips

docs/checklist-for-pourover-creation.md

@@ -21,9 +21,9 @@ Being a compendium of tasks needed to get a clean pour over of the spec.
    - make a ## section for the message.abnf and insert with abnf backticks
    - make a ### section of message.json and insert with json backticks
    - altogether remove the why_mf_next link
-- check the toc. The tool does a good job, but you might need to make `messageabnf` and `messagejson`
-  into `message-abnf` and `message-json` respectively. If you need to generate a TOC
-  try https://bitdowntoc.derlin.ch/
+- check the toc. @srl295 made a change so that `message.json` and `message.abnf` linkify automagically (as `#messagejson` and `#messageabnf`)
+  so there should be no need to touch the autogenerated stuff.
+  If you need to generate a TOC by hand (unlikely) try https://bitdowntoc.derlin.ch/
   but the tr-archive tool generates a TOC under dist, so use that preferably
 
 - use `base make-tr-archive.sh` to generate