none

1 files changed, 16 insertions, 16 deletions

diff --git a/TWiki/TWikiAccessControl.mdwn b/TWiki/TWikiAccessControl.mdwn
index 9a6edb9d..122f4121 100644
--- a/TWiki/TWikiAccessControl.mdwn
+++ b/TWiki/TWikiAccessControl.mdwn
@@ -1,14 +1,14 @@
 %TOC% %STARTINCLUDE%
 
-## <a name="TWiki_Access_Control"> TWiki Access Control </a>
+# <a name="TWiki_Access_Control"> TWiki Access Control </a>
 
 _Restricting read and write access to topics and webs, by users and groups_
 
-### <a name="Overview"> Overview </a>
+## <a name="Overview"> Overview </a>
 
 [[TWikiAccessControl]] allows you restrict access to single topics and entire webs, by individual user and by user groups, in three main areas: view; edit &amp; attach; and rename/move/delete. These controls, combined with [[TWikiDocumentation]], let you easily create and manage an extremely flexible, fine-grained privilege system.
 
-### <a name="An_Important_Control_Considerati"> An Important Control Consideration </a>
+## <a name="An_Important_Control_Considerati"> An Important Control Consideration </a>
 
 Open, freeform editing is the essence of the %TWIKIWEB%.WikiCulture - it's what makes TWiki different and often more effective than other collaboration tools. So, it is strongly recommended that decisions to restrict read or write access to a web or a topic are made with care. Experience shows that _unrestricted write access_ works very well because:
 
@@ -25,11 +25,11 @@ As a collaboration guideline:
 * Create broad groups (more and varied input), and...
 * Avoid creating view-only users (if you can read it, you can contribute to it).
 
-### <a name="Users_and_Groups"> Users and Groups </a>
+## <a name="Users_and_Groups"> Users and Groups </a>
 
 Access control is based on users and groups. Users are defined by their [[WikiNames]], an then organized into unlimited combinations under different user groups.
 
-#### <a name="Managing_Users"> Managing Users </a>
+### <a name="Managing_Users"> Managing Users </a>
 
 A user is created by with the [TWikiRegistration](%SCRIPTULRPATH%/view%SCRIPTSUFFIX%/TWiki/TWikiRegistration) form. The process generates a topic in the %MAINWEB% web in the new user's [[WikiName]]. The default visitor name is %MAINWEB%.TWikiGuest.
 
@@ -37,7 +37,7 @@ A user is created by with the [TWikiRegistration](%SCRIPTULRPATH%/view%SCRIPTSUF
 
 <a name="ManagingGroups"></a>
 
-#### <a name="Managing_Groups"> Managing Groups </a>
+### <a name="Managing_Groups"> Managing Groups </a>
 
 Groups are defined by group topics in the <code>**%MAINWEB%**</code> web, like the %MAINWEB%.TWikiAdminGroup. To start a new group:
 
@@ -50,11 +50,11 @@ Groups are defined by group topics in the <code>**%MAINWEB%**</code> web, like t
 
 * * ALLOWTOPICCHANGE defines who is allowed to change the group topic; it is a comma delimited list of users and groups. You typically want to restrict that to the members of the group itself, so it should contain the name of the topic,<br /><code>    \* Set ALLOWTOPICCHANGE = %MAINWEB%.TWikiAdminGroup</code><br /> for the TWikiAdminGroup topic. (This prevents users not in the group from editing the topic and from gaining unauthorized membership to the group.)
 
-### <a name="Restricting_Write_Access"> Restricting Write Access </a>
+## <a name="Restricting_Write_Access"> Restricting Write Access </a>
 
 You can define who is allowed to make changes to a web or a topic.
 
-#### <a name="Deny_Editing_by_Topic"> Deny Editing by Topic </a>
+### <a name="Deny_Editing_by_Topic"> Deny Editing by Topic </a>
 
 Denying editing of a topic also restricts attaching files to it; both privileges are assigned together.
 
@@ -68,7 +68,7 @@ Denying editing of a topic also restricts attaching files to it; both privileges
 
 * DENYTOPICCHANGE is evaluated before ALLOWTOPICCHANGE. Access is denied if the authenticated person is in the DENYTOPICCHANGE list, or not in the ALLOWTOPICCHANGE list. Access is granted in case DENYTOPICCHANGE and ALLOWTOPICCHANGE is not defined.
 
-#### <a name="Deny_Editing_by_Web"> Deny Editing by Web </a>
+### <a name="Deny_Editing_by_Web"> Deny Editing by Web </a>
 
 Restricting web-level editing blocks creating new topics, changing topics or attaching files.
 
@@ -81,11 +81,11 @@ The same rules apply as for restricting topics, with these additions:
 * DENYTOPICCHANGE (in topic) overrides DENYWEBCHANGE (in %WEBPREFSTOPIC%)
 * ALLOWTOPICCHANGE (in topic) overrides ALLOWWEBCHANGE (in %WEBPREFSTOPIC%)
 
-### <a name="Restricting_Rename_Access"> Restricting Rename Access </a>
+## <a name="Restricting_Rename_Access"> Restricting Rename Access </a>
 
 You can define who is allowed to rename, move or delete a topic, or rename a web.
 
-#### <a name="Deny_Renaming_by_Topic"> Deny Renaming by Topic </a>
+### <a name="Deny_Renaming_by_Topic"> Deny Renaming by Topic </a>
 
 To allow a user to rename, move or delete a topic, they also need write (editing) permission. They also need write access to change references in referring topics.
 
@@ -99,7 +99,7 @@ To allow a user to rename, move or delete a topic, they also need write (editing
 
 * DENYTOPICRENAME is evaluated before ALLOWTOPICRENAME. Access is denied if the authenticated person is in the DENYTOPICRENAME list, or not in the ALLOWTOPICRENAME list. Access is granted in case DENYTOPICRENAME and ALLOWTOPICRENAME is not defined.
 
-#### <a name="Deny_Renaming_by_Web"> Deny Renaming by Web </a>
+### <a name="Deny_Renaming_by_Web"> Deny Renaming by Web </a>
 
 You can define restrictions of who is allowed to rename a %WIKITOOLNAME% web.
 
@@ -112,7 +112,7 @@ The same rules apply as for topics, with these additions:
 * DENYTOPICRENAME (in topic) overrides DENYWEBRENAME (in %WEBPREFSTOPIC%)
 * ALLOWTOPICRENAME (in topic) overrides ALLOWWEBRENAME (in %WEBPREFSTOPIC%)
 
-### <a name="Restricting_Read_Access"> Restricting Read Access </a>
+## <a name="Restricting_Read_Access"> Restricting Read Access </a>
 
 You can define restrictions of who is allowed to view a %WIKITOOLNAME% web.
 
@@ -120,12 +120,12 @@ You can define restrictions of who is allowed to view a %WIKITOOLNAME% web.
   * Set DENYWEBVIEW = &lt; list of users and groups &gt;
   * Set ALLOWWEBVIEW = &lt; list of users and groups &gt;
 
-#### <a name="Known_Issues"> Known Issues </a>
+### <a name="Known_Issues"> Known Issues </a>
 
 * The view restriction is not suitable for very sensitive content since there is a way to circumvent the read access restriction.
 * Read access restriction only works if the view script is authenticated, that means that users need to log on also just to read topics. [[TWikiDocumentation]] has more on Basic Authentication based on the <code>**.htaccess**</code> file.
 
-##### <a name="Selective_Unrestricted_Web_Acces"> Selective Unrestricted Web Access </a>
+#### <a name="Selective_Unrestricted_Web_Acces"> Selective Unrestricted Web Access </a>
 
 * There is a workaround if you prefer to have unrestricted access to view topics located in normal webs, and to authenticate users only for webs where view restriction is enabled:
   1. **Omit** the <code>**view**</code> script from the `.htaccess` file.
@@ -139,7 +139,7 @@ You can define restrictions of who is allowed to view a %WIKITOOLNAME% web.
 
 <a name="SuperAdminGroup"></a>
 
-### <a name="The_SuperAdminGroup"> The SuperAdminGroup </a>
+## <a name="The_SuperAdminGroup"> The SuperAdminGroup </a>
 
 By mistyping a user or group name in the ALLOWTOPICCHANGE setting, it's possible to lock a topic so that it no-one can edit it from a browser. To avoid this: