Index: openacs-4/packages/acs-core-docs/www/eng-standards-versioning.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/eng-standards-versioning.html,v
diff -u -r1.54.2.3 -r1.54.2.4
--- openacs-4/packages/acs-core-docs/www/eng-standards-versioning.html	27 Jun 2019 18:22:21 -0000	1.54.2.3
+++ openacs-4/packages/acs-core-docs/www/eng-standards-versioning.html	3 Sep 2021 09:14:58 -0000	1.54.2.4
@@ -91,7 +91,7 @@
       coding standards; is fully internationalized; available on both
       supported databases.  </p></li><li class="listitem"><p> <span class="strong"><strong>Level 4:
       Deprecated.</strong></span> The package was in some earlier version
-      is use, but was probably replaced by a another package. The
+      is use, but was probably replaced by another package. The
       package description should point to a preferred version.
       </p></li></ul></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="naming-upgrade-scripts"></a>Naming Database Upgrade Scripts</h3></div></div></div><p>Database upgrade scripts must be named very precisely in order for the Package Manager to run the correct script at the correct time.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>Upgrade scripts should be named <code class="computeroutput">/packages/<span class="replaceable"><span class="replaceable">myfirstpackage</span></span>/sql/<span class="replaceable"><span class="replaceable">postgresql</span></span>/upgrade/upgrade-<span class="replaceable"><span class="replaceable">OLDVERSION</span></span>-<span class="replaceable"><span class="replaceable">NEWVERSION</span></span>.sql</code></p></li><li class="listitem"><p>If the version you are working on is a later version than the current released version, OLDVERSION should be the current version.  The current version is package version in the APM and in <code class="computeroutput">/packages/<span class="replaceable"><span class="replaceable">myfirstpackage</span></span>/<span class="replaceable"><span class="replaceable">myfirstpackage</span></span>.info</code>.  So if forums is at 2.0.1, OLDVERSION should be 2.0.1d1.  Note that this means that new version development that includes an upgrade must start at d2, not d1.
         </p></li><li class="listitem"><p>If you are working on a pre-release version of a package, use the current package version as OLDVERSION.  Increment the package version as appropriate (see above) and use the new version as NEWVERSION.  For example, if you are working on 2.0.1d3, make it 2.0.1d4 and use <code class="computeroutput">upgrade-2.0.1d3-2.0.1d4.sql</code>.</p></li><li class="listitem"><p>Database upgrades should be confined to development releases, not alpha or beta releases.</p></li><li class="listitem"><p>