aboutsummaryrefslogtreecommitdiffhomepage
path: root/site/docs/bazel-overview.md
diff options
context:
space:
mode:
authorGravatar Roller, David <droller47@gmail.com>2017-11-28 07:59:41 -0800
committerGravatar Copybara-Service <copybara-piper@google.com>2017-11-28 08:01:13 -0800
commit0dcf425c840b9b263951b31a6d48965435b206f1 (patch)
tree9e1dda30dd2c874d489568ccb5df436434c9b1f4 /site/docs/bazel-overview.md
parent74f86dc0a9416cea1ee1057ec4e08b1e7bd9ea39 (diff)
Grammar fix. bazel-overview.md
Removed duplicated word in bazel-overview.md docs Closes #4183. PiperOrigin-RevId: 177161035
Diffstat (limited to 'site/docs/bazel-overview.md')
-rw-r--r--site/docs/bazel-overview.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/site/docs/bazel-overview.md b/site/docs/bazel-overview.md
index dfd2f2b453..2e03f0c10d 100644
--- a/site/docs/bazel-overview.md
+++ b/site/docs/bazel-overview.md
@@ -61,7 +61,7 @@ To build or test a project with Bazel, you typically do the following:
which is a directory where Bazel looks for build inputs and `BUILD` files,
and where it stores build outputs.
-3. **Write a `BUILD` file**, which which tells Bazel what to build and how to
+3. **Write a `BUILD` file**, which tells Bazel what to build and how to
build it.
You write your `BUILD` file by declaring build targets using an abstract