@@ -27,7 +27,7 @@ Sound good? Let's go!
27
27
# Installing Rust
28
28
29
29
The first step to using Rust is to install it! There are a number of ways to
30
- install Rust, but the easiest is to use the the ` rustup ` script. If you're on
30
+ install Rust, but the easiest is to use the ` rustup ` script. If you're on
31
31
Linux or a Mac, all you need to do is this (note that you don't need to type
32
32
in the ` $ ` s, they just indicate the start of each command):
33
33
@@ -120,7 +120,7 @@ to make a projects directory in my home directory, and keep all my projects
120
120
there. Rust does not care where your code lives.
121
121
122
122
This actually leads to one other concern we should address: this tutorial will
123
- assume that you have basic familiarity with the command- line. Rust does not
123
+ assume that you have basic familiarity with the command line. Rust does not
124
124
require that you know a whole ton about the command line, but until the
125
125
language is in a more finished state, IDE support is spotty. Rust makes no
126
126
specific demands on your editing tooling, or where your code lives.
@@ -452,7 +452,7 @@ what you need, so it's not verboten.
452
452
453
453
Let's get back to bindings. Rust variable bindings have one more aspect that
454
454
differs from other languages: bindings are required to be initialized with a
455
- value before you're allowed to use it . If we try...
455
+ value before you're allowed to use them . If we try...
456
456
457
457
``` {ignore}
458
458
let x;
@@ -2281,7 +2281,7 @@ change that by adding loops!
2281
2281
2282
2282
## Looping
2283
2283
2284
- As we already discussed, the ` loop ` key word gives us an infinite loop. So
2284
+ As we already discussed, the ` loop ` keyword gives us an infinite loop. So
2285
2285
let's add that in:
2286
2286
2287
2287
``` {rust,no_run}
@@ -4099,7 +4099,7 @@ fn inverse(x: f64) -> Result<f64, String> {
4099
4099
```
4100
4100
4101
4101
We don't want to take the inverse of zero, so we check to make sure that we
4102
- weren't passed one . If we weren't , then we return an ` Err ` , with a message. If
4102
+ weren't passed zero . If we were , then we return an ` Err ` , with a message. If
4103
4103
it's okay, we return an ` Ok ` , with the answer.
4104
4104
4105
4105
Why does this matter? Well, remember how ` match ` does exhaustive matches?
0 commit comments