Index: openacs-4/packages/acs-core-docs/www/objects.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/objects.html,v
diff -u -N -r1.52 -r1.52.2.1
--- openacs-4/packages/acs-core-docs/www/objects.html	27 Oct 2014 16:39:23 -0000	1.52
+++ openacs-4/packages/acs-core-docs/www/objects.html	23 Sep 2015 11:54:43 -0000	1.52.2.1
@@ -79,7 +79,7 @@
 Fire up your text editor and open the
 <code class="computeroutput">ROOT/packages/notes/sql/oracle/notes-create.sql</code> (<code class="computeroutput">ROOT/packages/notes/sql/postgresql/notes-create.sql</code> for the PG version) file created
 when we <a class="link" href="packages.html" title="OpenACS Packages">created the package</a>.  Then, do the following:
-</p><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140717562637856"></a>Describe the new type to the type system</h4></div></div></div><p>
+</p><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140480057619632"></a>Describe the new type to the type system</h4></div></div></div><p>
 First, add an entry to the <code class="computeroutput">acs_object_types</code> table with the following PL/SQL call:
 </p><pre class="programlisting">
 begin  
@@ -139,7 +139,7 @@
 because the new type <code class="computeroutput">note</code> is a subtype of
 <code class="computeroutput">acs_object</code>, it will inherit these attributes, so there is
 no need for us to define them.
-</p></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140717559745456"></a>Define a table in which to store your objects</h4></div></div></div><p>
+</p></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140480058480144"></a>Define a table in which to store your objects</h4></div></div></div><p>
 The next thing we do is make a small modification to the data model to
 reflect the fact that each row in the <code class="computeroutput">notes</code> table
 represents something that is not only an object of type
@@ -164,7 +164,7 @@
 use the <code class="computeroutput">acs_objects</code> table to find objects will
 transparently find any objects that are instances of any subtype of
 <code class="computeroutput">acs_objects</code>.
-</p></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140717562490000"></a>Define a package for type specific procedures</h4></div></div></div><p>
+</p></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140480061304992"></a>Define a package for type specific procedures</h4></div></div></div><p>
 The next step is to define a PL/SQL package for your new type, and
 write some basic procedures to create and delete objects. Here is a
 package definition for our new type:
@@ -212,7 +212,7 @@
 object OBJ was "read only", then any other object that used OBJ as its
 context would also be "read only" by default. We'll talk about this more
 later.
-</p></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140717558867552"></a>Define a package body for type specific procedures</h4></div></div></div><p>
+</p></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140480045443952"></a>Define a package body for type specific procedures</h4></div></div></div><p>
 The PL/SQL package body contains the implementations of the procedures
 defined above. The only subtle thing going on here is that we must use
 <code class="computeroutput">acs_object.new</code> to insert a row into