Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix a wording typo in ch07 #3694

Merged
merged 2 commits into from
Apr 2, 2024
Merged

Fix a wording typo in ch07 #3694

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d7db512
Update ch07-03-paths-for-referring-to-an-item-in-the-module-tree.md
rahulrao0209 Jul 7, 2023
ff5c65d
Merge branch 'main' into patch-1
chriskrycho Apr 2, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/ch07-03-paths-for-referring-to-an-item-in-the-module-tree.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
>
Expand Down