Fix typos in style guide

[xszabo3]

Adds an escaped ` character before the external link and removes doubled colons.
Discussed in #1302 (comment) , and #1368 (comment)

[ansible-documentation-bot]

Thanks for your Ansible docs contribution! We talk about Ansible documentation on matrix at #docs:ansible.im and on libera IRC at #ansible-docs if you ever want to join us and chat about the docs! We meet there on Tuesdays (see the Ansible calendar) and welcome additions to our weekly agenda items - scroll down to find the upcoming agenda and add a comment to put something new on that agenda.

[oraNod]

Looks good to me in the rendered docs from the PR preview: https://ansible--1368.org.readthedocs.build/projects/ansible-core/en/1368/dev_guide/style_guide/index.html

[patchback]

Backport to stable-2.15: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 186be84 on top of patchback/backports/stable-2.15/186be843998a0d3436671bff7e1867edaefc5c0f/pr-1368

Backporting merged PR #1368 into devel

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/ansible/ansible-documentation.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/stable-2.15/186be843998a0d3436671bff7e1867edaefc5c0f/pr-1368 upstream/stable-2.15

4. Now, cherry-pick PR Fix typos in style guide #1368 contents into that branch:

   $ git cherry-pick -x 186be843998a0d3436671bff7e1867edaefc5c0f

   If it'll yell at you with something like fatal: Commit 186be843998a0d3436671bff7e1867edaefc5c0f is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x 186be843998a0d3436671bff7e1867edaefc5c0f

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Fix typos in style guide #1368 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-2.15/186be843998a0d3436671bff7e1867edaefc5c0f/pr-1368

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[samccann]

Thanks @xszabo3 for fixing both items in this PR!

[patchback]

Backport to stable-2.16: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 186be84 on top of patchback/backports/stable-2.16/186be843998a0d3436671bff7e1867edaefc5c0f/pr-1368

Backporting merged PR #1368 into devel

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/ansible/ansible-documentation.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/stable-2.16/186be843998a0d3436671bff7e1867edaefc5c0f/pr-1368 upstream/stable-2.16

4. Now, cherry-pick PR Fix typos in style guide #1368 contents into that branch:

   $ git cherry-pick -x 186be843998a0d3436671bff7e1867edaefc5c0f

   If it'll yell at you with something like fatal: Commit 186be843998a0d3436671bff7e1867edaefc5c0f is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x 186be843998a0d3436671bff7e1867edaefc5c0f

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Fix typos in style guide #1368 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-2.16/186be843998a0d3436671bff7e1867edaefc5c0f/pr-1368

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[patchback]

Backport to stable-2.17: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-2.17/186be843998a0d3436671bff7e1867edaefc5c0f/pr-1368

Backported as #1384

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[xszabo3]

Created a PR for both backports (#1385 and #1386), I hope they are correct...

[oraNod]

@xszabo3 Thanks for the fix and for the backports!