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

Typos and grammar #920

Merged
merged 2 commits into from
Jan 17, 2025
Merged

Typos and grammar #920

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
81de0eb
Fix typos and grammar
cbachhuber Jan 17, 2025
bd3e503
Update BUILD
cbachhuber Jan 17, 2025
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 examples/rich_structure/BUILD
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ load("@rules_pkg//pkg:zip.bzl", "pkg_zip")
#
# This example shows various techniques for specifying how your source tree
# transforms into the installation tree. As such, it favors using a lot of
# distict features, at the expense of uniformity.
# distinct features, at the expense of uniformity.

pkg_files(
name = "share_doc",
Expand Down
2 changes: 1 addition & 1 deletion examples/rich_structure/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,5 +46,5 @@ For macOS, it would be mostly the same, but files under `usr/share/foo` would
move to `Library/Foo`.

To emulate reality better, the source tree is organized in a way that is
convenient for the developers. This example illustrates techniques create
convenient for the developers. This example illustrates techniques to create
the desired final structure.