docs: fix typo

[jenting]

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
• The title of the PR states what changed and the related issues number (used for the release note).
• The title of the PR conforms to the Toolchain Guide
• I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
• I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
• Does this PR require documentation updates?
• I've updated documentation as required by this PR.
• Optional. My organization is added to USERS.md.
• I have signed off all my commits as required by DCO
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My build is green (troubleshooting builds).
• My new feature complies with the feature status guidelines.
• I have added a brief description of why this PR is necessary and/or what this PR solves.

Please see Contribution FAQs if you have questions about your pull-request.

[crenshaw-dev]

Thanks, @jenting!

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (d3ec7f8) 49.56% compared to head (efe41a9) 49.57%.

Additional details and impacted files

@@           Coverage Diff           @@
##           master   #13967   +/-   ##
=======================================
  Coverage   49.56%   49.57%           
=======================================
  Files         256      256           
  Lines       43920    43920           
=======================================
+ Hits        21770    21773    +3     
+ Misses      19987    19985    -2     
+ Partials     2163     2162    -1     

see 1 file with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.