(QEMU) Clarification on ENV VAR Usage

[camilamacedo86]

Readiness

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

Overview

The note provided before the command might lead users to believe that the ENV VAR will automatically be utilized by QEMU during its execution. This can be misleading, especially for those unfamiliar with QEMU or the outlined solution. Personally, the necessity of exporting this variable wasn't clear to me until I reviewed the 'targets' section.

So I would like to suggest the following changes:

Before this PR:

Suggested changes in this 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 dddf5cf are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2354/docs/artifacts/html/index.html

[kprosise]

Looks good, thanks!