Normalize usage of "workspace", "workspace directory" and "build root" in

documentation. Replaces instances of "build root" with "workspace directory"
as appropriate.

Makes the following changes:

- /docs/build-ref.html: Adds definition of workspace
- /docs/external.md: Replaces "build root" terminology with "workspace"
- /docs/getting-started.md: Adds link to workspace definition
- /docs/bazel-user-manual.html: Adds link to workspace definition

--
MOS_MIGRATED_REVID=101885966

1 files changed, 11 insertions, 10 deletions

diff --git a/site/docs/external.md b/site/docs/external.md
index e11f49fdd9..34ffe1b9a2 100644
--- a/site/docs/external.md
+++ b/site/docs/external.md
@@ -5,15 +5,16 @@ layout: documentation
 # Working with external dependencies
 
 Bazel is designed to have absolutely everything needed for a build, from source
-code to libraries to compilers, under one directory (the build root). This is
-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
-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
+code to libraries to compilers, under one directory (the workspace directory).
+This is 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 workspace.
+
+External dependencies can be specified in a `WORKSPACE` file in the
+[workspace directory](/docs/build-ref.html#workspaces). 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#workspace) list of rules in the Build
 Encyclopedia.
 
 ## Fetching dependencies
@@ -25,7 +26,7 @@ you would like to disable this behavior or prefetch dependencies, use
 <a name="transitive-dependencies"></a>
 ## Transitive dependencies
 
-Bazel only reads dependencies listed in your build root's `WORKSPACE` file. This
+Bazel only reads dependencies listed in your `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`