Update homepage.ejs (#11164)

# Checklist for submitter

If some of the following don't apply, delete the relevant line.

- [ ] Changes file added for user-visible changes in `changes/` or
`orbit/changes/`.
See [Changes
files](https://fleetdm.com/docs/contributing/committing-changes#changes-files)
for more information.
- [ ] Documented any API changes (docs/Using-Fleet/REST-API.md or
docs/Contributing/API-for-contributors.md)
- [ ] Documented any permissions changes
- [ ] Input data is properly validated, `SELECT *` is avoided, SQL
injection is prevented (using placeholders for values in statements)
- [ ] Added support on fleet's osquery simulator `cmd/osquery-perf` for
new osquery data ingestion features.
- [ ] Added/updated tests
- [ ] Manual QA for all new/changed functionality
  - For Orbit and Fleet Desktop changes:
- [ ] Manual QA must be performed in the three main OSs, macOS, Windows
and Linux.
- [ ] Auto-update manual QA, from released version of component to new
version (see [tools/tuf/test](../tools/tuf/test/README.md)).

website/views/pages/homepage.ejs

@@ -15,7 +15,7 @@
           <div purpose="hero-quote" class="d-flex flex-row align-items-between justify-content-center justify-content-md-start">
             <div><img alt="An opening quotation mark" src="/images/homepage-hero-quote-mark.svg"></div>
             <div>
-              <p purpose="quote">We wanted an open-source way to take advantage of MDM that is easy to integrate with Puppet in our configuration-as-code environment. Fleet is the obvious, and really the ony, choice.</p>
+              <p purpose="quote">We wanted an open-source way to take advantage of MDM that is easy to integrate with Puppet in our configuration-as-code environment. Fleet is the obvious, and really the only, choice.</p>
               <p><span class="font-weight-bold">Platform Engineering Manager</span><br>A leading online games company</p>
             </div>
           </div>