Correct some misuses of "its" and "it's".

Also expand some contractions of the same, discovered while I was
hunting down the above.

This commit can very likely be ignored by translation teams.
This commit is contained in:
Ceri Davies 2003-11-23 18:22:40 +00:00
parent 9b7a21de42
commit a7b5ebd24d
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=18963
7 changed files with 17 additions and 17 deletions

View file

@ -85,7 +85,7 @@ struct jail {
<para>As you can see, there is an entry for each of the
arguments passed to the jail program, and indeed, they are
set during it's execution.</para>
set during its execution.</para>
<programlisting><filename>/usr/src/usr.sbin/jail.c</filename>
j.version = 0;

View file

@ -737,7 +737,7 @@
<para>This entry point permits policy modules to perform
MAC-related events when a thread returns to user space.
This is required for policies that have floating process
labels, as it's not always possible to acquire the process
labels, as it is not always possible to acquire the process
lock at arbitrary points in the stack during system call
processing; process labels might represent traditional
authentication data, process history information, or other

View file

@ -828,7 +828,7 @@
/* The SCSI bus reset may take a long time, in this case its completion
* should be checked by interrupt or timeout. But for simplicity
* we assume here that it's really fast.
* we assume here that it is really fast.
*/
reset_scsi_bus(softc);
@ -1596,7 +1596,7 @@ ahc_async(void *callback_arg, u_int32_t code, struct cam_path *path, void *arg)<
/* re-initialization may take a lot of time, in such case
* its completion should be signaled by another interrupt or
* checked on timeout - but for simplicity we assume here that
* it's really fast
* it is really fast
*/
if(!fatal) {
reinitialize_controller_without_scsi_reset(softc);
@ -1776,7 +1776,7 @@ ahc_async(void *callback_arg, u_int32_t code, struct cam_path *path, void *arg)<
/* send event */
xpt_async(AC_SENT_BDR, hcb->ccb->ccb_h.path_id, NULL);
/* this was the CAM_RESET_DEV request itself, it's completed */
/* this was the CAM_RESET_DEV request itself, it is completed */
ccb_status = CAM_REQ_CMP;
} else {
calculate_residue(hcb);

View file

@ -269,7 +269,7 @@
<para>Implementing full kernel preemption is very
straightforward: when you schedule a thread to be executed
by putting it on a runqueue, you check to see if it's
by putting it on a runqueue, you check to see if its
priority is higher than the currently executing thread. If
so, you initiate a context switch to that thread.</para>

View file

@ -255,7 +255,7 @@
<para>The term "printserver" is one of those networking terms, like
<emphasis>packet,</emphasis> that has been carelessly tossed around
until it's meaning has become somewhat confusing and blurred. To be
until its meaning has become somewhat confusing and blurred. To be
specific, a printserver is simply a program that arbitrates print
data from multiple clients for a single printer. Printservers can
be implemented in one of the four methods described in the following
@ -922,7 +922,7 @@ Bind 3C5X9 #1 Ethernet_II LAN_NET</programlisting>
</step>
<step>
<para>The program opens up with it's menu. Click
<para>The program opens up with its menu. Click
<guibutton>Setup</guibutton> in the top menu, then select
<guimenuitem>Define New Queue</guimenuitem>.</para>
</step>
@ -1037,7 +1037,7 @@ Bind 3C5X9 #1 Ethernet_II LAN_NET</programlisting>
<para>The <command>wlprspl</command> program also can be used under
Windows 95, but as a 16-bit program, it is far from an optimal
implementation on a 32-bit operating system. In addition, Win95 and
it's derivatives fundamentally changed from Windows 3.1 in the
its derivatives fundamentally changed from Windows 3.1 in the
printing subsystem. For these reasons I use a different LPR client
program for Win95/98 LPR printing instructions. It is a full 32-bit
print program, and it installs as a <emphasis>Windows 32-bit
@ -2129,7 +2129,7 @@ lp|local line printer:\
printing raw text from the command line for directory listings,
there are two ways to fix stairstep. The first is to send a
command to the printer to make it print in "unix textfile" mode,
which makes the printer supply it's own carriage return. This
which makes the printer supply its own carriage return. This
solution is ugly in a printer environment with UNIX and Windows
machines attempting to share use of the same printer. Switching
the printer to work with UNIX disrupts DOS/Windows raw text
@ -2226,7 +2226,7 @@ lp|local line printer:\
<filename>/etc/printcap</filename> file to do this.</para>
<para>The following filter is taken from the FreeBSD Handbook. I've
slightly changed it's invocation for a couple of reasons. First,
slightly changed its invocation for a couple of reasons. First,
some PostScript printers have difficulty when two print files are
sent within the same print job or they lack the trailing
Control-D. Second is that the handbook invocation uses the LPRPS
@ -2499,7 +2499,7 @@ lpnobanner|local line printer, PostScript, no banner:\
<para>In operation, the SMB-networking client builds the print job on
itself and then transfers the entire job over the network to the Samba
server. On the server, Samba has it's own temporary print spool
server. On the server, Samba has its own temporary print spool
directory to which the job is copied. Once the job has been
completely received, it is then passed to the UNIX print
spooler.</para>
@ -2752,7 +2752,7 @@ The command was completed successfully.</screen>
<para>With Windows NT Server, loading the TCP/IP LPR printing support
also loads the LPD print server on NT. By using LPR client programs
on UNIX, it is possible to submit, view status, and remove jobs
remotely from an NT server that has LPR installed as a port for it's
remotely from an NT server that has LPR installed as a port for its
printers.</para>
<para>Following is a sample <filename>/etc/printcap</filename> file entry
@ -2789,7 +2789,7 @@ tank|sample remote printer:\
<para>The <command>lp</command> command is simply a front end command
that calls the <command>lpr</command> command with appropriate
options. It's main use is to allow the running of precompiled
options. Its main use is to allow the running of precompiled
binary programs and scripts that assume that the
<command>lp</command> command is the <emphasis>official</emphasis>
printing command.</para>

View file

@ -8548,7 +8548,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
<answer>
<para>You are running a program that requires the Berkeley
Packet Filter (&man.bpf.4;), but it's not in your kernel.
Packet Filter (&man.bpf.4;), but it is not in your kernel.
Add this to your kernel config file and build a new
kernel:</para>
@ -11086,7 +11086,7 @@ raisechar=^^</programlisting>
<answer>
<para>It stands for something in a secret language that only
members can know. It does not translate literally but its ok
members can know. It does not translate literally but it is ok
to tell you that BSD's translation is something between,
<quote>Formula-1 Racing Team</quote>, <quote>Penguins are
tasty snacks</quote>, and <quote>We have a better sense of

View file

@ -3703,7 +3703,7 @@ LDCONFIG_DIRS= %%PREFIX%%/lib/foo %%PREFIX%%/lib/bar</programlisting>
<makevar>PORTOBJFORMAT</makevar> to <literal>aout</literal> or
<literal>elf</literal> and export it in the environments
<envar>CONFIGURE_ENV</envar>, <envar>SCRIPTS_ENV</envar> and
<envar>MAKE_ENV</envar>. (It's always going to be
<envar>MAKE_ENV</envar>. (It is always going to be
<literal>aout</literal> in 2.2-STABLE). It is also passed to
<maketarget>PLIST_SUB</maketarget> as
<literal>PORTOBJFORMAT=${PORTOBJFORMAT}</literal>. (See comment on