summaryrefslogtreecommitdiff
path: root/docs/contributing
diff options
context:
space:
mode:
authorVille Skyttä <ville.skytta@iki.fi>2021-08-16 23:46:26 +0300
committerVille Skyttä <ville.skytta@iki.fi>2021-08-16 23:46:26 +0300
commitdff5e9105320ae39cbce4f375ef33803d0f3a593 (patch)
tree218a6bbb5f80be138d2eb9a12225ef073c7e7c6b /docs/contributing
parentb0007e703a67d0939a4fd123fe594ee04a7a03e5 (diff)
downloadisort-dff5e9105320ae39cbce4f375ef33803d0f3a593.tar.gz
Spelling fixes
Diffstat (limited to 'docs/contributing')
-rw-r--r--docs/contributing/1.-contributing-guide.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/contributing/1.-contributing-guide.md b/docs/contributing/1.-contributing-guide.md
index 2ba296f8..ee29ec7c 100644
--- a/docs/contributing/1.-contributing-guide.md
+++ b/docs/contributing/1.-contributing-guide.md
@@ -49,7 +49,7 @@ A local test cycle might look like the following:
3. if #2 fails, debug, save, and goto #1
* `docker run -it isort bash` will get you into the failed environment
* `docker run -v $(git rev-parse --show-toplevel):/isort` will make changes made in the docker environment persist on your local checkout.
- **TIP**: combine both to get an interacive docker shell that loads changes made locally, even after build, to quickly rerun that pesky failing test
+ **TIP**: combine both to get an interactive docker shell that loads changes made locally, even after build, to quickly rerun that pesky failing test
4. `./scripts/docker.sh`
5. if #4 fails, debug, save and goto #1; you may need to specify a different `--build-arg VERSION=$VER`
6. congrats! you are probably ready to push a contribution