reference docs: fix missing link from heading

[sarahsanders-docker]

- What I did

• When testing Hugo updates locally, I got an error from the CLI reference: https://docs.docker.com/reference/cli/docker/swarm/init/
• Added name="configure-node-healthcheck-frequency---dispatcher-heartbeat" to heading

If this is not the correct way to fix this, let me know!

- A picture of a cute animal (not mandatory but encouraged)
My cat Bean basking in sunlight

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 59.16%. Comparing base (1dcfd23) to head (f977b92).
Report is 2 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #5841   +/-   ##
=======================================
  Coverage   59.16%   59.16%           
=======================================
  Files         352      352           
  Lines       29567    29567           
=======================================
  Hits        17493    17493           
  Misses      11092    11092           
  Partials      982      982           

[thaJeztah]

Oh! And looks like the commit message is missing a "DCO" sign off line; hold on, I have a canned reply for thad (I'm on my phone 🥹)

[thaJeztah]

Thank you for contributing! It appears your commit message is missing a DCO sign-off,
causing the DCO check to fail.

We require all commit messages to have a Signed-off-by line with your name
and e-mail (see "Sign your work"
in the CONTRIBUTING.md in this repository), which looks something like:

Signed-off-by: YourFirsName YourLastName <yourname@example.org>

There is no need to open a new pull request, but to fix this (and make CI pass),
you need to amend the commit(s) in this pull request, and "force push" the amended
commit.

Unfortunately, it's not possible to do so through GitHub's web UI, so this needs
to be done through the git commandline.

You can find some instructions in the output of the DCO check (which can be found
in the "checks" tab on this pull request), as well as in the Moby contributing guide.

Steps to do so "roughly" come down to:

1. Set your name and e-mail in git's configuration:

   git config --global user.name "YourFirstName YourLastName"
   git config --global user.email "yourname@example.org"

   (Make sure to use your real name (not your GitHub username/handle) and e-mail)

2. Clone your fork locally

3. Check out the branch associated with this pull request

4. Sign-off and amend the existing commit(s)

   git commit --amend --no-edit --signoff

   If your pull request contains multiple commits, either squash the commits (if
   needed) or sign-off each individual commit.

5. Force push your branch to GitHub (using the --force or --force-with-lease flags) to update the pull request.

Sorry for the hassle (I wish GitHub would make this a bit easier to do), and let me know if you need help or more detailed instructions!

[sarahsanders-docker]

All good @thaJeztah that is on me!!

[thaJeztah]

LGTM

looks like the markdown had to be regenerated, so I did a quick fix-up of that; thanks!