aboutsummaryrefslogtreecommitdiffstats
path: root/chapter05
diff options
context:
space:
mode:
Diffstat (limited to 'chapter05')
-rw-r--r--chapter05/flex.xml2
-rw-r--r--chapter05/toolchaintechnotes.xml4
2 files changed, 3 insertions, 3 deletions
diff --git a/chapter05/flex.xml b/chapter05/flex.xml
index 639aa3abb..76ef408b7 100644
--- a/chapter05/flex.xml
+++ b/chapter05/flex.xml
@@ -35,7 +35,7 @@ following patch:</para>
<screen><userinput>patch -Np1 -i ../&flex-fixes-patch;</userinput></screen>
<para>The GNU autotools will detect that the Flex source code has been
-modified by the previous patch and tries to update the manual page
+modified by the previous patch and tries to update the man page
accordingly. This does not work on many systems, and the default page is
fine, so make sure it does not get regenerated:</para>
diff --git a/chapter05/toolchaintechnotes.xml b/chapter05/toolchaintechnotes.xml
index 6e4d54afb..802e6cf4d 100644
--- a/chapter05/toolchaintechnotes.xml
+++ b/chapter05/toolchaintechnotes.xml
@@ -194,8 +194,8 @@ included in the executable, resulting in a rather bulky program. When
a program is dynamically linked, it includes a reference to the
dynamic linker, the name of the library, and the name of the function,
resulting in a much smaller executable. A third option is to use the
-programming interface of the dynamic linker (see the
-<emphasis>dlopen</emphasis> man page for more information).</para>
+programming interface of the dynamic linker (see <filename>dlopen(3)</filename>
+for more information).</para>
<para>Dynamic linking is the default on Linux and has three major
advantages over static linking. First, only one copy of the executable