os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Where appropriate, s/in to/into/.

Browse source
This commit is contained in:
Ceri Davies 2002-05-04 14:22:35 +00:00
parent 89d248fca4
commit 5ae67b1827
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=12950
7 changed files with 18 additions and 18 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml
View file

@ -5325,7 +5325,7 @@ natd_flags=""</programlisting>
<listitem>
<para>Turn on TCP Wrapping for internal services which are
built in to <application>inetd</application>. (on by
built into <application>inetd</application>. (on by
default)</para>
</listitem>
</varlistentry>

6
en_US.ISO8859-1/books/handbook/basics/chapter.sgml
View file

@ -787,7 +787,7 @@
285 v0 S 0:38.45 /usr/X11R6/bin/sawfish</screen>
<para>As you can see in this example, the output from &man.ps.1; is
organized in to a number of columns. <literal>PID</literal> is the
organized into a number of columns. <literal>PID</literal> is the
process ID discussed earlier. PIDs are assigned starting from 1, go up
to 99999, and wrap around back to the beginning when you run out.
<literal>TT</literal> shows the tty the program is running on, and can
@ -830,7 +830,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse
7059 nik 2 0 7260K 4644K poll 1:38 0.00% 0.00% mutt
...</screen>
<para>The output is split in to two sections. The header (the first five
<para>The output is split into two sections. The header (the first five
lines) shows the PID of the last process to run, the system load averages
(which are a measure of how busy the system is), the system uptime (time
since the last reboot) and the current time. The other figures in the
@ -842,7 +842,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse
to the output from &man.ps.1;. As before you can see the PID, the
username, the amount of CPU time taken, and the command that was run.
&man.top.1; also defaults to showing you the amount of memory space
taken by the process. This is split in to two columns, one for total
taken by the process. This is split into two columns, one for total
size, and one for resident size&mdash;total size is how much memory the
application has needed, and the resident size is how much it is actually
using at the moment. In this example you can see that Netscape has

2
en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml
View file

@ -1014,7 +1014,7 @@ Script done, &hellip;</screen>
<title>Reboot into Single User Mode</title>
<indexterm><primary>single-user mode</primary></indexterm>
<para>You should reboot in to single user mode to test the new kernel
<para>You should reboot into single user mode to test the new kernel
works. Do this by following the instructions in
<xref linkend="makeworld-singleuser">.</para>
</sect2>

16
en_US.ISO8859-1/books/handbook/install/chapter.sgml
View file

@ -217,7 +217,7 @@
<sect3 id="install-where-i386">
<title>Disk Layouts for the i386</title>
<para>A PC disk can be divided in to discrete chunks. These chunks are
<para>A PC disk can be divided into discrete chunks. These chunks are
called <firstterm>partitions</firstterm>. By design, the PC only
supports four partitions per disk. These partitions are called
<firstterm>primary partitions</firstterm>. To work around this
@ -280,7 +280,7 @@
<para>Suppose that you have a computer with a single 4GB disk that
already has a version of Windows installed, and you have split the
disk in to two drive letters, <devicename>C:</devicename> and
disk into two drive letters, <devicename>C:</devicename> and
<devicename>D:</devicename>, each of which is 2GB in size. You have
1GB of data on <devicename>C:</devicename>, and 0.5GB of data on
<devicename>D:</devicename>.</para>
@ -441,7 +441,7 @@ pqb0.0.1.4.0 PQB0 PCI EIDE</screen>
<title>Check for FreeBSD Errata</title>
<para>Although the FreeBSD project strives to ensure that each release
of FreeBSD is as stable as possible, bugs do occasionally creep in to
of FreeBSD is as stable as possible, bugs do occasionally creep into
the process. On very rare occasions those bugs affect the
installation process. As these problems are discovered and fixed they
are noted in the FreeBSD Errata, posted on the FreeBSD web site. You
@ -867,7 +867,7 @@ Booting [kernel] in 9 seconds... _</screen>
<para>Because of this, the first thing you have the opportunity to do
when installing FreeBSD is look at the list of drivers that are
configured in to the kernel, and either disable some of them, if you
configured into the kernel, and either disable some of them, if you
do not own that device, or confirm (and alter) the driver's
configuration if you do own the device but the defaults are
wrong.</para>
@ -897,7 +897,7 @@ Booting [kernel] in 9 seconds... _</screen>
<orderedlist>
<listitem>
<para>A collapsible list of all the drivers that are currently
marked as <quote>active</quote>, subdivided in to groups such as
marked as <quote>active</quote>, subdivided into groups such as
<literal>Storage</literal>, and <literal>Network</literal>. Each
driver is shown as a description, its two three letter driver
name, and the IRQ and memory port used by that driver. In
@ -910,7 +910,7 @@ Booting [kernel] in 9 seconds... _</screen>
<listitem>
<para>Drivers that have been marked inactive. They remain in the
kernel, but they will not probe for their device when the kernel
starts. These are subdivided in to groups in the same way as the
starts. These are subdivided into groups in the same way as the
active driver list.</para>
</listitem>
@ -1020,7 +1020,7 @@ Booting [kernel] in 9 seconds... _</screen>
floppy that contains the programs used to reconfigure the card.
In any case, you should refer to the documentation that came with
the device. This will obviously entail restarting your computer,
so you will need to boot back in to the FreeBSD installation
so you will need to boot back into the FreeBSD installation
routine when you have reconfigured the card.</para>
</step>
@ -2008,7 +2008,7 @@ Mounting root from ufs:/dev/md0c
<application>FDisk</application> will start, with a display similar to
that shown in <xref linkend="sysinstall-fdisk1">.</para>
<para>The <application>FDisk</application> display is broken in to three
<para>The <application>FDisk</application> display is broken into three
sections.</para>
<para>The first section, covering the first two lines of the display,

4
en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml
View file

@ -85,7 +85,7 @@
kernel's functionality is contained in modules which can be dynamically
loaded and unloaded from the kernel as necessary. This allows the
kernel to adapt to new hardware suddenly becoming available (such as
PCMCIA cards in a laptop), or for new functionality to be brought in to
PCMCIA cards in a laptop), or for new functionality to be brought into
the kernel that was not necessary when the kernel was originally
compiled. Colloquially these are called KLDs.</para>
@ -283,7 +283,7 @@
</step>
<step>
<para>Change in to the build directory.</para>
<para>Change into the build directory.</para>
<screen>&prompt.root; <userinput>cd ../../compile/<replaceable>MYKERNEL</replaceable></userinput></screen>
</step>

4
en_US.ISO8859-1/books/handbook/policies/chapter.sgml
View file

@ -309,7 +309,7 @@ obrien@FreeBSD.org - 30 March 1997</programlisting>
<listitem>
<para>The <link linkend="staff-who">Release Engineer</link>
decides whether or not it goes in to the release.</para>
decides whether or not it goes into the release.</para>
</listitem>
</orderedlist>
</listitem>
@ -327,7 +327,7 @@ obrien@FreeBSD.org - 30 March 1997</programlisting>
<listitem>
<indexterm><primary>release engineer</primary></indexterm>
<para>The <link linkend="staff-who">Release Engineer</link>
decides if it goes in to the release.</para>
decides if it goes into the release.</para>
</listitem>
</orderedlist>
</listitem>

2
en_US.ISO8859-1/books/handbook/ports/chapter.sgml
View file

@ -221,7 +221,7 @@
<para>The FreeBSD web site maintains an up-to-date searchable list of
all the available applications, at
<ulink url="../../../../ports/index.html">http://www.FreeBSD.org/ports/</ulink>.
The name space is divided in to categories, and you may either
The name space is divided into categories, and you may either
search for an application by name (if you know it), or you can list
all the applications available in a category.</para>
</listitem>