From 97c38f38f9f0ea77ab9ae41473e78068917abe74 Mon Sep 17 00:00:00 2001 From: Thomas Landauer Date: Fri, 18 Nov 2022 18:42:23 +0100 Subject: [PATCH] Merging "list" into text Reason: "a few guidelines" sounded odd, cause the first was no guideline (but a rule), and the second was still no guideline (but more details to first). --- security.rst | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/security.rst b/security.rst index 845b86c3039..ae413392a74 100644 --- a/security.rst +++ b/security.rst @@ -1934,12 +1934,9 @@ database and every user is *always* given at least one role: ``ROLE_USER``:: } This is a nice default, but you can do *whatever* you want to determine which roles -a user should have. Here are a few guidelines: - -* Every role **must start with** ``ROLE_`` (otherwise, things won't work as expected) - -* Other than the above rule, a role is just a string and you can invent what you - need (e.g. ``ROLE_PRODUCT_ADMIN``). +a user should have. The only rule is that every role **must start with** ``ROLE_`` - +otherwise, things won't work as expected. Other than that, a role is just a string +and you can invent whatever you need (e.g. ``ROLE_PRODUCT_ADMIN``). You'll use these roles next to grant access to specific sections of your site.