Clarify that release builds go in the release dir, not another subdir
authorCarol (Nichols || Goulding) <carol.nichols@gmail.com>
Fri, 13 May 2016 23:42:40 +0000 (19:42 -0400)
committerCarol (Nichols || Goulding) <carol.nichols@gmail.com>
Fri, 13 May 2016 23:42:40 +0000 (19:42 -0400)
Good call @steveklabnik! This matches much more nicely with the contrast
to `target/debug`.

src/doc/guide.md

index 4afc3de6474a693fb68d5073dc92852057ef1a7a..d2150928fea23ec70d30b998acd9c8e5f73543d3 100644 (file)
@@ -104,7 +104,7 @@ Once you’re ready for release, you can use `cargo build --release` to compile
 class="s1">   Compiling</span> hello_world v0.1.0 (file:///path/to/project/hello_world)</code></pre>
 
 `cargo build --release` puts the resulting binary in
-`target/release/hello_world` instead of `target/debug`.
+`target/release` instead of `target/debug`.
 
 # Working on an existing Cargo project