Minor documentation fixes. Make sidebar navigation look more consistent.

--
MOS_MIGRATED_REVID=98934930

1 files changed, 30 insertions, 29 deletions

diff --git a/site/docs/external.md b/site/docs/external.md
index 583aaabe87..e11f49fdd9 100644
--- a/site/docs/external.md
+++ b/site/docs/external.md
@@ -10,8 +10,8 @@ impractical for some version control systems and goes against how many existing
 projects are structured. Thus, Bazel has a system for pulling in dependencies
 from outside of the build root.
 
-External dependencies can be specified in a _WORKSPACE_ file in the build root.
-This _WORKSPACE_ file uses the same Python-like syntax of BUILD files, but
+External dependencies can be specified in a `WORKSPACE` file in the build root.
+This `WORKSPACE` file uses the same Python-like syntax of BUILD files, but
 allows a different set of rules. See the full list of rules that are allowed in
 the [Workspace](/docs/build-encyclopedia.html) list of rules in the Build
 Encyclopedia.
@@ -22,24 +22,25 @@ By default, external dependencies are fetched as needed during `bazel build`. If
 you would like to disable this behavior or prefetch dependencies, use
 [`bazel fetch`](http://bazel.io/docs/bazel-user-manual.html#fetch).
 
+<a name="transitive-dependencies"></a>
 ## Transitive dependencies
 
-Bazel only reads dependencies listed in your build root's _WORKSPACE_ file. This
-means that if your project (_A_) depends on another project (_B_) which list a
-dependency on project _C_ in its _WORKSPACE_ file, you'll have to add both _B_
-and _C_ to your project's _WORKSPACE_ file. This can balloon the _WORKSPACE_
-file size, but hopefully limits the chances of having one library include _C_
-at version 1.0 and another include _C_ at 2.0.
+Bazel only reads dependencies listed in your build root's `WORKSPACE` file. This
+means that if your project (`A`) depends on another project (`B`) which list a
+dependency on project `C` in its `WORKSPACE` file, you'll have to add both `B`
+and `C` to your project's `WORKSPACE` file. This can balloon the `WORKSPACE`
+file size, but hopefully limits the chances of having one library include `C`
+at version 1.0 and another include `C` at 2.0.
 
-Bazel provides a tool to help generate these expansive _WORKSPACE_ files, called
+Bazel provides a tool to help generate these expansive `WORKSPACE` files, called
 `generate_workspace`. Run the following to build the tool and see usage:
 
 ```
 bazel run src/main/java/com/google/devtools/build/workspace:generate_workspace
 ```
 
-You can either specify directories containing Bazel projects (i.e., _WORKSPACE_
-files) or Maven projects (i.e., _pom.xml_ files).  For example:
+You can either specify directories containing Bazel projects (i.e., `WORKSPACE`
+files) or Maven projects (i.e., `pom.xml` files).  For example:
 
 ```bash
 $ bazel run src/main/java/com/google/devtools/build/workspace:generate_workspace -- \
@@ -51,17 +52,17 @@ Wrote:
 /tmp/1437415510621-0/2015-07-20-14-05-10.BUILD
 ```
 
-The _WORKSPACE_ file contains the transitive dependencies of given projects. The
-_BUILD_ file contains a single target, `transitive-deps`, that contains all of
+The `WORKSPACE` file contains the transitive dependencies of given projects. The
+`BUILD` file contains a single target, `transitive-deps`, that contains all of
 the dependencies. You can copy these files to your project and add
-`transitive-deps` as a dependency of your `java_` targets in _BUILD_ files.
+`transitive-deps` as a dependency of your `java_` targets in `BUILD` files.
 
 If you specify multiple Bazel or Maven projects, they will all be combined into
-one _WORKSPACE_ file (e.g., if the Bazel project depends on junit and the Maven
+one `WORKSPACE` file (e.g., if the Bazel project depends on junit and the Maven
 project also depends on junit, junit will only appear once as a dependency in
 the output).
 
-You may wish to curate the generated _WORKSPACE_ file to ensure it is using the
+You may wish to curate the generated `WORKSPACE` file to ensure it is using the
 correct version of each dependency. If several different versions of an artifact
 are requested (by different libraries that depend on it), then
 `generate_workspace` chooses a version and annotates the `maven_jar` with the
@@ -82,7 +83,7 @@ maven_jar(
 This indicates that `org.springframework:spring:2.5.6`, `javax.mail:mail:1.4`,
 `httpunit:httpunit:1.6`, `org.springframework:spring-support:2.0.2`, and
 `org.slf4j:nlog4j:1.2.24` all depend on javax.activation. However, two of these
-libraries wanted version 1.1 and three of them wanted 1.0.2. The _WORkSPACE_
+libraries wanted version 1.1 and three of them wanted 1.0.2. The `WORkSPACE`
 file is using version 1.1, but that might not be the right version to use.
 
 You may also want to break `transitive-deps` into smaller targets, as it is
@@ -101,11 +102,11 @@ use
 or [`http_archive`](http://bazel.io/docs/build-encyclopedia.html#http_archive)
 to symlink it from the local filesystem or download it (respectively).
 
-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
+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,10 +125,10 @@ Rules prefixed with `new_` (e.g.,
 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.
 
-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
+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
 project uses `make` to build, but you'd like to depend on one of the .so files
-it generates. To do so, add the following to _my\_project/WORKSPACE_:
+it generates. To do so, add the following to `my_project/WORKSPACE`:
 
 ```python
 new_local_repository(
@@ -154,18 +155,18 @@ files.
 # Caching of external dependencies
 
 Bazel caches external dependencies and only re-downloads or updates them when
-the _WORKSPACE_ file changes. If the _WORKSPACE_ file does not change, Bazel
+the `WORKSPACE` file changes. If the `WORKSPACE` file does not change, Bazel
 assumes that the external dependencies have not changed, either. This can cause
 unexpected results, especially with local repositories.
 
-For instance, in the example above, suppose that _my-project/_ has a target that
+For instance, in the example above, suppose that `my-project/` has a target that
 depends on `@coworkers-project//:a`, which you build. Then you change to
-_coworkers-project/_ and pull the latest updates to their library, which changes
-the behavior of `@coworkers-project//:a`. If you go back to _my-project/_ and
+`coworkers-project/` and pull the latest updates to their library, which changes
+the behavior of `@coworkers-project//:a`. If you go back to `my-project/` and
 build your target again, it will assume `@coworkers-project//:a` is already
 up-to-date and reuse the cached library (instead of realizing that the sources
 have changed and, thus, rebuilding).
 
 To avoid this situation, prefer remote repositories to local ones and do not
-manually change the files in _\[output\_base\]/external_. If you change a file
-in _\[output\_base\]/external_, rerun `bazel fetch ...` to update the cache.
+manually change the files in `[output_base]/external`. If you change a file
+in `[output_base]/external`, rerun `bazel fetch ...` to update the cache.