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

More minor smithing.

Browse source
This commit is contained in:
Ceri Davies 2005-08-17 10:38:40 +00:00
parent ca0a1af9fc
commit c206b7579b
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=25393
1 changed files with 6 additions and 6 deletions

12
en_US.ISO8859-1/articles/version-guide/article.sgml
View file

@ -58,7 +58,7 @@
<sect2 id="releases">
<title>Releases</title>
<para><literal>releases</literal> are named with a <firstterm>major
<para><literal>Releases</literal> are named with a <firstterm>major
version number</firstterm> and <firstterm>minor version
number</firstterm>.<para>
@ -126,8 +126,8 @@
</sect2>
<sect2 id="ports-vs-packages">
<title><firstterm>ports</firstterm> versus
<firstterm>PACKAGES</firstterm></title>
<title><firstterm>Ports</firstterm> versus
<firstterm>Packages</firstterm></title>
<para>Separately from the files distributed above, &os;
supports thousands of applications that are developed by third
@ -138,7 +138,7 @@
programs to be installed (termed the <firstterm>Ports
Collection</firstterm>). Applications may be installed
either from source, if its licensing terms allow such
redistribution (these are termed <literal>ports</literal>,
redistribution (these are termed <literal>ports</literal>),
or as compiled binaries if allowed (these are termed
<literal>packages</literal>).</para>
</sect2>
@ -262,7 +262,7 @@
be able to better plan for the future.</para>
<para>These considerations, rather than any kind of keeping up with
the major release number of any other OS, is the main motivation for
the major release number of any other OS, comprise the main motivation for
the scheduling changes going forward.</para>
</sect1>
@ -389,7 +389,7 @@
<title>Conclusion</title>
<para>We hope that this article serves as a useful starting point
for understand the &os; development model and deciding what version
for understanding the &os; development model and deciding what version
is right for your needs.</para>
</sect1>
</article>