aboutsummaryrefslogtreecommitdiffhomepage
path: root/site/docs/external.md
diff options
context:
space:
mode:
authorGravatar Googler <noreply@google.com>2015-09-11 18:07:56 +0000
committerGravatar Lukacs Berki <lberki@google.com>2015-09-11 18:57:35 +0000
commitf64cd446d32dff5fe3019f9660a54cfe8bac53e6 (patch)
tree8996a1b140670e12df9bf89a1fa7d69666fb9069 /site/docs/external.md
parent676f39ae51536d2697627ddc352f4af4782fc893 (diff)
Fix minor typos in external.md
-- MOS_MIGRATED_REVID=102859533
Diffstat (limited to 'site/docs/external.md')
-rw-r--r--site/docs/external.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/site/docs/external.md b/site/docs/external.md
index de935d33be..6777cf60e9 100644
--- a/site/docs/external.md
+++ b/site/docs/external.md
@@ -107,7 +107,7 @@ For example, suppose you are working on a project, `my-project/`, and you want
to depend on targets from your coworker's project, `coworkers-project/`. Both
projects use Bazel, so you can add your coworker's project as an external
dependency and then use any targets your coworker has defined from your own
-BUILD files. You would add the following to `my\_project/WORKSPACE`:
+BUILD files. You would add the following to `my_project/WORKSPACE`:
```python
local_repository(
@@ -124,7 +124,7 @@ If your coworker has a target `//foo:bar`, your project can refer to it as
Rules prefixed with `new_` (e.g.,
[`new_local_repository`](http://bazel.io/docs/build-encyclopedia.html#new_local_repository)
and [`new_http_archive`](http://bazel.io/docs/build-encyclopedia.html#new_http_archive)
-allow you to create targets from projects that do not use Bazel.
+) allow you to create targets from projects that do not use Bazel.
For example, suppose you are working on a project, `my-project/`, and you want
to depend on your coworker's project, `coworkers-project/`. Your coworker's