Update runbooks based on downstream wording

[machadovilaca]

What this PR does / why we need it:

There is some wording on downstream runbooks that we can move to the upstream runbooks to make them more similar

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Checklist

This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

• Design: A design document was considered and is present (link) or not required
• PR: The PR description is expressive enough and will help future contributors
• Code: Write code that humans can understand and Keep it simple
• Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
• Upgrade: Impact of this change on upgrade flows was considered and addressed if required
• Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
• Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
• Community: Announcement to kubevirt-dev was considered

Release note:

Update runbooks wording

[machadovilaca]

/cc @ousleyp

[kubevirt-bot]

@machadovilaca: GitHub didn't allow me to request PR reviews from the following users: ousleyp.

Note that only kubevirt members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @ousleyp

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[ousleyp]

This mostly LGTM, but there are a couple of minor issues (one of them repeats in several files). Thanks!

[ousleyp]

/lgtm

[sradco]

/lgtm