[Checkins] SVN: zope2docs/trunk/zope2book/source/ using note directive

[Andreas Jung]

Log message for revision 97117:
  using note directive
  

Changed:
  U   zope2docs/trunk/zope2book/source/DTML.rst
  U   zope2docs/trunk/zope2book/source/RelationalDatabases.rst

-=-
Modified: zope2docs/trunk/zope2book/source/DTML.rst
===================================================================
--- zope2docs/trunk/zope2book/source/DTML.rst	2009-02-22 18:18:48 UTC (rev 97116)
+++ zope2docs/trunk/zope2book/source/DTML.rst	2009-02-22 19:58:32 UTC (rev 97117)
@@ -1,20 +1,20 @@
 Basic DTML
 ==========
 
-Preliminary remark (for the Zope 2.12 edition)
-----------------------------------------------
-DTML has been the primary markup language within Zope for a long time.  However
-the *recommended* primary markup language within Zope is nowadays ZPT (Zope
-Page Templates). ZPT is your choice for generating markupish output like HTML
-or XML. The usage of DTML should be limited where you have to generate
-non-markupish output like text files or other formats. Since DTML is pretty old
-it really does not support features like internationalization or unicode very
-well.  In addition the syntax of DTML is not always very easy to understand.
-You have to learn DTML to some point if you intend to use ZSQL methods (for
-RDBMS integration with Zope) - but even for the RDBMS integration we have
-better solutions like Object-Relational-Mappers (check with the chapter about
-relational database connectivity).
 
+.. note::
+    DTML has been the primary markup language within Zope for a long time.  However
+    the *recommended* primary markup language within Zope is nowadays ZPT (Zope
+    Page Templates). ZPT is your choice for generating markupish output like HTML
+    or XML. The usage of DTML should be limited where you have to generate
+    non-markupish output like text files or other formats. Since DTML is pretty old
+    it really does not support features like internationalization or unicode very
+    well.  In addition the syntax of DTML is not always very easy to understand.
+    You have to learn DTML to some point if you intend to use ZSQL methods (for
+    RDBMS integration with Zope) - but even for the RDBMS integration we have
+    better solutions like Object-Relational-Mappers (check with the chapter about
+    relational database connectivity).
+
 Introduction
 ------------
 

Modified: zope2docs/trunk/zope2book/source/RelationalDatabases.rst
===================================================================
--- zope2docs/trunk/zope2book/source/RelationalDatabases.rst	2009-02-22 18:18:48 UTC (rev 97116)
+++ zope2docs/trunk/zope2book/source/RelationalDatabases.rst	2009-02-22 19:58:32 UTC (rev 97117)
@@ -1,20 +1,21 @@
 Relational Database Connectivity
 ================================
 
-Preliminary remark (for the Zope 2.12 edition)
-----------------------------------------------
-This chapter explains you how to access a relational databases directly through
-SQL. The alternative and modern way integrating a RDBMS with Zope is using an
-Object-Relational-Mapper (ORM). An ORM abstracts the SQL layer and allows you
-to deal with database tables, rows etc. like standard Python objects.
 
-The most common and most flexible ORM in the
-Python world is `SQLAlchemy <http://www.sqlalchemy.org>`_ . You can not use
-SQLAlchemy directly within Zope because the transaction system of the RDBMS
-must participate with Zope transaction. This integration layer is implemented
-through the `zope.sqlalchemy <http://pypi.python.org/pypi/zope.sqlalchemy>`_
-module.
+.. note::
 
+    This chapter explains you how to access a relational databases directly through
+    SQL. The alternative and modern way integrating a RDBMS with Zope is using an
+    Object-Relational-Mapper (ORM). An ORM abstracts the SQL layer and allows you
+    to deal with database tables, rows etc. like standard Python objects.
+
+    The most common and most flexible ORM in the
+    Python world is `SQLAlchemy <http://www.sqlalchemy.org>`_ . You can not use
+    SQLAlchemy directly within Zope because the transaction system of the RDBMS
+    must participate with Zope transaction. This integration layer is implemented
+    through the `zope.sqlalchemy <http://pypi.python.org/pypi/zope.sqlalchemy>`_
+    module.
+
 Introduction
 ------------