Fix typo in configuration comment

[dirkmueller]

The files are supposed to be in /etc/crio/crio.conf.d/ not
/etc/crio/conf.d/. Also cleanup wording a bit.

Why is this PR needed?

Does it fix an issue? addresses a business case?

add a description and link to the issue if one exists.

Fixes #

Reminder: Add the "fixes bsc#XXXX" to the title of the commit so that it will
appear in the changelog.

What does this PR do?

please include a brief "management" technical overview (details are in the code)

Anything else a reviewer needs to know?

Special test cases, manual steps, links to resources or anything else that could be helpful to the reviewer.

Info for QA

This is info for QA so that they can validate this. This is mandatory if this PR fixes a bug.
If this is a new feature, a good description in "What does this PR do" may be enough.

Related info

Info that can be relevant for QA:

• link to other PRs that should be merged together
• link to packages that should be released together
• upstream issues

Status BEFORE applying the patch

The README generated in skuba init process step pointed to a file / directory location that does not exist.

Status AFTER applying the patch

The README generated in skuba init process step points to an existing directory.

Docs

Docs do not need to be updated because they do not carry this typo.

Merge restrictions

(Please do not edit this)

We are in v4-maintenance phase, so we will restrict what can be merged to prevent unexpected surprises:

What can be merged (merge criteria):
    2 approvals:
        1 developer: code is fine
        1 QA: QA is fine
    there is a PR for updating documentation (or a statement that this is not needed)

[suseclee]

LGTM

[suseclee]

Sorry. @jenting I accidentally clicked re-request review circle on the top right.

[fgerling]

From a QA perspective, this looks reasonable. Thank you.