Update general and existing glossary terms

[kprosise]

The glossary was cleaned up a bit, new terms added, as well as links to related topic pages.

Links to glossary terms were added in a few areas, with a focus on the 'getting started' sections.

This is the first of a handful of PR commits meant to update the glossary.

QA Steps: Ran build, examined output. No issues spotted. Linkcheck failed due to unrelated issue which has been identified and will be updated separately.

This commit addresses FFTK-3008

PR Template and Checklist

Please complete as much as possible to speed up the reviewing process.

Readiness and adding reviewers as appropriate is required.

All PRs should be reviewed by a technical writer/documentation team and a peer.
If effecting customers—which is a majority of content changes—a member of Customer Success must also review.

Readiness

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

Overview

Why merge this PR? What does it solve?

Checklist

• 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

More PRs to follow. Glossary options within Sphinx are pretty limited, so making it look better would require theme editing.

[doanac]

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