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

Sentences should be short enough to read without gasping for air in

Browse source 
the middle.  While I'm here, reorganize a bit of language to make
things slightly more orderly.
This commit is contained in:
Michael Lucas 2002-06-25 16:37:58 +00:00
parent 457889b160
commit cdad1be94b
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=13477
1 changed files with 9 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
en_US.ISO8859-1/books/faq/book.sgml
View file

@ -362,18 +362,18 @@
</question>
<answer>
<para>Back when FreeBSD 2.0.5 was released, we decided to
branch FreeBSD development into two parts. One branch was
<para>Back when FreeBSD 2.0.5 was released,
FreeBSD development branched in two. One branch was
named <ulink
URL="../handbook/current-stable.html#STABLE">-STABLE</ulink>,
with the intention that only well-tested bug fixes and
small incremental enhancements would be made to it (for
Internet Service Providers and other commercial
one <ulink URL="../handbook/current-stable.html#CURRENT">-CURRENT</ulink>.
FreeBSD-STABLE is intended for Internet Service Providers and other commercial
enterprises for whom sudden shifts or experimental
features are quite undesirable). The other branch was
<ulink
URL="../handbook/cutting-edge.html#CURRENT">-CURRENT</ulink>,
which essentially has been one unbroken line leading
features are quite undesirable. It
receives only well-tested bug fixes and
other small incremental enhancements.
FreeBSD-CURRENT,
on the other hand, has been one unbroken line leading
towards 5.0-RELEASE (and beyond) since 2.0 was
released. If a little ASCII art would help, this is how it
looks:</para>