(Setting up your PKI): (Nit)Clarify command usage

[camilamacedo86]

Readiness

• Merge (pending reviews)
• Merge after date or event
• Draft

Overview

• Just add the commands in the code block to make it easier to copy and paste
• Clarify that the view should be executed after the first command to check the outcome.

See the proposal changes:

(Before PR)

(After PR)

Checklist

Optional. Add a 'x' to steps taken.
You can fill this out after opening the PR. "Did I..."

• Run spelling and grammar check, preferably with linter.
• Avoid changing any header associated with a link/reference.
• Step through instructions (or ask someone to do so).
• Review for wordiness
• Match tone and style of page/section.
• Run make linkcheck.
• View HTML in a browser to check rendering.
• Use semantic newlines.
• follow best practices for commits.
  • Descriptive title written in the imperative.
  • Include brief overview of QA steps taken.
  • Mention any related issues numbers.
  • End message with sign off/DCO line (-s, --signoff).
  • Sign commit with your gpg key (-S, --gpg-sign).
  • Squash commits if needed.
• Request PR review by a technical writer and at least one peer.

Comments

Any thing else that a maintainer/reviewer should know.
This could include potential issues, rational for approach, etc.

[doanac]

Docs for c36c7d4 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2357/docs/artifacts/html/index.html