Skip to content

Commit

Permalink
Fix spelling errors!!!
Browse files Browse the repository at this point in the history
  • Loading branch information
carols10cents committed Jan 7, 2017
1 parent a360c3d commit 52b7fcb
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion src/ch03-03-how-functions-work.md
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ Functions can also be defined to have *parameters*, which are special variables
that are part of a function's signature. When a function has parameters, we can
provide it with concrete values for those parameters. Technically, the concrete
values are called *arguments*, but in casual conversation people tend to use
the words "parameter" and "argument" interchangably for either the variables in
the words "parameter" and "argument" interchangeably for either the variables in
a function's definition or the concrete values passed in when you call a
function.

Expand Down
2 changes: 1 addition & 1 deletion src/ch10-03-lifetime-syntax.md
Original file line number Diff line number Diff line change
Expand Up @@ -172,7 +172,7 @@ Again, the lifetime names are declared in the angle brackets where generic type
parameters are declared, and this is because lifetimes are a form of generics.
In the examples above, `'a` and `'b` were concrete lifetimes: we knew about `r`
and `x` and how long they would live exactly. However, when we write a
function, we can't know beforehand exactly all of the valuess that it could be
function, we can't know beforehand exactly all of the values that it could be
called with and how long they will be valid for. We have to explain to Rust
what we expect the lifetime of the parameter to be (we'll learn about how to
know what you expect the lifetime to be in a bit). This is similar to writing a
Expand Down

0 comments on commit 52b7fcb

Please sign in to comment.