[IMP] web: documents the new module system.

This add a basic overview of how the modules work.  This is a work in
progress, more documentation needs to be updated, such as the
tutorial.

1 files changed, 6 insertions, 6 deletions

diff --git a/doc/reference/qweb.rst b/doc/reference/qweb.rst
index 81b3966a0fd..ab2b5313f82 100644
--- a/doc/reference/qweb.rst
+++ b/doc/reference/qweb.rst
@@ -516,13 +516,13 @@ The javascript QWeb implementation provides a few debugging hooks:
 Helpers
 -------
 
-.. js:attribute:: openerp.qweb
+.. js:attribute:: core.qweb
 
-    An instance of :js:class:`QWeb2.Engine` with all module-defined template
+    (core is the ``web.core`` module) An instance of :js:class:`QWeb2.Engine` with all module-defined template
     files loaded, and references to standard helper objects ``_``
     (underscore), ``_t`` (translation function) and JSON_.
 
-    :js:func:`openerp.qweb.render <QWeb2.Engine.render>` can be used to
+    :js:func:`core.qweb.render <QWeb2.Engine.render>` can be used to
     easily render basic module templates
 
 API
@@ -533,9 +533,9 @@ API
     The QWeb "renderer", handles most of QWeb's logic (loading,
     parsing, compiling and rendering templates).
 
-    OpenERP Web instantiates one for the user, and sets it to
-    ``instance.web.qweb``. It also loads all the template files of the
-    various modules into that QWeb instance.
+    OpenERP Web instantiates one for the user in the core module, and 
+    exports it to ``core.qweb``. It also loads all the template files 
+    of the various modules into that QWeb instance.
 
     A :js:class:`QWeb2.Engine` also serves as a "template namespace".