Apply suggestions from code review

Co-authored-by: Felipe R. Monteiro <rms.felipe@gmail.com>

README.md

@@ -17,10 +17,10 @@ The goal is to have a verified [Rust standard library](https://doc.rust-lang.org
 
 For that we are launching a contest that includes a series of challenges that focus on verifying
 memory safety and a subset of undefined behaviors in the Rust standard library.
-Each challenge describes the goal, the success criteria, and whether it has a financial award to awarded upon its
+Each challenge describes the goal, the success criteria, and whether it has a financial award to be awarded upon its
 successful completion.
 
-See [our book](https://model-checking.github.io/verify-rust-std/intro.html) more details on the challenge rules
+See [our book](https://model-checking.github.io/verify-rust-std/intro.html) for more details on the challenge rules
 and the list of existing challenges.
 
 We welcome everyone to participate!

doc/src/intro.md

@@ -9,7 +9,7 @@ given Rust standard library implementation is safe.
 Verifying the Rust libraries is difficult because:
 1. Lack of a specification,
 2. Lack of an existing verification mechanism in the Rust ecosystem,
-3. Lhe large size of the verification problem,
+3. The large size of the verification problem,
 4. The unknowns of scalable verification.
 
 Given the magnitude and scope of the effort, we believe this should be a community owned effort.