From bafc80349258758203361b9ca22e140424fb0e71 Mon Sep 17 00:00:00 2001
From: "Martin A. Brown" <martin@linux-ip.net>
Date: Wed, 2 Mar 2016 22:18:00 -0800
Subject: [PATCH] <progralistingco/> can/should be omitted unless <areaspec/>
 included

---
 LDP/howto/docbook/Font-HOWTO/Font-HOWTO.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/LDP/howto/docbook/Font-HOWTO/Font-HOWTO.xml b/LDP/howto/docbook/Font-HOWTO/Font-HOWTO.xml
index d351642c..b06df590 100644
--- a/LDP/howto/docbook/Font-HOWTO/Font-HOWTO.xml
+++ b/LDP/howto/docbook/Font-HOWTO/Font-HOWTO.xml
@@ -558,7 +558,7 @@ myfonts/myfonts/font3.ttf
 			<para>To build an <acronym>RPM</acronym> package you'll have to create a <filename>.spec</filename> file that provides instructions to the package builder on how to organize the files, package description, author, copyright, etc. We provide a template <ulink url="template.spec" >here</ulink> that you can use to start your work. The template looks like this:</para>
 			<example id="spectemplate" >
 				<title>The <filename>.spec</filename> file template</title>
-				<programlistingco>
+				<!-- <programlistingco> -->
 					<programlisting>
 Name: myfonts     <co id="spectemplate.name" />
 Summary: Collection of My Funny Fonts   <co id="spectemplate.summary" />
@@ -715,7 +715,7 @@ rm -rf $RPM_BUILD_ROOT
 							<para>The evolution history of this package here. Must follow this layout.</para>
 						</callout>
 					</calloutlist>
-				</programlistingco>
+				<!-- </programlistingco> -->
 			</example>
 			<para>This file must be named as the name of the package - <filename>myfonts.spec</filename> in our example. And you must put it under the main directory of the package. So in the end we'll have something like this:</para>
 			<screen>