Minor wording fixes. (mainly igor -y)
Differential Revision: https://reviews.freebsd.org/D657 Reviewed by: wblock Sponsored by: Absolight
This commit is contained in:
parent
206b42631b
commit
615544d051
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=45540
1 changed files with 10 additions and 10 deletions
|
@ -1095,8 +1095,8 @@
|
|||
<row>
|
||||
<entry>500101</entry>
|
||||
<entry>February 19, 2003</entry>
|
||||
<entry><sys/dkstat.h> is empty and should
|
||||
not be included.</entry>
|
||||
<entry><sys/dkstat.h> is empty. Do not include
|
||||
it.</entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
|
@ -2500,7 +2500,7 @@
|
|||
Legacy RFC 1724 behavior of the IP_MULTICAST_IF
|
||||
ioctl has now been removed; 0.0.0.0/8 may no longer
|
||||
be used to specify an interface index.
|
||||
struct ipmreqn should be used instead.</entry>
|
||||
Use struct ipmreqn instead.</entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
|
@ -2621,7 +2621,7 @@
|
|||
<entry>May 5, 2008</entry>
|
||||
<entry>7.0-STABLE after some &man.lockmgr.9; changes,
|
||||
which makes it necessary to include
|
||||
<filename>sys/lock.h</filename> in order to use
|
||||
<filename>sys/lock.h</filename> to use
|
||||
&man.lockmgr.9;.</entry>
|
||||
</row>
|
||||
|
||||
|
@ -3490,7 +3490,7 @@
|
|||
<function>sx_init_flags()</function> KPI. The
|
||||
<constant>SX_ADAPTIVESPIN</constant> is retired and a
|
||||
new <constant>SX_NOADAPTIVE</constant> flag is
|
||||
introduced in order to handle the reversed
|
||||
introduced to handle the reversed
|
||||
logic.</entry>
|
||||
</row>
|
||||
|
||||
|
@ -4722,7 +4722,7 @@
|
|||
<row>
|
||||
<entry>1000034</entry>
|
||||
<entry>June 3, 2013</entry>
|
||||
<entry>10-CURRENT after the addition of the following
|
||||
<entry>10-CURRENT after the addition of these
|
||||
functions to libm: <function>cacos</function>,
|
||||
<function>cacosf</function>,
|
||||
<function>cacosh</function>,
|
||||
|
@ -5342,9 +5342,9 @@
|
|||
pattern used to be year followed by the month, but we decided to
|
||||
change it to a more straightforward major/minor system starting
|
||||
from 2.2. This is because the parallel development on several
|
||||
branches made it infeasible to classify the releases simply by
|
||||
their real release dates. If you are making a port now, you do
|
||||
not have to worry about old -CURRENTs; they are listed here just
|
||||
for your reference.</para>
|
||||
branches made it infeasible to classify the releases merely by
|
||||
their real release dates. Do
|
||||
not worry about old -CURRENTs; they are listed here just
|
||||
for reference.</para>
|
||||
</note>
|
||||
</chapter>
|
||||
|
|
Loading…
Reference in a new issue