Skip to content

Commit 704f11d

Browse files
froydnjalexcrichton
authored andcommitted
correct a few spelling mistakes in the tutorial
1 parent 5d36005 commit 704f11d

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/doc/tutorial.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -469,7 +469,7 @@ fn signum(x: int) -> int {
469469

470470
Rust's `match` construct is a generalized, cleaned-up version of C's
471471
`switch` construct. You provide it with a value and a number of
472-
*arms*, each labelled with a pattern, and the code compares the value
472+
*arms*, each labeled with a pattern, and the code compares the value
473473
against each pattern in order until one matches. The matching pattern
474474
executes its corresponding arm.
475475

@@ -2524,7 +2524,7 @@ of the components of types. By design, trait objects don't know the exact type
25242524
of their contents and so the compiler cannot reason about those properties.
25252525

25262526
You can instruct the compiler, however, that the contents of a trait object must
2527-
acribe to a particular bound with a trailing colon (`:`). These are examples of
2527+
ascribe to a particular bound with a trailing colon (`:`). These are examples of
25282528
valid types:
25292529

25302530
~~~rust
@@ -2579,7 +2579,7 @@ This is a silly way to compute the radius of a circle
25792579

25802580
In type-parameterized functions,
25812581
methods of the supertrait may be called on values of subtrait-bound type parameters.
2582-
Refering to the previous example of `trait Circle : Shape`:
2582+
Referring to the previous example of `trait Circle : Shape`:
25832583

25842584
~~~
25852585
# trait Shape { fn area(&self) -> f64; }

0 commit comments

Comments
 (0)