A couple of small wording, grammar and style fixes:

- add   between the &epson.perfection; and the model number
- replace a ` with ' to be consistent with the screen output
- contain -> contents
- cause -> because
- Reword the sentence containing "most of time" to one that is
  easier to read

Approved by:    jkois (mentor)
This commit is contained in:
Benedict Reuschling 2009-09-29 15:06:13 +00:00
parent f7147280b6
commit 5b2338f990
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=34739

View file

@ -1537,7 +1537,7 @@ device ehci</programlisting>
either <filename>/dev/ugen0.2</filename> or
<filename>/dev/uscanner0</filename> as device node according
to the &os; version we run. For this example, a
&epson.perfection; 1650 USB scanner was used.</para>
&epson.perfection;&nbsp;1650 USB scanner was used.</para>
</sect3>
<sect3>
@ -1646,7 +1646,7 @@ device `snapscan:/dev/pass3' is a AGFA SNAPSCAN 600 flatbed scanner</screen>
device 'epson2:libusb:/dev/usb:/dev/ugen0.2' is a Epson GT-8200 flatbed scanner</screen>
<para>This output comes from a &os;&nbsp;8.X system, the
<literal>`epson2:libusb:/dev/usb:/dev/ugen0.2'</literal> item
<literal>'epson2:libusb:/dev/usb:/dev/ugen0.2'</literal> item
gives us the backend name (<literal>epson2</literal>) and the
device node (<literal>/dev/ugen0.2</literal>) used by our
scanner.</para>
@ -1658,7 +1658,7 @@ device 'epson2:libusb:/dev/usb:/dev/ugen0.2' is a Epson GT-8200 flatbed scanner<
the backend configuration file and define the scanner device
used. The <filename
class="directory">/usr/local/etc/sane.d/</filename> directory
contains all backends configuration files. This
contains all backend configuration files. This
identification problem does appear with certain USB
scanners.</para>
@ -1685,7 +1685,7 @@ which came with this software (README, FAQ, manpages).</screen>
<para>Since the scanner is not identified, we will need to edit
the <filename>/usr/local/etc/sane.d/epson2.conf</filename>
file. The scanner model used was the &epson.perfection; 1650,
file. The scanner model used was the &epson.perfection;&nbsp;1650,
so we know the scanner will use the <literal>epson2</literal>
backend. Be sure to read the help comments in the backends
configuration files. Line changes are quite simple: comment
@ -1746,7 +1746,7 @@ device `epson:/dev/uscanner0' is a Epson GT-8200 flatbed scanner</screen>
<filename>/dev/ugen0.2</filename> which is in fact just a
symlink to the real device node called
<filename>/dev/usb/0.2.0</filename> (a quick look at the
contain of the <filename class="directory">/dev</filename>
contents of the <filename class="directory">/dev</filename>
directory will confirm it). Both, the symlink and the
device node, are owned respectively by the
<groupname>wheel</groupname> and the
@ -1770,7 +1770,7 @@ device `epson:/dev/uscanner0' is a Epson GT-8200 flatbed scanner</screen>
<para>Then we have to make the <filename>/dev/ugen0.2</filename>
symlink and the <filename>/dev/usb/0.2.0</filename> device node accessible to the <groupname>usb</groupname> group
with the correct write permissions (<literal>0660</literal> or
<literal>0664</literal>), cause by default only the owner of
<literal>0664</literal>), because by default only the owner of
these files (<username>root</username>) can write to them.
All of this is done by adding the following
lines to the <filename>/etc/devfs.rules</filename> file:</para>
@ -1779,9 +1779,8 @@ device `epson:/dev/uscanner0' is a Epson GT-8200 flatbed scanner</screen>
add path ugen0.2 mode 0660 group usb
add path usb/0.2.0 mode 0666 group usb</programlisting>
<para>For the &os;&nbsp;7.X users, the following lines with the
correct device node, most of time
<filename>/dev/uscanner0</filename>, are needed:</para>
<para>&os;&nbsp;7.X users will probably need the following lines with the
correct device node <filename>/dev/uscanner0</filename>:</para>
<programlisting>[system=5]
add path uscanner0 mode 660 group usb</programlisting>