Skip to content

docs: fix a typo in MAINTAINING.md #4711

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 10, 2022
Merged

docs: fix a typo in MAINTAINING.md #4711

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/MAINTAINING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ Current maintainers:
- @TeffenEllis
- @jsjoeio

Occassionally, other Coder employees may step in time to time to assist with code-server.
Occasionally, other Coder employees may step in time to time to assist with code-server.

### Onboarding

Expand Down Expand Up @@ -202,7 +202,7 @@ This is currently automated with the release process.

We publish code-server on Homebrew [here](https://github.com/Homebrew/homebrew-core/blob/master/Formula/code-server.rb).

This is currently automated with the release process (but may fail occassionally). If it does, run this locally:
This is currently automated with the release process (but may fail occasionally). If it does, run this locally:

```shell
# Replace VERSION with version
Expand Down Expand Up @@ -231,7 +231,7 @@ Ideally, our fork stays as close to upstream as possible. See the differences be

Our testing structure is laid out under our [Contributing docs](https://coder.com/docs/code-server/latest/CONTRIBUTING#test).

We hope to eventually hit 100% test converage with our unit tests, and maybe one day our scripts (coverage not tracked currently).
We hope to eventually hit 100% test coverage with our unit tests, and maybe one day our scripts (coverage not tracked currently).

If you're ever looking to add more tests, here are a few ways to get started:

Expand Down