From 00ebcc7837dc251145afa292f8c7945aeed5a988 Mon Sep 17 00:00:00 2001 From: Jeremie Knuesel Date: Wed, 26 Aug 2026 17:02:06 +0200 Subject: [PATCH] Fix confusing wording about cargo update --- src/ch02-00-guessing-game-tutorial.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/ch02-00-guessing-game-tutorial.md b/src/ch02-00-guessing-game-tutorial.md index f118eb5455..3b5b59492b 100644 --- a/src/ch02-00-guessing-game-tutorial.md +++ b/src/ch02-00-guessing-game-tutorial.md @@ -473,7 +473,7 @@ checked into source control with the rest of the code in your project. When you _do_ want to update a crate, Cargo provides the command `update`, which will ignore the _Cargo.lock_ file and figure out all the latest versions that fit your specifications in _Cargo.toml_. Cargo will then write those -versions to the _Cargo.lock_ file. Otherwise, by default, Cargo will only look +versions to the _Cargo.lock_ file. Given our specification `0.10.1`, Cargo will only look for versions greater than 0.10.1 and less than 0.11.0. If the `rand` crate has released the two new versions 0.10.2 and 0.999.0, you would see the following if you ran `cargo update`: