[Db-derby Wiki] Trivial Update of "DerbySnapshotOrRelease" by JohnHEmbretsen

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by JohnHEmbretsen:
http://wiki.apache.org/db-derby/DerbySnapshotOrRelease

------------------------------------------------------------------------------
  
  For example, when adding a new demo or changing which files gets included in certain subdirectories of a -bin distribution, reviewing generated release artifacts is often the only way to verify that modifications made to the build scripts are correct (of course, having a developer with knowledge of the build scripts and experience with the release building process review the patch thoroughly would help as well).
  
- Note that this section describes only a small subset of the steps needed to build a real Apache Derby release. The generated artifacts are '''''only suitable for private testing purposes only'''''.
+ Note that this section describes only a small subset of the steps needed to build a real Apache Derby release. The generated artifacts are '''''suitable for private testing purposes only'''''.
   * the development community has not been involved
   * version numbers are probably incorrect
   * release notes are wrong, or not included at all
   * jars are not signed
   * etc. etc.
  
- To build a set of release artifacts that are suitable for reviewing the file structure of a release, among other things, do the following steps (extraced from the full release procedure description above):
+ To build a set of release artifacts that is suitable for reviewing the file structure of a release, among other things, do the following steps (extracted from the full release procedure description above):
  
   1. Check out (or update) the source tree from which you want to build release artifacts, for example 
     https://svn.apache.org/repos/asf/db/derby/code/trunk/ for the trunk