docs typo, missing a space

[dwgrth]

works either way, but it annoyed me so I fixed it

[ansible-documentation-bot]

Thanks for your Ansible docs contribution! We talk about Ansible documentation on Matrix at #docs:ansible.im if you ever want to join us and chat about the docs! We meet on Matrix every Tuesday. See the Ansible calendar for meeting details. We welcome additions to our weekly agenda items too. You can add the dawgs-meeting tag to a forum topic to bring it up at the next meeting.

[oraNod]

Nice one @dwgrth Thanks for taking the time to fix this!

[patchback]

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

❌ Failed to cleanly apply 071f461 on top of patchback/backports/stable-2.15/071f4614808683f8afde22d16f2b97d9e83a9d8b/pr-2004

Backporting merged PR #2004 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/071f4614808683f8afde22d16f2b97d9e83a9d8b/pr-2004 upstream/stable-2.15

4. Now, cherry-pick PR docs typo, missing a space #2004 contents into that branch:

   $ git cherry-pick -x 071f4614808683f8afde22d16f2b97d9e83a9d8b

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

   $ git cherry-pick -m1 -x 071f4614808683f8afde22d16f2b97d9e83a9d8b

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR docs typo, missing a space #2004 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-2.15/071f4614808683f8afde22d16f2b97d9e83a9d8b/pr-2004

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.16: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-2.16/071f4614808683f8afde22d16f2b97d9e83a9d8b/pr-2004

Backported as #2028

🤖 @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/071f4614808683f8afde22d16f2b97d9e83a9d8b/pr-2004

Backported as #2030

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

[patchback]

Backport to stable-2.18: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-2.18/071f4614808683f8afde22d16f2b97d9e83a9d8b/pr-2004

Backported as #2031

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