doc/book/en/B0010-define-schema.en.txt
changeset 1163 232aef110a0a
parent 292 2d9e83c34b23
child 1205 79d33f7db590
--- a/doc/book/en/B0010-define-schema.en.txt	Thu Mar 26 09:09:58 2009 +0100
+++ b/doc/book/en/B0010-define-schema.en.txt	Thu Mar 26 11:43:06 2009 +0100
@@ -4,14 +4,15 @@
 ================================
 
 The schema is the core piece of a `CubicWeb` application as it defines
-the data model handled. It is based on entities types already defined
-in the `CubicWeb` standard library and others, more specific, we would 
-expect to find in one or more Python files under the `schema` directory.
+the data model handled. It is based on entity types that are either already
+defined in the `CubicWeb` standard library; or more specific types, that 
+`CubicWeb` expects to find in one or more Python files under the directory 
+`schema`.
 
 At this point, it is important to make clear the difference between
-relation type and relation definition: a relation type is only a relation
+*relation type* and *relation definition*: a *relation type* is only a relation
 name with potentially other additionnal properties (see XXXX), whereas a 
-relation definition is a complete triplet 
+*relation definition* is a complete triplet 
 "<subject entity type> <relation type> <object entity type>". 
 A relation type could have been implied if none is related to a 
 relation definition of the schema.