# HG changeset patch
# User Laurent Peuch <cortex@worlddomination.be>
# Date 1550771663 -3600
# Node ID 76c9ced6b3cc437b8b3898aab0675d17eb8b27a5
# Parent  72536c93f3c1262ae9a35336f3d1275dc9ac2f8b
[doc] style, switch to bullet points list to make things easier to read

diff -r 72536c93f3c1 -r 76c9ced6b3cc doc/tutorials/advanced/part02_security.rst
--- a/doc/tutorials/advanced/part02_security.rst	Thu Feb 21 18:53:39 2019 +0100
+++ b/doc/tutorials/advanced/part02_security.rst	Thu Feb 21 18:54:23 2019 +0100
@@ -21,10 +21,12 @@
 * only authenticated users can see people
 * everyone can see classifier entities, such as tag and zone
 
-Also, unless explicitly specified, the visibility of an image should be the same as
-its parent folder, as well as visibility of a comment should be the same as the
-commented entity. If there is no parent entity, the default visibility is
-``authenticated``.
+Also:
+
+* unless explicitly specified, the visibility of an image should be the same as
+its parent folder
+* the visibility of a comment should be the same as the commented entity
+* If there is no parent entity, the default visibility is ``authenticated``.
 
 Regarding write security, that's much easier:
 
@@ -42,10 +44,13 @@
 Step 1: configuring security into the schema
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-In schema, you can grant access according to groups, or to some RQL expressions:
-users get access if the expression returns some results. To implement the read
-security defined earlier, groups are not enough, we'll need some RQL expression. Here
-is the idea:
+In the schema, you can grant access according to:
+
+* groups
+* to some RQL expressions: users get access if the expression returns some results
+
+To implement the read security defined earlier, groups are not enough, we'll
+need some RQL expression. Here is the idea:
 
 * add a `visibility` attribute on Folder, File and Comment, which may be one of
   the value explained above