Minor word niggles on the snapshot page:
- if something is obvious, don't say it - use &os; - people don't really use netnews - don't discourage bug submissions about documentation Approved by: bcr (mentor)
This commit is contained in:
parent
dfa8b0d764
commit
cb04387d47
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=40759
1 changed files with 4 additions and 4 deletions
|
@ -69,7 +69,7 @@
|
|||
These are <em>not</em> releases, these are <em>snapshots</em>,
|
||||
and it is important that this distinction be preserved.
|
||||
Although people can and will, of course, refer to snapshots
|
||||
by date in mail or netnews, do not confuse them.</li>
|
||||
by date in email, do not confuse them.</li>
|
||||
|
||||
<li>Snapshots might not include package sets, but will generally
|
||||
include a ports tree.</li>
|
||||
|
@ -78,12 +78,12 @@
|
|||
For example, <tt>README</tt> may still refer
|
||||
to a previous release. This is because that is much less important
|
||||
than getting the real bug fixes and new features out for testing.
|
||||
Please do not send a bug report about the documentation.</li>
|
||||
Please do not send a bug report about version numbers.</li>
|
||||
</ul>
|
||||
|
||||
<p>Your feedback on these snapshots is, of course, greatly welcome.
|
||||
<p>Your feedback on these snapshots is greatly welcome.
|
||||
They are not just for our benefit - those who are coming to rely
|
||||
on FreeBSD for mission critical applications should welcome
|
||||
on &os; for mission critical applications should welcome
|
||||
a chance to get at more updated bits in a structured fashion.
|
||||
You can also use these snapshots as tangible evidence that your
|
||||
feedback is getting incorporated and that you (hopefully) will not have
|
||||
|
|
Loading…
Reference in a new issue