Index: trunk/kernel/admin/include/help/editgroup_permissions.txt
===================================================================
diff -u -r49 -r158
--- trunk/kernel/admin/include/help/editgroup_permissions.txt	(.../editgroup_permissions.txt)	(revision 49)
+++ trunk/kernel/admin/include/help/editgroup_permissions.txt	(.../editgroup_permissions.txt)	(revision 158)
@@ -1,15 +1,16 @@
-The permissions tab allows the administrator to assign permissions to the group. This is the recommended way of managing user permissions. 
-  The permissions are broken down by type, one for the In-portal administrative console permissions, and one for the front-end. The "Access" check box shows whether a permission is set or unset for the current group. Next to the check box, you will also see a green or a red circle. These circles indicate the active permission state for the group � red means unset, and the green � set. <br><br>The list of the administrative console permissions is as follows: 
-<ul>  
-<li> Admin Login � this permission allows the group member to log in, and to use the administrative console. This permission should be assigned with caution. 
-  <li> Append phpinfo to all pages (Debug) � All permissions, marked with (debug) are used for testing purposes when the code has been modified. They are not necessary, and sometimes distracting, for the daily usage of the console. This permission will display the PHP info page at the top of each page. 
-  <li> Change User Profiles � this permission will allow the group member to view and change other users' profiles on the front end. 
-  <li> Display Item List Queries (Debug) � this debug permission will display the SQL queries above on each list page, after each list operation is performed. 
-  <li> Display Item Queries (Debug) � this debug permission will display the SQL queries for all other actions. 
-  <li> Show Language Tags � this permission will show undefined language variables in the administrative console as links. The link will open up a pop-up for creation of that language variable in the current regional pack. This is a useful permission for enhancing and debugging translations.
-</ul> 
-  The list of the front-end permissions is as follows: 
+
+<p>The permissions tab allows the administrator to assign permissions to the group. This is the recommended way of managing user permissions. </p>
+<p>The permissions are broken down by type, one for the In-portal Administrative Console permissions, and one for the front-end. The �Access' check box shows whether a permission is set or unset for the current group. Next to the check box, you will also see a green or a red circle. These circles indicate the active permission state for the group � red means unset, and the green � set. The list of the administrative console permissions is as follows: </p>
 <ul>
-  <li> Allow Login � this permission will allow the group member to log into the front end of the In-portal site. It is equivalent, for all intents and purposes, to setting a front-end only user's status to "Pending" or "Disabled". The only difference is for users with administrative privileges � "Pending" or "Disabled" user will not be able to log into the administrative console as well, regardless of their "Admin Login" permission setting. 
+<li> Admin Login � this permission allows the group member to log in, and to use the administrative console. This permission should be assigned with caution. 
+<li> Append phpinfo to all pages (Debug) � All permissions, marked with (debug) are used for testing purposes when the code has been modified. They are not necessary, and sometimes distracting, for the daily usage of the console. This permission will display the PHP info page at the top of each page. 
+<li> Change User Profiles � this permission will allow the group member to view and change other users' profiles on the front end. 
+<li> Display Item List Queries (Debug) � this debug permission will display the SQL queries above on each list page, after each list operation is performed. 
+<li> Display Item Queries (Debug) � this debug permission will display the SQL queries for all other actions. 
+<li> Show Language Tags � this permission will show undefined language variables in the administrative console as links. The link will open up a pop-up for creation of that language variable in the current regional pack. This is a useful permission for enhancing and debugging translations. 
+<li> Read-Only Access To Database � this permission will take away user's ability to modify any information in the database when using the Administrative Console. It is useful for demonstration purposes, as well as for setting up administrators who are only supposed to monitor information without actually changing it. 
 </ul>
-  
\ No newline at end of file
+<p>The list of the front-end permissions is as follows: </p>
+<ul>
+<li> Allow Login � this permission will allow the group member to log into the front end of the In-portal site. It is equivalent, for all intents and purposes, to setting a front-end only user's status to �Pending' or �Disabled'. The only difference is for users with administrative privileges � �Pending' or �Disabled' user will not be able to log into the Administrative Console as well, regardless of their �Admin Login' permission setting.
+</ul>
\ No newline at end of file
Index: trunk/kernel/admin/include/help/install.txt
===================================================================
diff -u -r62 -r158
--- trunk/kernel/admin/include/help/install.txt	(.../install.txt)	(revision 62)
+++ trunk/kernel/admin/include/help/install.txt	(.../install.txt)	(revision 158)
@@ -54,7 +54,7 @@
 <p><li> Default META Keywords: Enter text here that will be displayed as a default META keyword tag on the front-end pages. If a category will have its own META keyword tag, it will take precedence over this setting. You may also leave it blank. </p>
 <p><li> Default META description: Enter text here that will be displayed as a default META description tag on the front-end pages. If a category will have its own META description tag, it will take precedence over this setting. You may also leave it blank. </p>
 <h4><li> In-portal Platform Settings, part 4 </h4>
-<p><li> Default Theme: Choose the default theme. The only selection here will be the themes that you have already uploaded to your �in-portal/themes' directory. The default installation of 1.0.4 comes with one theme called �Default'. Additional themes may be available for download on our web site: <a href="http://www.in-portal.net/">http://www.in-portal.net/ </a></p>
+<p><li> Default Theme: Choose the default theme. The only selection here will be the themes that you have already uploaded to your �in-portal/themes' directory. The default installation of 1.0.5 comes with one theme called �Default'. Additional themes may be available for download on our web site: <a href="http://www.in-portal.net/">http://www.in-portal.net/ </a></p>
 <h3><a name="_Toc87037139"><li> Step 9 � Post-Install Configuration </a></h3>
 <p>Congratulations! You have completed your In-portal installation. Clicking �Continue' will take you to your new Administrative Console. </p>
 Please remember to log in with the user name �root' and the password that you have assigned in the step 4.
Index: trunk/kernel/admin/include/help/edituser_permissions.txt
===================================================================
diff -u -r49 -r158
--- trunk/kernel/admin/include/help/edituser_permissions.txt	(.../edituser_permissions.txt)	(revision 49)
+++ trunk/kernel/admin/include/help/edituser_permissions.txt	(.../edituser_permissions.txt)	(revision 158)
@@ -1,14 +1,16 @@
-The permissions tab allows the administrator to assign individual permissions to the user. This is recommended only for exceptional situations, as it complicates user permission management. The standard way of assigning permissions, is to configure a group with the desired set of permissions, and then assign the user to it. 
-  The permissions are broken down by type, one for the In-portal administrative console permissions, and one for the front-end. The �Inherited' check box specifies that a particular permission is inherited from a group that this user belongs to, and therefore cannot be defined for this user. The �Access' check box shows whether a permission is set or unset for the current user. Next to the check box, you will also see a green or a red circle. These circles indicate the active permission state for the user � red means unset, and the green � set. This is especially useful in for the inherited permissions � you do not have to look up all of the groups this user belongs to, to find out what the value of a particular permission is.<br><br> The list of the administrative console permissions is as follows:
-<ul> 
-  <li> Admin Login � this permission allows the user to log in, and to use the administrative console. This permission should be assigned with caution. 
-  <li> Append phpinfo to all pages (Debug) � All permissions, marked with (debug) are used for testing purposes when the code has been modified. They are not necessary, and sometimes distracting, for the daily usage of the console. This permission will display the PHP info page at the top of each page. 
-  <li> Change User Profiles � this permission will allow the user to view and change other users' profiles on the front end. 
-  <li> Display Item List Queries (Debug) � this debug permission will display the SQL queries above on each list page, after each list operation is performed. 
-  <li> Display Item Queries (Debug) � this debug permission will display the SQL queries for all other actions. 
-  <li> Show Language Tags � this permission will show undefined language variables in the administrative console as links. The link will open up a pop-up for creation of that language variable in the current regional pack. This is a useful permission for enhancing and debugging translations.
+
+<p>The permissions tab allows the administrator to assign individual permissions to the user. This is recommended only for exceptional situations, as it complicates user permission management. The standard way of assigning permissions, is to configure a group with the desired set of permissions, and then assign the user to it. </p>
+<p>The permissions are broken down by type, one for the In-portal Administrative Console permissions, and one for the front-end. The �Inherited' check box specifies that a particular permission is inherited from a group that this user belongs to, and therefore cannot be defined for this user. The �Access' check box shows whether a permission is set or unset for the current user. Next to the check box, you will also see a green or a red circle. These circles indicate the active permission state for the user � red means unset, and the green � set. This is especially useful in for the inherited permissions � you do not have to look up all of the groups this user belongs to, to find out what the value of a particular permission is. The list of the administrative console permissions is as follows: </p>
+<ul>
+<li> Admin Login � this permission allows the user to log in, and to use the administrative console. This permission should be assigned with caution. 
+<li> Append phpinfo to all pages (Debug) � All permissions, marked with (debug) are used for testing purposes when the code has been modified. They are not necessary, and sometimes distracting, for the daily usage of the console. This permission will display the PHP info page at the top of each page. 
+<li> Change User Profiles � this permission will allow the user to view and change other users' profiles on the front end. 
+<li> Display Item List Queries (Debug) � this debug permission will display the SQL queries above on each list page, after each list operation is performed. 
+<li> Display Item Queries (Debug) � this debug permission will display the SQL queries for all other actions. 
+<li> Show Language Tags � this permission will show undefined language variables in the administrative console as links. The link will open up a pop-up for creation of that language variable in the current regional pack. This is a useful permission for enhancing and debugging translations. 
+<li> Read-Only Access To Database � this permission will take away user's ability to modify any information in the database when using the Administrative Console. It is useful for demonstration purposes, as well as for setting up administrators who are only supposed to monitor information without actually changing it.
 </ul> 
-  The list of the front-end permissions is as follows: 
+<p>The list of the front-end permissions is as follows: </p>
 <ul>
-  <li> Allow Login � this permission will allow a registered user to log into the front end of the In-portal site. It is equivalent, for all intents and purposes, to setting a front-end only user's status to �Pending' or �Disabled'. The only difference is for users with administrative privileges � �Pending' or �Disabled' user will not be able to log into the administrative console as well, regardless of their �Admin Login' permission setting.
+<li> Allow Login � this permission will allow a registered user to log into the front end of the In-portal site. It is equivalent, for all intents and purposes, to setting a front-end only user's status to �Pending' or �Disabled'. The only difference is for users with administrative privileges � �Pending' or �Disabled' user will not be able to log into the administrative console as well, regardless of their �Admin Login' permission setting. 
 </ul>
\ No newline at end of file
Index: trunk/kernel/admin/include/help/advanced_view.txt
===================================================================
diff -u
--- trunk/kernel/admin/include/help/advanced_view.txt	(revision 0)
+++ trunk/kernel/admin/include/help/advanced_view.txt	(revision 158)
@@ -0,0 +1,4 @@
+The Advanced View section allows you to manage categories and items across all categories. This is especially useful, when you are looking for a particular category or item, if you do not know their location (in which category they are located). One of the most common ways to use the Advanced View section is to review pending items. To do this, simply use the View menu to filter only Pending items of each type. </p>
+<p>In the Advanced View section, you can only manage existing items � delete, edit, approve or deny them. All these actions are the same in this section as they are in the Catalog. To add a new item, please use the Catalog section. </p>
+<p>The Advanced View allows you to filter using the View menu and Search, similar to the Catalog section. The essential difference is that while in the Catalog the filtering options only apply to the current category you are looking at, in the Advanced View section they apply to all of the items of each type. </p>
+<p>The section is divided into tabs, a tab for Categories, and a tab for each module installed on your system. Each tab retains its individual filter settings (Search keyword and View menu options).
\ No newline at end of file