# HG changeset patch
# User Aurelien Campeas <aurelien.campeas@logilab.fr>
# Date 1271770513 -7200
# Node ID ecf07370e6db7a4e51e79c0d75b0e79bbd318425
# Parent  49c065ae225e2729d20410a95acab066af585840
[doc/book] a proper note (style)

diff -r 49c065ae225e -r ecf07370e6db doc/book/en/development/datamodel/definition.rst
--- a/doc/book/en/development/datamodel/definition.rst	Tue Apr 20 15:33:09 2010 +0200
+++ b/doc/book/en/development/datamodel/definition.rst	Tue Apr 20 15:35:13 2010 +0200
@@ -381,20 +381,20 @@
   - the permissions `add` and `delete` are equivalent. Only `add`/`read`
     are actually taken in consideration.
 
-:Note on the use of RQL expression for `add` permission:
+.. note::
 
-  Potentially, the use of an RQL expression to add an entity or a
-  relation can cause problems for the user interface, because if the
+  Potentially, the `use of an RQL expression to add an entity or a
+  relation` can cause problems for the user interface, because if the
   expression uses the entity or the relation to create, then we are
   not able to verify the permissions before we actually add the entity
   (please note that this is not a problem for the RQL server at all,
   because the permissions checks are done after the creation). In such
   case, the permission check methods (CubicWebEntitySchema.check_perm
   and has_perm) can indicate that the user is not allowed to create
-  this entity but can obtain the permission.
-  To compensate this problem, it is usually necessary, for such case,
-  to use an action that reflects the schema permissions but which enables
-  to check properly the permissions so that it would show up if necessary.
+  this entity but can obtain the permission.  To compensate this
+  problem, it is usually necessary, for such case, to use an action
+  that reflects the schema permissions but which enables to check
+  properly the permissions so that it would show up if necessary.
 
 
 Use of RQL expression for reading rights