markdown anchor links with _ need to be stripped when converting from wiki markdown

[malcomio]

The IDs on https://docs.check-spelling.dev/Configuration.html are inconsistent, so some of the anchor links in the table of contents don't work

[jsoref]

Oh. Ouch. Sadly the links are from a different flavor of markdown (specifically GitHub's wiki markdown).

I'll have to figure out if I can easily fix the script that converts them.

[jsoref]

I think I fixed this issue by adding this line:

check-spelling-docs/process-md.pl

Line 7 in 8ca6b96

$a =~ s/_//g;

and changing this line (to remove _ from the pattern):

check-spelling-docs/process-md.pl

Line 8 in 8ca6b96

$a =~ tr/[A-Z ]/[a-z\-]/;

I'm sorry that it's impossible to review the workflow runs / push log -- this repository is an amalgamation of a couple of things:

• a wiki (where I evolve content changes using one flavor of GFM)
• some scripts to massage from that GFM to the GFM used by gh-pages (🤯)
• workflows to check-spelling (eating some 🐶 food)

Because the primary history is the wiki (and the fact that I don't like merges), the changes applied by the massaging script, the workflows, and the generated content don't actually survive (I could retain distinct commits for each evolution of the massaging scripts and the workflows, but I don't seem them as particularly valuable, and they can be recovered w/ effort).

github has changes how gh-pages works somewhat recently, so it's possible for me to actually drop the commit that contains the generated content and move it strictly to a github workflow that's responsible for publishing gh-pages, but I haven't had the time to do that (I also don't know much about that status of the gh-pages workflow stuff, it could be a beta feature 🤷 )...

Anyway, if you could give https://docs.check-spelling.dev/ a quick check to confirm that the content works as you expect, that'd be great.

Testing I've done:

1. In https://docs.check-spelling.dev/Configuration.html#workflow-parameters, clicking
   GITHUB_TOKEN works
2. In https://docs.check-spelling.dev/Event-descriptions.html, clicking unrecognized-spelling works.