[Checkins] SVN: bluebream/website/docs/v1.0/tutorial1.rst why we need schemas ?

[Baiju M]

Log message for revision 108203:
  why we need schemas ?
  

Changed:
  U   bluebream/website/docs/v1.0/tutorial1.rst

-=-
Modified: bluebream/website/docs/v1.0/tutorial1.rst
===================================================================
--- bluebream/website/docs/v1.0/tutorial1.rst	2010-01-18 05:06:23 UTC (rev 108202)
+++ bluebream/website/docs/v1.0/tutorial1.rst	2010-01-18 05:25:11 UTC (rev 108203)
@@ -571,6 +571,16 @@
 Declaring Interface
 ~~~~~~~~~~~~~~~~~~~
 
+From the overview of introduction chapter, you must be noticed, one
+of the important BlueBream feature: BlueBream has transactional
+object database (:term:`ZODB`).  This is the reason why relational
+database connectivity and ORMs are not discussed yet.  BlueBream
+recommend to use the Python based object database called ZODB for
+storing data.  BlueBream makes it easy to do this.  In this section,
+you will see the basic steps you need to make your objects
+persistent.  Having a well defined schema for all objects (data) is
+good idea.
+
 As the first step for creating the main application container object
 which is going to hold all other objects, you need to create an
 interface.  You can name the main container interface as
@@ -598,8 +608,8 @@
           default=u"",
           required=False)
 
-The interface defined is your schema for the object.  There are two
-fields defined in the schema.  The first one is ``name`` and the
+The interface defined here is your schema for the object.  There are
+two fields defined in the schema.  The first one is ``name`` and the
 second one is ``description``.  The schema is used for
 auto-generating web forms.