Oops. Missed something.

git-svn-id: https://svn.apache.org/repos/asf/jakarta/poi/trunk@352296 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/src/documentation/xdocs/hssf/how-to.xml b/src/documentation/xdocs/hssf/how-to.xml
index 01d59232d036e4eb448cc1e1e0e82c7962e55674..d642f6152bfdd09b6a6f29f135644ebc534550f9 100644 (file)
--- a/src/documentation/xdocs/hssf/how-to.xml
+++ b/src/documentation/xdocs/hssf/how-to.xml
@@ -446,7 +446,7 @@ down problems.
 <p>So Why use commons logging rather than log4j? Well the following discussion from
 the jakarta-general mailing list sums it up pretty well.  (Thanks Morgan)
 </p>
-<p>Here's the problem, as I see it.
+<p><em>Here's the problem, as I see it.</em>
 </p>
 <p><em>Suppose Commons component A decides to adopt Log4J, Commons component B
 decides to adopt LogKit, and Commons component C adopts JDK1.4 logging.