# HG changeset patch
# User Emile Anclin <emile.anclin@logilab.fr>
# Date 1238691482 -7200
# Node ID 0d5035525a23b88d6ac8475c8fd6930ed4dec4b6
# Parent  d474534fd04d7a24a1835749185cb26e2782df27
[doc] spelling : dictionary

diff -r d474534fd04d -r 0d5035525a23 doc/book/en/B0012-schema-definition.en.txt
--- a/doc/book/en/B0012-schema-definition.en.txt	Thu Apr 02 18:57:24 2009 +0200
+++ b/doc/book/en/B0012-schema-definition.en.txt	Thu Apr 02 18:58:02 2009 +0200
@@ -222,7 +222,7 @@
 ``````````````````````
 
 Setting permissions is done with the attribute `permissions` of entities and
-relation types. It defines a dictionnary where the keys are the access types
+relation types. It defines a dictionary where the keys are the access types
 (action), and the values are the authorized groups or expressions.
 
 For an entity type, the possible actions are `read`, `add`, `update` and
diff -r d474534fd04d -r 0d5035525a23 doc/book/en/B0030-data-as-objects.en.txt
--- a/doc/book/en/B0030-data-as-objects.en.txt	Thu Apr 02 18:57:24 2009 +0200
+++ b/doc/book/en/B0030-data-as-objects.en.txt	Thu Apr 02 18:58:02 2009 +0200
@@ -120,14 +120,14 @@
 
 *rtags* allow to specify certain behaviors of relations relative to a given
 entity type (see later). They are defined on the entity class by the attribute
-`rtags` which is a dictionnary with as keys the triplets ::
+`rtags` which is a dictionary with as keys the triplets ::
 
   <relation type>, <target entity type>, <context position ("subject" ou "object")>
 
 and as values a `set` or a tuple of markers defining the properties that
 apply to this relation.
 
-It is possible to simplify this dictionnary:
+It is possible to simplify this dictionary:
 
 * if we want to specifiy a single marker, it is not necessary to
   use a tuple as value, the marker by itself (character string)
@@ -139,9 +139,9 @@
   we have to use the string `*` as target entity type
 
 
-Please note that this dictionnary is *treated at the time the class is created*.
+Please note that this dictionary is *treated at the time the class is created*.
 It is automatically merged with the parent class(es) (no need to copy the
-dictionnary from the parent class to modify it). Also, modifying it after the 
+dictionary from the parent class to modify it). Also, modifying it after the 
 class is created will not have any effect...
 
 .. include:: B0031-define-entities.en.txt
diff -r d474534fd04d -r 0d5035525a23 doc/book/en/B1060-templates.en.txt
--- a/doc/book/en/B1060-templates.en.txt	Thu Apr 02 18:57:24 2009 +0200
+++ b/doc/book/en/B1060-templates.en.txt	Thu Apr 02 18:58:02 2009 +0200
@@ -181,7 +181,7 @@
   whatever the number of entities to display
 * `__method`, if the result set to render contains only one entity and this 
   parameter is set, it refers to a method to call on the entity by passing it
-  the dictionnary of the forms parameters, before going the classic way (through
+  the dictionary of the forms parameters, before going the classic way (through
   step 1 and 2 described juste above)
 
 The MainTemplate is a bit complex as it tries to accomodate many