diff options
| author | Adrian Duong <adrian.duong@gmail.com> | 2020-10-13 09:08:32 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-10-13 12:08:32 -0400 |
| commit | 875ed1ed12b3a770e42ff0712b4e395c3e7f6315 (patch) | |
| tree | 098f39d190df962b733d3f7c2ab5eff1905a7306 /CONTRIBUTING.md | |
| parent | a8264cdab9245695b6f818166a45db8d2ff940db (diff) | |
docs: fix typo in CONTRIBUTING.md (#1772)
consistend -> consistent
Diffstat (limited to 'CONTRIBUTING.md')
| -rw-r--r-- | CONTRIBUTING.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8277afe87..987ee2f62 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -106,7 +106,7 @@ cargo fmt Testing is critical to making sure starship works as intended on systems big and small. Starship interfaces with many applications and system APIs when generating the prompt, so there's a lot of room for bugs to slip in. -Unit tests are written using the built-in Rust testing library in the same file as the implementation, as is traditionally done in Rust codebases. These tests can be run with `cargo test` and are run on GitHub as part of our GitHub Actions continuous integration to ensure consistend behavior. +Unit tests are written using the built-in Rust testing library in the same file as the implementation, as is traditionally done in Rust codebases. These tests can be run with `cargo test` and are run on GitHub as part of our GitHub Actions continuous integration to ensure consistent behavior. All tests that test the rendered output of a module should use `ModuleRenderer`. For Example: |