Remove reference to missing figures.
Fixes
@@ -98,23 +98,6 @@ src/my/app/tests/test.cc
but they are far less numerous.
</p>
-<div style='margin:auto; text-align: center'>
-<div class='graphviz dot'><!--
-digraph G1 {
- node [shape=ellipse];
- Target -> Rule;
- Rule -> cc_library
- Rule -> java_test
- Rule -> "..."
- Target -> File;
- File -> Source;
- File -> Generated;
- Target -> "Package group"
-}
---></div>
-<p><i>Hierarchy of targets.</i></p>
-</div>
-
<p>
Files are further divided into two kinds.
<i>Source files</i> are usually written by the efforts of people,
@@ -418,39 +401,6 @@ testdata/input.txt
dependency graph.
</p>
-<p>
- The figure below represents an example fragment of the build
- dependency graph, and illustrates: files (circles) and rules
- (boxes); dependencies from generated files to rules; dependencies
- from rules to files, and from rules to other rules. Conventionally,
- dependency arrows are represented as pointing from a target towards
- its prerequisites.
-</p>
-
-<div style="margin:auto; text-align:center">
-<div class='graphviz dot'><!--
-digraph G1 {
- graph [rankdir=BT];
- node [fontname="Courier-Bold",fontsize=10,fontcolor="#006000"];
-
- node [shape=box,label="rule"]; r1; r2;
-
- node [shape=circle,width=.4,fixedsize=1];
- node [label="in"]; s1; s2; s3; s4;
- node [label="out"]; o1; o2;
-
- r1 -> s1;
- r1 -> s2;
- r1 -> s3;
- r2 -> s4;
- r2 -> r1;
- o1 -> r1;
- o2 -> r2;
-}
---></div>
-<p><i>Source files, rules, and generated files.</i></p>
-</div>
-
<p>
This directed acyclic graph over targets is called the
"target graph" or "build dependency graph", and is the domain over
