can not -> cannot
"Cannot" is proper English, has more instances in the handbook than "can not" and conforms to O'Reilly's word list. Approved by: murray
This commit is contained in:
parent
f05db19844
commit
1c9cca9012
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=9896
5 changed files with 13 additions and 13 deletions
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.53 2001/07/14 00:57:55 murray Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.54 2001/07/14 01:56:33 chern Exp $
|
||||
-->
|
||||
|
||||
<chapter id="advanced-networking">
|
||||
|
@ -2606,7 +2606,7 @@ TWO (,hotel,test-domain)
|
|||
persist in broadcasting in search of one even after they receive a
|
||||
response from a v2 server). Note that while support for normal
|
||||
client calls is provided, this version of ypserv does not handle
|
||||
v1 map transfer requests; consequently, it can not be used as a
|
||||
v1 map transfer requests; consequently, it cannot be used as a
|
||||
master or slave in conjunction with older NIS servers that only
|
||||
support the v1 protocol. Fortunately, there probably are not any
|
||||
such servers still in use today.</para>
|
||||
|
@ -3095,7 +3095,7 @@ dhcp_flags=""</programlisting>
|
|||
<sect3>
|
||||
<title><filename>/etc/namedb/named.conf</filename></title>
|
||||
|
||||
<programlisting>// $FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.53 2001/07/14 00:57:55 murray Exp $
|
||||
<programlisting>// $FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.54 2001/07/14 01:56:33 chern Exp $
|
||||
//
|
||||
// Refer to the named(8) man page for details. If you are ever going
|
||||
// to setup a primary server, make sure you've understood the hairy
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.73 2001/06/28 22:27:27 nik Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.74 2001/06/29 18:19:55 murray Exp $
|
||||
-->
|
||||
|
||||
<chapter id="cutting-edge">
|
||||
|
@ -279,7 +279,7 @@ subscribe cvs-all</programlisting>
|
|||
the releases it affects.</para>
|
||||
|
||||
<para>Although we endeavour to ensure that the &os.stable; branch
|
||||
compiles and runs at all times, this can not be guaranteed. In
|
||||
compiles and runs at all times, this cannot be guaranteed. In
|
||||
addition, while code is developed in &os.current; before including
|
||||
it in &os.stable;, more people run &os.stable; than &os.current;, so
|
||||
it is inevitable that bugs and corner cases will sometimes be found
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/hw/chapter.sgml,v 1.38 2001/06/23 06:57:02 dd Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/hw/chapter.sgml,v 1.39 2001/06/23 07:04:37 dd Exp $
|
||||
-->
|
||||
|
||||
<appendix id="hw">
|
||||
|
@ -391,7 +391,7 @@
|
|||
<term>Neptune:</term>
|
||||
|
||||
<listitem>
|
||||
<para>Can not run more than 2 bus master devices. Admitted Intel
|
||||
<para>Cannot run more than 2 bus master devices. Admitted Intel
|
||||
design flaw. Workarounds include do not run more than 2 bus
|
||||
masters, special hardware design to replace the PCI bus
|
||||
arbiter (appears on Intel Altair board and several other Intel
|
||||
|
@ -4040,7 +4040,7 @@ disk wd3 at wdc1 drive 1</programlisting>
|
|||
number of data lines (usually 16).</para>
|
||||
|
||||
<note>
|
||||
<para>A narrow SCSI device can not communicate with a SCSI device
|
||||
<para>A narrow SCSI device cannot communicate with a SCSI device
|
||||
with a target ID larger than 7. This means it is generally not
|
||||
a good idea to move your SCSI host adapter's target ID to
|
||||
something higher than 7 (or your CDROM will stop
|
||||
|
@ -5150,7 +5150,7 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue </screen>
|
|||
<para>Native capacity is 150/250MB. Both 150MB (DC6150) and 250MB
|
||||
(DC6250) tapes have the recording format. The 250MB tapes are
|
||||
approximately 67% longer than the 150MB tapes. This drive can
|
||||
read 120MB tapes as well. It can not write 120MB tapes.</para>
|
||||
read 120MB tapes as well. It cannot write 120MB tapes.</para>
|
||||
|
||||
<para>Data transfer rate is 100kB/s</para>
|
||||
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/l10n/chapter.sgml,v 1.54 2001/06/26 19:43:07 dd Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/l10n/chapter.sgml,v 1.55 2001/07/11 21:07:31 murray Exp $
|
||||
-->
|
||||
|
||||
<chapter id="l10n">
|
||||
|
@ -454,7 +454,7 @@ keychange="<replaceable>fkey_number sequence</replaceable>"</programlisting>
|
|||
|
||||
<para>The <literal>keychange</literal> is usually needed to program
|
||||
function keys to match the selected terminal type because
|
||||
function key sequences can not be defined in the key map.</para>
|
||||
function key sequences cannot be defined in the key map.</para>
|
||||
|
||||
<para>Also be sure to set the correct console terminal type in
|
||||
<filename>/etc/ttys</filename> for all <literal>ttyv*</literal>
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml,v 1.26 2001/07/14 01:47:38 murray Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml,v 1.27 2001/07/14 02:06:29 chern Exp $
|
||||
-->
|
||||
|
||||
<chapter id="serialcomms">
|
||||
|
@ -2093,7 +2093,7 @@ raisechar=^^</programlisting>
|
|||
running. (It is assumed that <devicename>COM1:</devicename> will
|
||||
be available on a file/compute/terminal server anyway; if you
|
||||
really need <devicename>COM1:</devicename> for something else
|
||||
(and you can not switch that something else to
|
||||
(and you cannot switch that something else to
|
||||
<devicename>COM2:</devicename> (<devicename>sio1</devicename>)),
|
||||
then you probably should not even be bothering with all this in
|
||||
the first place.)</para>
|
||||
|
|
Loading…
Reference in a new issue