update of the doc

doc/configapi.txt

@@ -46,7 +46,7 @@ Here are some private attributes of a `Config()` object, for a
 comprehension of the internal merchanism:
 
 - `_cfgimpl_descr =` `option.OptionDescription()`,
-  e.g. the `optionapi#schema`
+  e.g. the :ref:`optdescr`
 
 - `_cfgimpl_values` contains the `option.Option()`'s values.
   Yes, the values of the options: remember that the values are stored **inside**
@@ -57,7 +57,7 @@ comprehension of the internal merchanism:
 ::
 
     {'int': 0, 'wantframework': False, 'objspace': 'std', 'bool': False,
-    'str': 'abc', 'gc': <config.Config object at 0xa33f8ec>, 'wantref': False}
+    'str': 'abc', 'wantref': False}
 
 We can see that values can also be config objects, it's the
 sub-namespaces that are stored in the values as `Config()` objects.
@@ -69,7 +69,7 @@ With this `config.Config()` configuration management entry point,
 it is possible to
 
 - `iter` on config, notice that there is an iteration order wich is
-  the order of the `optionapi#schema` specification entries,
+  the order of the :ref:`optdescr` specification entries,
 - compare two configs (equality),
 - export the whole config into a `dict` with `config.make_dict()`,
 

doc/getting-started.txt

@@ -16,8 +16,8 @@ What is Tiramisu ?
 
 Tiramisu is yet another configuration handler, wich aims at producing
 flexible and fast configuration options access. The main advantages are
-its access `glossary#rules` and the fact that the configuration 's
-consistency is preserved at any time, see `glossary#consistency`.
+its access rules and the fact that the configuration 's
+consistency is preserved at any time, see :doc:`consistency`.
 
 There are type and structures's validations for configuration options,
 and validations towards the whole configuration.
@@ -47,7 +47,7 @@ directory named ``tiramisu``.
 Understanding Tiramisu's architecture
 --------------------------------------
 
-The `glossary#schema` is loaded from an XML file, and the values of
+The `schema` is loaded from an XML file, and the values of
 the configuration options are recovered from a `.ini` like file.
 
 By now, all the in-depth informations about the configuration are stored

doc/optionapi.txt

@@ -13,6 +13,8 @@ value of the option. If this argument is not supplied the default value
 is assumed to be ``None``.
 
 
+.. _optdescr:
+
 The `OptionDescription` class
 -------------------------------