Index: openacs-4/packages/acs-kernel/sql/postgresql/acs-metadata-create.sql
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-kernel/sql/postgresql/acs-metadata-create.sql,v
diff -u -N -r1.19 -r1.20
--- openacs-4/packages/acs-kernel/sql/postgresql/acs-metadata-create.sql	11 Dec 2003 21:39:52 -0000	1.19
+++ openacs-4/packages/acs-kernel/sql/postgresql/acs-metadata-create.sql	7 Feb 2004 22:25:57 -0000	1.20
@@ -202,13 +202,13 @@
  Object types (and their subtypes) that require more type-specific
  data than the fields already existing in acs_object_types may name
  a table in which that data is stored.  The table should be keyed
- by the associated object_type.  For example, a row in the user_group_types
+ by the associated object_type.  For example, a row in the group_types
  table stores a default approval policy for every user group of that type.
- In this example, the user_group_types table has a primary key named
- group_type that references acs_object_types.  If a subtype of user_groups
+ In this example, the group_types table has a primary key named
+ group_type that references acs_object_types.  If a subtype of groups
  for example, lab_courses, has its own type-specific data, it could be
  maintained in a table called lab_course_types, with a primary key named
- lab_course_type that references user_group_types.  This provides the same
+ lab_course_type that references group_types.  This provides the same
  functionality as static class fields in an object-oriented programming language.
 ';