Index: openacs-4/packages/acs-core-docs/www/subsites.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/subsites.adp,v
diff -u -N -r1.1.2.3 -r1.1.2.4
--- openacs-4/packages/acs-core-docs/www/subsites.adp	28 Sep 2015 07:54:25 -0000	1.1.2.3
+++ openacs-4/packages/acs-core-docs/www/subsites.adp	9 Jun 2016 13:03:11 -0000	1.1.2.4
@@ -225,7 +225,7 @@
 instance at the user's home page, and set up the permissions so
 that the instance is only visible to that user. The end result is a
 site where users can come and write notes to themselves.</p><p>This is a good example of the leverage available in the OpenACS
-5.7.0 system. The code that we have written for Notes is not at all
+5.9.0 system. The code that we have written for Notes is not at all
 more complex than a similar application without access control or
 site map awareness. By adding a small amount of code, we have taken
 a small, simple, and special purpose application to something that
@@ -234,7 +234,7 @@
 administration.</p>
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="subsites-summary" id="subsites-summary"></a>Summary</h3></div></div></div><p>In OpenACS 5.7.0, application pages and scripts can be aware of
+<a name="subsites-summary" id="subsites-summary"></a>Summary</h3></div></div></div><p>In OpenACS 5.9.0, application pages and scripts can be aware of
 the package instance, or subsite in which they are executing. This
 is a powerful general purpose mechanism that can be used to
 structure web services in very flexible ways.</p><p>We saw how to use this mechanism in the Notes application and