Skip to content

Commit 38d81ba

Browse files
committed
rollup merge of #20478: SeanTAllen/master
Number of rustc calls would depending on various circumstances. Two is misleading.
2 parents eee6a57 + 0536986 commit 38d81ba

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/doc/guide.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -355,7 +355,7 @@ Hello, world!
355355
Bam! We build our project with `cargo build`, and run it with
356356
`./target/hello_world`. This hasn't bought us a whole lot over our simple use
357357
of `rustc`, but think about the future: when our project has more than one
358-
file, we would need to call `rustc` twice, and pass it a bunch of options to
358+
file, we would need to call `rustc` more than once, and pass it a bunch of options to
359359
tell it to build everything together. With Cargo, as our project grows, we can
360360
just `cargo build` and it'll work the right way.
361361

@@ -977,7 +977,7 @@ fn main() {
977977
```
978978

979979
Even though Rust functions can only return one value, a tuple _is_ one value,
980-
that happens to be made up of two. You can also see in this example how you
980+
that happens to be made up of more than one value. You can also see in this example how you
981981
can destructure a pattern returned by a function, as well.
982982

983983
Tuples are a very simple data structure, and so are not often what you want.

0 commit comments

Comments
 (0)