use glossary directive and link some terms to the glossary.

Author: rouilj

doc/glossary.txt

@@ -7,37 +7,48 @@
 Roundup Glossary
 ================
 
+.. glossary::
 
-class
-   a definition of the properties and behaviour of a set of items
-classname
-   the name of a class. It must start with a letter, end with a letter
-   or "_", and only have alphanumerics and "_" in the middle.
-db (or hyperdb)
-   a collection of items
-definitional class
-   a class that exists to define a descrete set of values. For example
-   status or priority.
-designator
-   a combined class + itemid reference to any item in the
-   hyperdb. E.g. issue26. Note that form values can include
-   something that looks like a designator composed of a classname, a
-   dash '-', and a number. E.g. file-1. These
-   are used to create new instances of a class via the web interface.
-itemid
-   a numeric reference to a particular item of one class
-item
-   a collection of data that forms one entry in the hyperdb.
-property
-   one element of data that makes up an item. In Roundup, the set 
-   of item properties may be changed as needed - even after the 
-   tracker has been initialised and used in production.
-schema
-   the definition of all the classes that make up an tracker
-tracker
-   the schema and hyperdb that forms one issue tracker
-tracker home
-   the physical location on disk of a tracker
+   class
+      a definition of the properties and behaviour of a set of items
+
+   classname
+      the name of a class. It must start with a letter, end with a letter
+      or "_", and only have alphanumerics and "_" in the middle.
+
+   db (or hyperdb)
+      a collection of items
+
+   definitional class
+      a class that exists to define a descrete set of values. For example
+      status or priority.
+
+   designator
+      a combined class + itemid reference to any item in the
+      hyperdb. E.g. issue26. Note that form values can include
+      something that looks like a designator composed of a classname, a
+      dash '-', and a number. E.g. file-1. These
+      are used to create new instances of a class via the web interface.
+
+   itemid
+      a numeric reference to a particular item of one class
+
+   item
+      a collection of data that forms one entry in the hyperdb.
+
+   property
+      one element of data that makes up an item. In Roundup, the set 
+      of item properties may be changed as needed - even after the 
+      tracker has been initialised and used in production.
+
+   schema
+      the definition of all the classes that make up an tracker
+
+   tracker
+      the schema and hyperdb that forms one issue tracker
+
+   tracker home
+      the physical location on disk of a tracker
 
 
 -----------------

doc/reference.txt

@@ -1117,7 +1117,7 @@ create(information)
 :::::::::::::::::::
 
 Create an item in the database. This is generally used to create items
-in the "definitional" classes like "priority" and "status".
+in the :term:`definitional class` like "priority" and "status".
 
 IssueClass
 ~~~~~~~~~~
@@ -1515,13 +1515,13 @@ Database Content
 ================
 
 .. note::
-   If you modify the content of definitional classes, you will
+   If you modify the content of a :term:`definitional class`, you will
    need to edit the tracker `detectors`_ if they reference a value
    of a definitional class. (E.g. if a detector checks to see if an
-   issue is "open", and you change the "open" definition to be
-   "working".)
+   issue has a status of "open", and you change the "open" definition
+   to be "working", you need to change the check.)
 
-Customisation of the special "definitional" classes (eg. status,
+Customisation of the special definitional classes (eg. status,
 priority, resolution, ...) may be done either before or after the
 tracker is initialised. The actual method of doing so is completely
 different in each case though, so be careful to use the right one.
@@ -2020,9 +2020,9 @@ for specific object of issue class with id 1 will look like:
 .. _strip_zeros:
 
 Note that a leading string of 0's will be stripped from the id part of
-the object designator in the URL. E.G. ``/issue001`` is the same as
-``/issue1``.  Similarly for ``/file01`` etc. However you should
-generate URL's without the extra zeros.
+the object :term:`designator` in the URL. E.G. ``/issue001`` is the
+same as ``/issue1``.  Similarly for ``/file01`` etc. However you
+should generate URL's without the extra zeros.
 
 Determining web context
 -----------------------