about summary refs log tree commit diff
diff options
context:
space:
mode:
authorTang Chenglong <ideami@outlook.com>2016-03-16 23:45:28 +0800
committerTang Chenglong <ideami@outlook.com>2016-03-16 23:45:28 +0800
commit01d76099f261abe50342d9261fad618c5323274b (patch)
tree4223e472cd94c3f2c2c935ede9f4c85e159f0cfa
parente68d40edf49496e8d7a9ab03d75c9de2096446c5 (diff)
downloadrust-01d76099f261abe50342d9261fad618c5323274b.tar.gz
rust-01d76099f261abe50342d9261fad618c5323274b.zip
docs: One typo
I think it's a mistake of spelling.
-rw-r--r--src/doc/book/guessing-game.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/doc/book/guessing-game.md b/src/doc/book/guessing-game.md
index e071bfdf8bc..590c7e84819 100644
--- a/src/doc/book/guessing-game.md
+++ b/src/doc/book/guessing-game.md
@@ -912,7 +912,7 @@ returned by `parse()`, this is an `enum`  like `Ordering`, but in this case,
 each variant has some data associated with it: `Ok` is a success, and `Err` is a
 failure. Each contains more information: the successfully parsed integer, or an
 error type. In this case, we `match` on `Ok(num)`, which sets the name `num` to
-the unwrapped `Ok` value (ythe integer), and then we  return it on the
+the unwrapped `Ok` value (the integer), and then we  return it on the
 right-hand side. In the `Err` case, we don’t care what kind of error it is, so
 we just use the catch all `_` instead of a name. This catches everything that
 isn't `Ok`, and `continue` lets us move to the next iteration of the loop; in