Various grammar and word-smithing fixes from Gnats.
PR: docs/34547 Submitted by: Jay Edwards <jayed@jayed.com>
This commit is contained in:
parent
b4be411f83
commit
1f67b659df
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=13996
1 changed files with 13 additions and 13 deletions
|
@ -239,7 +239,7 @@
|
|||
<quote>at no cost</quote>, the other meaning <quote>you can do
|
||||
whatever you like</quote>. Apart from one or two things you
|
||||
<emphasis>cannot</emphasis> do with the FreeBSD code, for
|
||||
example pretending you wrote it, you really can do whatever you
|
||||
example pretending you wrote it, you can really do whatever you
|
||||
like with it.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
@ -258,7 +258,7 @@
|
|||
|
||||
<para>Briefly, <emphasis>-STABLE</emphasis> is aimed
|
||||
at the ISP, corporate user, or any user who wants stability and a
|
||||
low change count over the wizzy new features of the latest
|
||||
minimal number of changes compared to the new (and possibly unstable) features of the latest
|
||||
<emphasis>-CURRENT</emphasis> snapshot. Releases can come
|
||||
from either branch, but <emphasis>-CURRENT</emphasis>
|
||||
should only be used if you are prepared for its increased volatility (relative to
|
||||
|
@ -306,8 +306,8 @@
|
|||
<para>Every day, <ulink
|
||||
URL="../../../../releases/snapshots.html">snapshot
|
||||
</ulink> releases are made based on the current state of the
|
||||
-CURRENT and -STABLE branches. Nowadays, distributions of the
|
||||
occasional snapshot are now being made available. The goals
|
||||
-CURRENT and -STABLE branches. Distributions of the
|
||||
occasional snapshot are made available. The goals
|
||||
behind each snapshot release are:</para>
|
||||
|
||||
<itemizedlist>
|
||||
|
@ -331,7 +331,7 @@
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>To ensure that any new features in need of testing
|
||||
<para>To ensure that all new features and fixes in need of testing
|
||||
have the greatest possible number of potential
|
||||
testers.</para>
|
||||
</listitem>
|
||||
|
@ -351,7 +351,7 @@
|
|||
3-STABLE snapshots are not being produced at the time of
|
||||
this writing (May 2000).</para>
|
||||
|
||||
<para>Snapshots are generated, on the average, once a day for
|
||||
<para>Snapshots are generated, on the average, daily for
|
||||
all actively developed branches.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
@ -439,7 +439,7 @@
|
|||
that the addition of new features does not compromise the
|
||||
stability of the release.
|
||||
Many users regard this caution as one of the best
|
||||
things about FreeBSD, although
|
||||
things about FreeBSD, even though
|
||||
waiting for all the latest goodies to reach -STABLE
|
||||
can be a little frustrating.</para>
|
||||
|
||||
|
@ -450,7 +450,7 @@
|
|||
engineering</ulink> pages on the FreeBSD Web site.</para>
|
||||
|
||||
<para>For people who need or want a little more excitement,
|
||||
binary snapshots are made every day as discussed above.</para>
|
||||
binary snapshots are made daily as discussed above.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
|
@ -504,13 +504,13 @@
|
|||
<listitem>
|
||||
<para><ulink
|
||||
URL="ftp://releng4.FreeBSD.org/pub/FreeBSD/">4.X
|
||||
snapshots</ulink> are usually made once a day.</para>
|
||||
snapshots</ulink> are usually made daily.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><ulink
|
||||
URL="ftp://current.FreeBSD.org/pub/FreeBSD/">
|
||||
5.0 Snapshot</ulink> releases are made once a day for the
|
||||
5.0 Snapshot</ulink> releases are made daily for the
|
||||
<link linkend="current">-CURRENT</link> branch, these being
|
||||
of service purely to bleeding-edge testers and
|
||||
developers.</para>
|
||||
|
@ -3898,7 +3898,7 @@ quit</programlisting>
|
|||
</question>
|
||||
|
||||
<answer>
|
||||
<para>This can be caused by various hardware and/or software
|
||||
<para>This can be caused by various hardware or software
|
||||
ailments relating to interrupts. It may be due to bugs but can
|
||||
also happen by nature of certain devices. Running TCP/IP over
|
||||
the parallel port using a large MTU is one good way to provoke
|
||||
|
@ -5719,7 +5719,7 @@ C:\="DOS"</programlisting>
|
|||
<screen>&prompt.root; <userinput>dd if=/dev/rda0a of=/mnt/bootsect.bsd bs=512 count=1</userinput></screen>
|
||||
|
||||
<para>Reboot into DOS or NT. NTFS users copy the
|
||||
<filename>bootsect.bsd</filename> and/or the
|
||||
<filename>bootsect.bsd</filename> or the
|
||||
<filename>bootsect.lnx</filename> file from the floppy to
|
||||
<filename>C:\</filename>. Modify the attributes (permissions)
|
||||
on <filename>boot.ini</filename> with:</para>
|
||||
|
@ -11096,7 +11096,7 @@ raisechar=^^</programlisting>
|
|||
usefulness was stretched more and more with each new feature.
|
||||
In addition, people wanted to dynamically load things at run
|
||||
time, or to junk parts of their program after the init code had
|
||||
run to save in core memory and/or swap space. Languages became
|
||||
run to save in core memory and swap space. Languages became
|
||||
more sophisticated and people wanted code called before main
|
||||
automatically. Lots of hacks were done to the
|
||||
<filename>a.out</filename> format to allow all of these things
|
||||
|
|
Loading…
Reference in a new issue