Skip to content

Commit 57b53fd

Browse files
authoredDec 28, 2016
Use "an" before "i32"
(Minor typo fix.) Since the word `i32` starts with a vowel, the indefinite article should use "an", not "a" \[[1](http://www.dictionary.com/browse/an)\]. (Previously there was one instance of "an i32" and two instances of "a i32", so at least something is wrong!) Since I believe that "an" is the correct form, I aligned everything with that.
1 parent 02b22ec commit 57b53fd

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed
 

‎src/doc/book/closures.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -283,7 +283,7 @@ fn call_with_one<F>(some_closure: F) -> i32
283283
# some_closure(1) }
284284
```
285285

286-
We take one parameter, and it has the type `F`. We also return a `i32`. This part
286+
We take one parameter, and it has the type `F`. We also return an `i32`. This part
287287
isn’t interesting. The next part is:
288288

289289
```rust
@@ -293,7 +293,7 @@ isn’t interesting. The next part is:
293293
```
294294

295295
Because `Fn` is a trait, we can use it as a bound for our generic type. In
296-
this case, our closure takes a `i32` as an argument and returns an `i32`, and
296+
this case, our closure takes an `i32` as an argument and returns an `i32`, and
297297
so the generic bound we use is `Fn(i32) -> i32`.
298298

299299
There’s one other key point here: because we’re bounding a generic with a

0 commit comments

Comments
 (0)