about summary refs log tree commit diff
path: root/src/doc/rustc-dev-guide
diff options
context:
space:
mode:
authorNiko Matsakis <niko@alum.mit.edu>2018-08-31 12:49:16 -0400
committerNiko Matsakis <niko@alum.mit.edu>2018-09-11 12:02:57 -0400
commit1dcc3df66dc19b2f0b0844ecd5223b4fb83ad9cf (patch)
treea1107fecc5ca699cd191a6d807c3a393f31ae02c /src/doc/rustc-dev-guide
parentb8abcaa6583a87da2e245ff6921a8e34d4caa290 (diff)
downloadrust-1dcc3df66dc19b2f0b0844ecd5223b4fb83ad9cf.tar.gz
rust-1dcc3df66dc19b2f0b0844ecd5223b4fb83ad9cf.zip
fix typos
Diffstat (limited to 'src/doc/rustc-dev-guide')
-rw-r--r--src/doc/rustc-dev-guide/src/how-to-build-and-run.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/doc/rustc-dev-guide/src/how-to-build-and-run.md b/src/doc/rustc-dev-guide/src/how-to-build-and-run.md
index f6c26ddf197..aef5b66b8e8 100644
--- a/src/doc/rustc-dev-guide/src/how-to-build-and-run.md
+++ b/src/doc/rustc-dev-guide/src/how-to-build-and-run.md
@@ -179,10 +179,10 @@ compiler.
 when doing simple refactorings, is to run `./x.py check`
 continuously. Here you are just checking that the compiler can
 **build**, but often that is all you need (e.g., when renaming a
-method). You can then run `./x.py build` when you acqtually need to
+method). You can then run `./x.py build` when you actually need to
 run tests.
 
-In fact, it is eomtimes useful to put off tests even when you are not
+In fact, it is sometimes useful to put off tests even when you are not
 100% sure the code will work. You can then keep building up
 refactoring commits and only run the tests at some later time. You can
 then use `git bisect` to track down **precisely** which commit caused