fix typos

[Adam-D-Lewis]

Reference Issues or PRs

What does this implement/fix?

Put a x in the boxes that apply

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds a feature)
• [ ] Breaking change (fix or feature that would cause existing features not to work as expected)
• [x] Documentation Update
• [ ] Code style update (formatting, renaming)
• [ ] Refactoring (no functional changes, no API changes)
• [ ] Build related changes
• [ ] Other (please describe):

Testing

• [ ] Did you test the pull request locally?
• [ ] Did you add new tests?

Documentation

Access-centered content checklist

Text styling

• [ ] The content is written with plain language (where relevant).
• [ ] If there are headers, they use the proper header tags (with only one level-one header: H1 or # in markdown).
• [ ] All links describe where they link to (for example, check the Nebari website).
• [ ] This content adheres to the Nebari style guides.

Non-text content

• [ ] All content is represented as text (for example, images need alt text, and videos need captions or descriptive transcripts).
• [ ] If there are emojis, there are not more than three in a row.
• [ ] Don't use flashing GIFs or videos.
• [ ] If the content were to be read as plain text, it still makes sense, and no information is missing.

Any other comments?

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
jhub-apps	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 5, 2024 9:07pm
jhub-apps-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 5, 2024 9:07pm

[jbouder]

Is this PR still needed? I see you added the changes to another PR as well

[Adam-D-Lewis]

Yeah, I figured this PR would be uncontroversial while the other might need to be adjusted.