aboutsummaryrefslogtreecommitdiffhomepage
path: root/site
diff options
context:
space:
mode:
authorGravatar Florian Weikert <fwe@google.com>2016-06-30 14:08:04 +0000
committerGravatar Lukacs Berki <lberki@google.com>2016-07-01 07:07:26 +0000
commit5e546d55993d5e5d37ad7500c71b3083f0f85c0b (patch)
tree300f8dfad9a1e1f5c6aff4ba12d6f406374df4d2 /site
parent13e4036d15a5aa814ab529ea6040c3267390880b (diff)
Minor fixes to the Bazel documentation.
-- MOS_MIGRATED_REVID=126298962
Diffstat (limited to 'site')
-rw-r--r--site/docs/bazel-user-manual.html2
-rw-r--r--site/docs/build-ref.html16
-rw-r--r--site/docs/query.html2
3 files changed, 7 insertions, 13 deletions
diff --git a/site/docs/bazel-user-manual.html b/site/docs/bazel-user-manual.html
index 102487f227..66b4a1229b 100644
--- a/site/docs/bazel-user-manual.html
+++ b/site/docs/bazel-user-manual.html
@@ -267,7 +267,7 @@ the <code class='flag'>--bazelrc=<var>file</var></code> option, and the
</p>
<p>
Bazel prints progress messages during
- the <a href='#phases'>execution phase</a> of the build, showing the
+ the <a href='#execution-phase'>execution phase</a> of the build, showing the
current build step (compiler, linker, etc.) that is being started,
and the number of completed over total number of build actions. As the
build starts the number of total actions will often increase as Bazel
diff --git a/site/docs/build-ref.html b/site/docs/build-ref.html
index 5069354174..6bb3e11926 100644
--- a/site/docs/build-ref.html
+++ b/site/docs/build-ref.html
@@ -2,10 +2,10 @@
layout: documentation
title: BUILD files
---
-<h1>Bazel: Build files and Terminology</h1>
+<h1>Bazel: Build Files and Terminology</h1>
<p>
- This document provides an overview of sourte tree layout and terminology used
- in Bazel.
+ This document provides an overview of the source tree layout and the
+ terminology used in Bazel.
</p>
<h2>Table of Contents</h2>
@@ -88,16 +88,10 @@ src/my/app/data/input.txt
src/my/app/tests/BUILD
src/my/app/tests/test.cc
</pre>
-<p>
- there are two packages, <code>my/app</code>,
- and <code>my/app/tests</code>, a subpackage;
- <code>my/app/data</code> is not a package, but a directory belonging to package
- <code>my/app</code>.
-</p>
<h3 id="targets">Targets</h3>
<p>
- A package is a container. The elements of a package are called
+ A package is a container. The elements of a package are called
<i>targets</i>. Most targets are one of two principal kinds, <i>files</i>
and <i>rules</i>. Additionally, there is another kind of target,
<a href="be/functions.html#package_group">package groups</a>,
@@ -636,7 +630,7 @@ testdata/input.txt
"target graph" or "build dependency graph", and is the domain over
which the
- <a href="query.html">Bazel Query tool</a></li>.
+ <a href="query.html">Bazel Query tool</a></li>
operates.
</p>
diff --git a/site/docs/query.html b/site/docs/query.html
index 7a424fa431..a5068c8eef 100644
--- a/site/docs/query.html
+++ b/site/docs/query.html
@@ -154,7 +154,7 @@ title: Query Language
Bazel adds additional <em>implicit</em> dependencies to rules. For example
every Java rule implicitly depends on the JavaBuilder. Implicit dependencies
are established using attributes that start with <code>$</code> and they
- cannot overridden in BUILD files.
+ cannot be overridden in BUILD files.
</p>