svn commit: r1424041 - /vcl/site/trunk/content/docs/authorization/administrationconcepts.mdtext

[jf...@apache.org]

Author: jfthomps
Date: Wed Dec 19 19:16:43 2012
New Revision: 1424041

URL: http://svn.apache.org/viewvc?rev=1424041&view=rev
Log:
changed h1s to h2s

Modified:
    vcl/site/trunk/content/docs/authorization/administrationconcepts.mdtext

Modified: vcl/site/trunk/content/docs/authorization/administrationconcepts.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/docs/authorization/administrationconcepts.mdtext?rev=1424041&r1=1424040&r2=1424041&view=diff
==============================================================================
--- vcl/site/trunk/content/docs/authorization/administrationconcepts.mdtext (original)
+++ vcl/site/trunk/content/docs/authorization/administrationconcepts.mdtext Wed Dec 19 19:16:43 2012
@@ -20,7 +20,7 @@ There are several concepts you need to u
 
 [TOC]
 
-#Resources
+##Resources
 
 VCL manages sets of resources. There are four types of resources: images, computers, 
 management nodes, and schedules. Each of these resources types are described below.
@@ -61,7 +61,7 @@ computers in a traditional university co
 the lab is physically closed, but you wouldn't want to be assigning remote users to 
 those computers when the lab is open.
 
-#Groups
+##Groups
 
 Users and resources are placed into groups to make management of them easier.
 
@@ -81,7 +81,7 @@ resources and also to allow VCL to know 
 resources. One example of this is to configure which images can be deployed to which 
 computers. Another example is which management nodes can manage which computers.
 
-#Resource Management
+##Resource Management
 
 VCL needs to know how resources related to one another. This is done by adding the 
 resources to a resource group, and then mapping one type of resource group to another.
@@ -113,7 +113,7 @@ mapping is to partition off parts of you
 users purchase their own hardware to be managed by VCL, you could map only their image 
 groups to their computer groups.
 
-#Privileges
+##Privileges
 
 Users are granted access to parts of the VCL web site and to resources through the 
 Privilege tree. User permissions and resource attributes can both be cascaded down