Approved by: jkh

typos, and an innaccuracy about bi-directional parallel communication
under FreeBSD

1 files changed, 20 insertions, 23 deletions

diff --git a/en_US.ISO8859-1/books/handbook/printing/chapter.sgml b/en_US.ISO8859-1/books/handbook/printing/chapter.sgml
index 8400b1bf22..8a97aa5d16 100644
--- a/en_US.ISO8859-1/books/handbook/printing/chapter.sgml
+++ b/en_US.ISO8859-1/books/handbook/printing/chapter.sgml
@@ -1,7 +1,7 @@
 <!--
      The FreeBSD Documentation Project
 
-     $FreeBSD: doc/en_US.ISO_8859-1/books/handbook/printing/chapter.sgml,v 1.26 2000/05/17 19:55:22 jim Exp $
+     $FreeBSD: doc/en_US.ISO_8859-1/books/handbook/printing/chapter.sgml,v 1.27 2000/06/08 01:56:16 jim Exp $
 -->
 
 <chapter id="printing">
@@ -62,7 +62,7 @@
       </listitem>
 
       <listitem>
-	<para>It can send jobs over the network to another LPD spooler on
+	<para>It can send jobs over the network to a LPD spooler on
 	  another host.</para>
       </listitem>
 
@@ -216,12 +216,11 @@
 	  </itemizedlist>
 
 	  <para>In general, serial interfaces are slower than parallel
-	    interfaces.  Parallel interfaces usually offer just one-way
-	    communication (computer to printer) while serial gives you
-	    two-way.  Many newer parallel ports can also receive data from
-	    the printer, but only few printers need to send data back to
-	    the computer.  And FreeBSD does not support two-way parallel
-	    communication yet.</para>
+	    interfaces.  Parallel interfaces usually offer just
+	    one-way communication (computer to printer) while serial
+	    gives you two-way.  Many newer parallel ports and printers
+	    can communicate in both directions under FreeBSD when a
+	    IEEE1284 compliant cable is used.</para>
 
 	  <para>Usually, the only time you need two-way communication with
 	    the printer is if the printer speaks PostScript.  PostScript
@@ -831,7 +830,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none</programlisting>
 
 	  <para>The first (easy) step is to pick a name for your printer
 	    It really does not matter whether you choose functional or
-	    whimsical names since you can also provide a number aliases
+	    whimsical names since you can also provide a number of aliases
 	    for the printer.</para>
 
 	  <para>At least one of the printers specified in the
@@ -1695,7 +1694,7 @@ fi</programlisting>
           special text filter for your printer, you can make your
           non-PostScript printer act like a real PostScript printer.</para>
             
-        <para>Ghostscript should be in the FreeBSD ports collection, if you
+        <para>Ghostscript is in the FreeBSD ports collection, if you
           would like to install it from there.  You can fetch, build, and
           install it quite easily yourself, as well.</para>
             
@@ -3205,8 +3204,8 @@ madrigal.fishbaum.de</programlisting>
               <para>This means <hostid>rose</hostid> will accept requests from
                 the hosts <hostid>orchid</hostid>, <hostid>violet</hostid>,
                 and <hostid role="fqdn">madrigal.fishbaum.de</hostid>. If any
-                other host tries to access <hostid>rose</hostid>'s LPD, LPD
-                will refuse them.</para>
+                other host tries to access <hostid>rose</hostid>'s
+                LPD, the job will be refused.</para>
             </listitem>
           </varlistentry>
           
@@ -3519,7 +3518,7 @@ total                     337.00  154   $  6.74</screen>
           to be able to determine how much paper a job uses.  This is the
           essential problem of printer accounting.</para>
             
-        <para>For plain text jobs, the problem's not that hard to solve: you
+        <para>For plain text jobs, the problem is not that hard to solve: you
           count how many lines are in a job and compare it to how many lines
           per page your printer supports.  Do not forget to take into account
           backspaces in the file which overprint lines, or long logical lines
@@ -3940,16 +3939,14 @@ cfA013rose dequeued
 	    
 	<screen>&prompt.user; <userinput>zcat /usr/share/man/man1/ls.1.gz | troff -t -man | lpr -t</userinput></screen>
 	      
-	<para>The &man.zcat.1; command uncompresses the source of the</para>
-	    
-	<para>&man.ls.1; manual page and passes it to the &man.troff.1;
-	  command, which formats that source and makes GNU troff output and
-	  passes it to &man.lpr.1;, which submits the job to the LPD spooler.
-	  Because we used the <option>-t</option> option to</para>
-	    
-	<para>&man.lpr.1;, the spooler will convert the GNU troff output into
-	  a format the default printer can understand when it prints the
-	  job.</para>
+	<para>The &man.zcat.1; command uncompresses the source of the
+	  &man.ls.1; manual page and passes it to the &man.troff.1;
+	  command, which formats that source and makes GNU troff
+	  output and passes it to &man.lpr.1;, which submits the job
+	  to the LPD spooler.  Because we used the <option>-t</option>
+	  option to &man.lpr.1;, the spooler will convert the GNU
+	  troff output into a format the default printer can
+	  understand when it prints the job.</para>
       </sect3>
       
       <sect3 id="printing-lpr-options-job-handling">