Globally changed DejaGnu to DejaGNU

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3759 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

3 files changed, 11 insertions, 11 deletions

diff --git a/chapter05/binutils-pass1.xml b/chapter05/binutils-pass1.xml
index ae00bdc3d..96ebbdfa6 100644
--- a/chapter05/binutils-pass1.xml
+++ b/chapter05/binutils-pass1.xml
@@ -96,7 +96,7 @@ is passed to the <command>libtool</command> program, which then passes
 </variablelist>
 
 <para>Compilation is complete. Normally we would now run the test suite, but
-at this early stage the test suite framework (Tcl, Expect and DejaGnu) is not
+at this early stage the test suite framework (Tcl, Expect and DejaGNU) is not
 yet in place. And there would be little point in running the tests anyhow,
 since the programs from this first pass will soon be replaced by those from the
 second.</para>
diff --git a/chapter05/dejagnu.xml b/chapter05/dejagnu.xml
index 969eb36db..95b6641d3 100644
--- a/chapter05/dejagnu.xml
+++ b/chapter05/dejagnu.xml
@@ -3,14 +3,14 @@
   <!ENTITY % general-entities SYSTEM "../general.ent">
   %general-entities;
 ]>
-<sect1 id="ch-tools-dejagnu" xreflabel="DejaGnu" role="wrap">
-<title>DejaGnu-&dejagnu-version;</title>
+<sect1 id="ch-tools-dejagnu" xreflabel="DejaGNU" role="wrap">
+<title>DejaGNU-&dejagnu-version;</title>
 <?dbhtml filename="dejagnu.html"?>
 
-<indexterm zone="ch-tools-dejagnu"><primary sortas="a-DejaGnu">DejaGnu</primary></indexterm>
+<indexterm zone="ch-tools-dejagnu"><primary sortas="a-DejaGNU">DejaGNU</primary></indexterm>
 
 <sect2 role="package"><title/>
-<para>The DejaGnu package contains a framework for testing other programs.</para>
+<para>The DejaGNU package contains a framework for testing other programs.</para>
 
 <segmentedlist>
 <segtitle>&buildtime;</segtitle>
@@ -19,16 +19,16 @@
 </segmentedlist>
 
 <segmentedlist>
-<segtitle>Dejagnu installation depends on</segtitle>
+<segtitle>DejaGNU installation depends on</segtitle>
 <seglistitem><seg>Bash, Binutils, Coreutils, Diffutils,
 GCC, Glibc, Grep, Make, Sed</seg></seglistitem>
 </segmentedlist>
 </sect2>
 
 <sect2 role="installation">
-<title>Installation of DejaGnu</title>
+<title>Installation of DejaGNU</title>
 
-<para>Prepare DejaGnu for compilation:</para>
+<para>Prepare DejaGNU for compilation:</para>
 
 <screen><userinput>./configure --prefix=/tools</userinput></screen>
 
@@ -39,7 +39,7 @@ GCC, Glibc, Grep, Make, Sed</seg></seglistitem>
 </sect2>
 
 
-<sect2 id="contents-dejagnu" role="content"><title>Contents of DejaGnu</title>
+<sect2 id="contents-dejagnu" role="content"><title>Contents of DejaGNU</title>
 
 <segmentedlist>
 <segtitle>Installed program</segtitle>
@@ -53,7 +53,7 @@ GCC, Glibc, Grep, Make, Sed</seg></seglistitem>
 <listitem>
 <indexterm zone="ch-tools-dejagnu runtest"><primary sortas="b-runtest">runtest</primary></indexterm>
 <para>is the wrapper script that finds the proper
-<command>expect</command> shell and then runs DejaGnu.</para>
+<command>expect</command> shell and then runs DejaGNU.</para>
 </listitem>
 </varlistentry>
 </variablelist>
diff --git a/chapter05/gcc-pass2.xml b/chapter05/gcc-pass2.xml
index 7b5130376..3d451ce11 100644
--- a/chapter05/gcc-pass2.xml
+++ b/chapter05/gcc-pass2.xml
@@ -25,7 +25,7 @@
 <title>Re-installation of GCC</title>
 
 <para>The tools required to test GCC and Binutils are installed now: Tcl,
-Expect and DejaGnu. Therefore we can now rebuild GCC and Binutils, linking
+Expect and DejaGNU. Therefore we can now rebuild GCC and Binutils, linking
 them against the new Glibc, and test them properly (if running the test suites
 in this chapter). One thing to note, however, is that these test suites are
 highly dependent on properly functioning pseudo terminals (PTYs) which are