teruchi
diff --git a/‎book/security.rst
Copy file name to clipboardExpand all lines: book/security.rst
+8-4Lines changed: 8 additions & 4 deletions b/‎book/security.rst
Copy file name to clipboardExpand all lines: book/security.rst
+8-4Lines changed: 8 additions & 4 deletions
@@ -760,12 +760,15 @@ to find *one* that matches the current request. As soon as it finds a matching
 is used to enforce access.
 
 Each ``access_control`` has several options that configure two different
-things: (a) :ref:`should the incoming request match this access control entry<security-book-access-control-matching-options>`
-and (b) :ref:`once it matches, should some sort of access restriction be enforced<security-book-access-control-enforcement-options>`:
+things:
+
+* :ref:`should the incoming request match this access control entry<security-book-access-control-matching-options>`
+* :ref:`once it matches, should some sort of access restriction be enforced<security-book-access-control-enforcement-options>`:
 
 .. _security-book-access-control-matching-options:
 
-**(a) Matching Options**
+Matching Options
+................
 
 Symfony2 creates an instance of :class:`Symfony\\Component\\HttpFoundation\\RequestMatcher`
 for each ``access_control`` entry, which determines whether or not a given
@@ -860,7 +863,8 @@ will match any ``ip``, ``host`` or ``method``:
 
 .. _security-book-access-control-enforcement-options:
 
-**(b) Access Enforcement**
+Access Enforcement
+..................
 
 Once Symfony2 has decided which ``access_control`` entry matches (if any),
 it then *enforces* access restrictions based on the ``roles`` and ``requires_channel``