doc-el commit 985:4e69a47acb56 - Minor whitespace nits in en_US ...

[freebsd-doc-el at lists.hellug.gr]

changeset: 985:4e69a47acb56
user:      Manolis Kiagias <sonicy at otenet.gr>
date:      2008-11-01 11:30 +0200
details:   http://hg.hellug.gr/freebsd/doc-el/?cmd=changeset;node=4e69a47acb56

description:
	Minor whitespace nits in en_US cutting-edge chapter

diffstat:

1 file changed, 4 insertions(+), 4 deletions(-)
en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml |    8 ++++----

diffs (32 lines):

diff -r 52b8c459e0a7 -r 4e69a47acb56 en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml
--- a/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml	Fri Oct 31 23:39:43 2008 +0200
+++ b/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml	Sat Nov 01 11:30:26 2008 +0200
@@ -289,7 +289,7 @@
 	      </indexterm>
 	      <listitem>
 		<para>Use the <application><link
-		  linkend="ctm">CTM</link></application> facility.  If you
+		    linkend="ctm">CTM</link></application> facility.  If you
 		  have very bad connectivity (high price connections or
 		  only email access) <application>CTM</application> is an
 		  option.  However, it is a lot of hassle and can give you
@@ -373,8 +373,8 @@
 	    of the current security policy for old releases of
 	    FreeBSD, please see <ulink
 	      url="&url.base;/security/">http://www.FreeBSD.org/security/</ulink>.</para>
-	  </footnote>
-	  , and tracking an entire development branch just
+	  </footnote>,
+	  and tracking an entire development branch just
 	  for security reasons is likely to bring in a lot of unwanted
 	  changes as well.</para>
 
@@ -476,7 +476,7 @@
 	      </indexterm>
 	      <listitem>
 		<para>Use the <application><link
-		  linkend="ctm">CTM</link></application> facility.  If
+		    linkend="ctm">CTM</link></application> facility.  If
 		  you do not have a fast and inexpensive connection to
 		  the Internet, this is the method you should consider
 		  using.</para>