diff options
| author | Joe Lencioni <joe.lencioni@gmail.com> | 2022-06-11 09:57:59 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-06-11 10:57:59 -0400 |
| commit | 93a7c6f16b49e1513e8b95df328116fcee125e64 (patch) | |
| tree | a89ff98e1c4dd7bb0a81e34840e89e43269cb304 | |
| parent | 3ab57446213bd24595674b3946a355df5e1e4d64 (diff) | |
| download | bazelbuild-rules_pkg-93a7c6f16b49e1513e8b95df328116fcee125e64.tar.gz | |
Fix typo "someon" -> "someone" (#594)
| -rw-r--r-- | examples/where_is_my_output/README.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/examples/where_is_my_output/README.md b/examples/where_is_my_output/README.md index 9b4e16d..4000676 100644 --- a/examples/where_is_my_output/README.md +++ b/examples/where_is_my_output/README.md @@ -5,7 +5,7 @@ Most of the time, Bazel users do not need to know the path to the artifacts created for any given target. A notable exception is for users of packaging rules. You typically create an RPM or Debian packaged file for the explicit -purpose of taking it from your machine and giving it to someon else. +purpose of taking it from your machine and giving it to someone else. Users often create scripts to push `bazel build` outputs to other places and need to know the path to those outputs. This can be a challenge for rules which |