Minor documentation content fixes

[spollard]

PR Checklist

Please check if your PR fulfills the following requirements:

• [ ] Tests for the changes have been added (for bug fixes / features)
• [x] Docs have been added / updated (for bug fixes / features)
• [ ] If applicable, have a visual design approval

PR Type

What kind of change does this PR introduce?

• [ ] Bugfix
• [ ] Feature
• [ ] Code style update (formatting, local variables)
• [ ] Refactoring (no functional changes, no api changes)
• [ ] Build related changes
• [ ] CI related changes
• [x] Documentation content changes
• [ ] clarity.design website / infrastructure changes
• [ ] Other... Please describe:

What is the current behavior?

Doc sentences don't sound right.

Issue Number: N/A

What is the new behavior?

Doc sentences do sound right.

Does this PR introduce a breaking change?

• [ ] Yes
• [x] No

Other information

[vmwclabot]

@spollard, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <john.doe@email.org> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit f5337cd30a440cee685f315ecee4bfe0b26fdaff must be signed by public@stephentpollard.com

[ashleyryan]

Closing in favor of https://github.com/vmware/clarity/pull/6699