From d7db5129d2c6b9b256e762b8a4a15bcd15927228 Mon Sep 17 00:00:00 2001
From: Rahul Rao <63695122+rahulrao0209@users.noreply.github.com>
Date: Fri, 7 Jul 2023 23:45:42 +0530
Subject: [PATCH] Update
 ch07-03-paths-for-referring-to-an-item-in-the-module-tree.md

Editing what I think is a minor typo. The binary crate should be calling code within the library crate (instead of with 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 c8fb3247ff..3d6d890c13 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 the most functionality that the package
 > provides, because the library crate’s code can be shared.
 >