Skip to content

Commit 77fd7c3

Browse files
committed
more typo fixes
1 parent 96bf1ee commit 77fd7c3

File tree

4 files changed

+28
-31
lines changed

4 files changed

+28
-31
lines changed

source/ch_graphtheory.ptx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,11 +4,11 @@
44
<title>Graph Theory</title>
55
<introduction>
66
<p>
7-
Graph theory has existed as a branch of mathematics for only a short time; the first book on graph theory was published less than 100 years ago. While the first problem related to what we now call graph theory dates back to 1735, it has been the advent of computers that has shown that the subject's true utility. It is a subject with simple beauty and surprising depth. Many of the main areas of graph theory can be understood with almost no mathematical prerequisites, yet new research in the subject generate hundreds of peer-reviewed research papers each year.
7+
Graph theory has existed as a branch of mathematics for only a short time; the first book on graph theory was published less than 100 years ago. While the first problem related to what we now call graph theory dates back to 1735, it has been the advent of computers that has shown the subject's true utility. It is a subject with simple beauty and surprising depth. Many of the main areas of graph theory can be understood with almost no mathematical prerequisites, yet new research in the subject generates hundreds of peer-reviewed research papers each year.
88
</p>
99

1010
<p>
11-
In this chapter we will explore just a few of the ways you can use graphs and their properties to solve problems that show up in computer science, mathematics, and almost every other applied science.
11+
In this chapter, we will explore just a few of the ways you can use graphs and their properties to solve problems that show up in computer science, mathematics, and almost every other applied science.
1212
</p>
1313
</introduction>
1414

source/exercises/gt-trees.ptx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -487,7 +487,7 @@
487487
<exercise>
488488
<statement>
489489
<p>
490-
Prove that every connected graph which is not itself a tree must have at last three
490+
Prove that every connected graph which is not itself a tree must have at least three
491491
different
492492
(although possibly isomorphic)
493493
spanning trees.

source/sec_gt-intro.ptx

Lines changed: 15 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -94,15 +94,15 @@
9494
<p>
9595
Graph Theory is a relatively new area of mathematics,
9696
first studied by the super famous mathematician Leonhard Euler in 1735.
97-
Since then it has blossomed in to a powerful tool used in nearly every branch of science and is currently an active area of mathematics research.
97+
Since then it has blossomed into a powerful tool used in nearly every branch of science and is currently an active area of mathematics research.
9898
</p>
9999

100100
<p>
101101
The problem above, known as the
102102
<em>Seven Bridges of Königsberg</em>,
103103
is the problem that originally inspired graph theory.
104104
Consider a <q>different</q> problem: Below is a drawing of four dots connected by some lines.
105-
Is it possible to trace over each line once and only once (without lifting up your pencil,
105+
Is it possible to trace over each line once and only once (without lifting your pencil,
106106
starting and ending on a dot)?
107107
</p>
108108

@@ -139,19 +139,19 @@
139139
we say they are <term>adjacent</term>.
140140
<idx><h>adjacent</h><h>vertices</h></idx>
141141
The nice thing about looking at graphs instead of pictures of rivers,
142-
islands and bridges is that we now have a mathematical object to study.
142+
islands, and bridges is that we now have a mathematical object to study.
143143
We have distilled the <q>important</q>
144-
parts of the bridge picture for the purposes of the problem.
144+
parts of the bridge picture for the problem.
145145
It does not matter how big the islands are,
146146
what the bridges are made out of,
147147
if the river contains alligators, etc.
148148
All that matters is which land masses are connected to which other land masses,
149149
and how many times.
150-
This was the great insight that Euler had.
150+
This was the great insight Euler had.
151151
</p>
152152

153153
<p>
154-
We will return to the question of finding paths through graphs in <xref ref="sec_gt-paths"/>. In this section we will explore various ways that graphs can be used to represent, or <em>model</em>, real world problems. Along the way we will introduce some basic definitions, terminology, and notation that will be used in the rest of the chapter.
154+
We will return to the question of finding paths through graphs in <xref ref="sec_gt-paths"/>. In this section, we will explore various ways that graphs can be used to represent, or <em>model</em>, real-world problems. Along the way, we will introduce some basic definitions, terminology, and notation that will be used in the rest of the chapter.
155155

156156
</p>
157157
<worksheet xml:id="PA-gt-intro">
@@ -274,7 +274,7 @@
274274

275275
<statement>
276276
<p>
277-
First, let's just count the number of vertices and edges in each graph.
277+
First, let's count the number of vertices and edges in each graph.
278278
</p>
279279
<p component="interactive">
280280
Number of vertices: <m>G_1</m>: <var name="10" width="5"/>; <m>G_2</m>: <var name="6" width="5"/>; <m>G_3</m>: <var name="6" width="5"/>; <m>G_4</m>: <var name="6" width="5"/>.
@@ -448,13 +448,13 @@
448448
<p>
449449
The way we avoid ambiguities in mathematics is to provide concrete and rigorous <em>definitions</em>.
450450
Crafting good definitions is not easy, but it is incredibly important. The definition is the
451-
agreed upon starting point from which all truths in mathematics proceed. Is there a graph with
451+
agreed-upon starting point from which all truths in mathematics proceed. Is there a graph with
452452
no edges? We have to look at the definition to see if this is possible. </p>
453453

454454
<p>
455455
We want our
456456
definition to be precise and unambiguous, but it also must agree with our intuition for the
457-
objects we are studying. It needs to be useful: we <em>could</em> define a graph to be a six legged
457+
objects we are studying. It needs to be useful: we <em>could</em> define a graph to be a six-legged
458458
mammal, but that would not let us solve any problems about bridges. Instead, here is the (now)
459459
standard definition of a graph.
460460
</p>
@@ -573,8 +573,7 @@
573573
<solution>
574574
<p> No. Here the vertex sets of each graph are equal, which is a
575575
good start. Also, both graphs have two edges. In the first graph, we have edges <m>\{a,b\}</m>
576-
and <m>\{b,c\}</m>, while in the second graph we have edges <m>\{a,c\}</m> and <m>\{c,b\}</m>. Now we
577-
do have <m>\{b,c\} = \{c,b\}</m>, so that is not the problem. The issue is that <m>\{a,b\} \ne
576+
and <m>\{b,c\}</m>, while in the second graph we have edges <m>\{a,c\}</m> and <m>\{c,b\}</m>. Of course, <m>\{b,c\} = \{c,b\}</m>, so that is not the problem. The issue is that <m>\{a,b\} \ne
578577
\{a,c\}</m>. Since the edge sets of the two graphs are not equal (as sets), the graphs are
579578
not equal (as graphs). </p>
580579
</solution>
@@ -724,7 +723,7 @@
724723
<solution>
725724
<p> The graphs are NOT equal, since <m>\{a,d\}
726725
\in E_1</m> but <m>\{a,d\} \notin E_2</m>. However, since both graphs contain the same number
727-
of vertices and same number of edges, they <em>might</em> be isomorphic (this is not enough in
726+
of vertices and the same number of edges, they <em>might</em> be isomorphic (this is not enough in
728727
most cases, but it is a good start). </p>
729728

730729
<p> We can try to build an isomorphism. How about we
@@ -825,10 +824,8 @@
825824
<idx><h>graph</h><h>isomorphism class</h>
826825
</idx> Sometimes we will talk about a graph
827826
with a special name (like <m>K_n</m> or the <em>Petersen graph</em>) or perhaps draw a graph without
828-
any labels. In this case we are really referring to <em>all</em> graphs isomorphic to any copy of
829-
that particular graph. A collection of isomorphic graphs is often called an <term>isomorphism class</term>
830-
.
831-
<fn> This is not unlike geometry, where we might have more than one copy of a particular
827+
any labels. In this case, we are really referring to <em>all</em> graphs isomorphic to any copy of
828+
that particular graph. A collection of isomorphic graphs is often called an <term>isomorphism class</term>.<fn> This is not unlike geometry, where we might have more than one copy of a particular
832829
triangle. There instead of <em>isomorphic</em> we say <em>congruent</em>. </fn></p>
833830

834831
<p>
@@ -1027,7 +1024,7 @@
10271024
Back to some basic graph theory definitions. Notice that all the graphs we have drawn above have
10281025
the property that no pair of vertices is connected more than once, and no vertex is connected to
10291026
itself. Graphs like these are sometimes called <term>simple</term>, although we will just call them <em>
1030-
graphs</em>. This is because our definition for a graph says that the edges form a set of
1027+
graphs</em>. This is because our definition of a graph says that the edges form a set of
10311028
2-element subsets of the vertices. Remember that it doesn't make sense to say a set contains an
10321029
element more than once. So no pair of vertices can be connected by an edge more than once. Also,
10331030
since each edge must be a set containing two vertices, we cannot have a single vertex connected
@@ -1041,7 +1038,7 @@
10411038
<idx><h>multiset</h><h>relation
10421039
to multigraph</h>
10431040
</idx> That said, there are times we want to consider double (or more)
1044-
edges and single edge loops. For example, the <q>graph</q> we drew for the Bridges of Königsberg
1041+
edges and single-edge loops. For example, the <q>graph</q> we drew for the Bridges of Königsberg
10451042
problem had double edges because there really are two bridges connecting a particular island to
10461043
the near shore. We will call these objects <term>multigraphs</term>. This is a good name: a <em>multiset</em>
10471044
is a set in which we are allowed to include a single element multiple times. </p>

source/sec_gt-trees.ptx

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -136,7 +136,7 @@
136136

137137
<p>
138138
So far so good,
139-
but while your grandparents are (probably) not blood-relatives,
139+
but while your grandparents are (probably) not blood relatives,
140140
if we go back far enough,
141141
it is likely that they did have
142142
<em>some</em> common ancestor.
@@ -196,7 +196,7 @@
196196
</latex-image>
197197
</image>
198198
<p>
199-
We are going to add edges to this graph to following some requirements.
199+
We are going to add edges to this graph following some requirements.
200200
</p>
201201
</introduction>
202202
<task>
@@ -539,7 +539,7 @@
539539
Under each chapter, draw a vertex for each section,
540540
connecting it to the chapter it belongs to.
541541
The graph will not have any cycles; it will be a tree.
542-
But a tree with clear hierarchy which is not present if we don't identify the book vertex as the <q>top</q>.
542+
But a tree with a clear hierarchy which is not present if we don't identify the <q>book vertex</q> as the <q>top</q>.
543543
</p>
544544

545545
<p>
@@ -556,7 +556,7 @@
556556
<p>
557557
<idx><h>descendant (in a rooted tree)</h></idx>
558558
<idx><h>ancestor (in a rooted tree)</h></idx>
559-
Not surprisingly, the child of a child of a vertex is called the <term>grandchild</term> of the vertex (and it is the <term>grandparent</term>). More in general, we say that a vertex <m>v</m> is a <term>descendent</term> of a vertex <m>u</m> provided <m>u</m> is a vertex on the path from <m>v</m> to the root. Then we would call <m>u</m> an <term>ancestor</term> of <m>v</m>.
559+
Not surprisingly, the child of a child of a vertex is called the <term>grandchild</term> of the vertex (and it is the <term>grandparent</term>). More generally, we say that a vertex <m>v</m> is a <term>descendent</term> of a vertex <m>u</m> provided <m>u</m> is a vertex on the path from <m>v</m> to the root. Then we would call <m>u</m> an <term>ancestor</term> of <m>v</m>.
560560
</p>
561561

562562
<p>
@@ -630,15 +630,15 @@
630630
</example>
631631

632632
<p>
633-
<idx><h>breadth first search</h></idx>
634-
<idx><h>search</h><h>breadth first</h></idx>
635-
The key to how we partitioned the tree in the example was to know which vertex to assign to a set next. We chose to visit all vertices in the same generation before any vertices of the next generation. This is usually called a <term>breadth first search</term> (we say <q>search</q> because you often traverse a tree looking for vertices with certain properties).
633+
<idx><h>breadth-first search</h></idx>
634+
<idx><h>search</h><h>breadth-first</h></idx>
635+
The key to how we partitioned the tree in the example was to know which vertex to assign to a set next. We chose to visit all vertices in the same generation before any vertices of the next generation. This is usually called a <term>breadth-first search</term> (we say <q>search</q> because you often traverse a tree looking for vertices with certain properties).
636636
</p>
637637

638638
<p>
639-
<idx><h>depth first search</h></idx>
640-
<idx><h>search</h><h>depth first</h></idx>
641-
In contrast, we could also have partitioned the tree in a different order. Start with the root, put it in <m>A</m>. Then look for one child of the root to put in <m>B</m>. Then find a child of that vertex, into <m>A</m>, and then find its child, into <m>B</m>, and so on. When you get to a vertex with no children, retreat to its parent and see if the parent has any other children. So we travel as far from the root as fast as possible, then backtrack until we can move forward again. This is called <term>depth first search</term>.
639+
<idx><h>depth-first search</h></idx>
640+
<idx><h>search</h><h>depth-first</h></idx>
641+
In contrast, we could also have partitioned the tree in a different order. Start with the root, put it in <m>A</m>. Then look for one child of the root to put in <m>B</m>. Then find a child of that vertex, into <m>A</m>, and then find its child, into <m>B</m>, and so on. When you get to a vertex with no children, retreat to its parent and see if the parent has any other children. So we travel as far from the root as fast as possible, then backtrack until we can move forward again. This is called <term>depth-first search</term>.
642642
</p>
643643

644644
<p>

0 commit comments

Comments
 (0)