From 08d3496982aaa197b8db8bc885f9cd82d87a6747 Mon Sep 17 00:00:00 2001
From: Matt Nield <64328730+matthewjnield@users.noreply.github.com>
Date: Sun, 8 Oct 2023 01:52:28 -0400
Subject: [PATCH 1/2] Fix typo in Chapter 7 Section 3

Fix typo in Chapter 7 Section 3, changing "benefit from the most functionality" to "benefit from most of the functionality"
---
 ...ch07-03-paths-for-referring-to-an-item-in-the-module-tree.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/ch07-03-paths-for-referring-to-an-item-in-the-module-tree.md b/src/ch07-03-paths-for-referring-to-an-item-in-the-module-tree.md
index c8fb3247ff..e2e627eb75 100644
--- a/src/ch07-03-paths-for-referring-to-an-item-in-the-module-tree.md
+++ b/src/ch07-03-paths-for-referring-to-an-item-in-the-module-tree.md
@@ -185,7 +185,7 @@ interested in this topic, see [The Rust API Guidelines][api-guidelines].
 > package name by default. Typically, packages with this pattern of containing
 > both a library and a binary crate will have just enough code in the binary
 > crate to start an executable that calls code with the library crate. This
-> lets other projects benefit from the most functionality that the package
+> lets other projects benefit from most of the functionality that the package
 > provides, because the library crate’s code can be shared.
 >
 > The module tree should be defined in *src/lib.rs*. Then, any public items can

From 1402554da88bfaf3fe1cc33d18a5974286287408 Mon Sep 17 00:00:00 2001
From: Matt Nield <64328730+matthewjnield@users.noreply.github.com>
Date: Sun, 8 Oct 2023 02:02:46 -0400
Subject: [PATCH 2/2] Fix typo in Chapter 7 Section 3

Fix typo in Chapter 7 Section 3, changing "start an executable that calls code with the library crate." to "start an executable that calls code within the library crate."
---
 ...ch07-03-paths-for-referring-to-an-item-in-the-module-tree.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/ch07-03-paths-for-referring-to-an-item-in-the-module-tree.md b/src/ch07-03-paths-for-referring-to-an-item-in-the-module-tree.md
index e2e627eb75..85fc247376 100644
--- a/src/ch07-03-paths-for-referring-to-an-item-in-the-module-tree.md
+++ b/src/ch07-03-paths-for-referring-to-an-item-in-the-module-tree.md
@@ -184,7 +184,7 @@ interested in this topic, see [The Rust API Guidelines][api-guidelines].
 > well as a *src/lib.rs* library crate root, and both crates will have the
 > package name by default. Typically, packages with this pattern of containing
 > both a library and a binary crate will have just enough code in the binary
-> crate to start an executable that calls code with the library crate. This
+> crate to start an executable that calls code within the library crate. This
 > lets other projects benefit from most of the functionality that the package
 > provides, because the library crate’s code can be shared.
 >