nits

Author: vladak

doc/authorization_howto.txt

@@ -1,5 +1,5 @@
 Using OpenGrok authorization
-------------------------
+----------------------------
 
 This howto provides information about opengrok authorization with authorization framework.
 You can use this package along with project groupings (merged before) which allows
@@ -15,7 +15,9 @@ Configuration
 --------------
 
 You can configure:
+
 1) Plugin directory
+
     In web.xml for the webapp, there is a context parameter dedicated to this.
 
       <context-param>
@@ -26,14 +28,15 @@ You can configure:
               Default value is OPENGROK_DATA_ROOT/plugins
           </description>
       </context-param>
-  
+
     It is commented out by default so that the framework does not do anything.
     The OPENGROK_DATA_ROOT is the dataRoot directory set in configuration.xml.
 
     Opengrok authorization expects plugin classes in that directory, it loads those classes in
     memory as plugins and then perform the authorization for each request.
 
 2) Watchdog service
+
     For easier development there is another context parameter in web.xml.
 
       <context-param>
@@ -51,7 +54,8 @@ You can configure:
     plugin directory are loaded.
 
 3) Provide a plugin
-    You can provide your own plugin by putting the compiled 
+
+    You can provide your own plugin by putting the compiled
     plugin class (.class or in .jar) into plugin directory.
 
 
@@ -116,8 +120,8 @@ Also JVM can forbid you to extend some packages which are not meant to be extend
 Set up
 ------
 
-The plugin class must be compiled to the .class file (and the it can be packaged into .jar file).
-The frameworks supports both .class and .jar files.
+The plugin class must be compiled to the .class file (and then it can be packaged into .jar file).
+The framework supports both .class and .jar files.
 For compiling you have to provide opengrok.jar in the classpath
 
 Example (for the SampleAuthorizationPlugin which is included):
@@ -127,12 +131,12 @@ Then you can just drop the compiled .class file into plugin directory and deploy
 If the plugin is a part of a package. Then you have to copy the full directory path which is made
 by the compiler relatively to the source file.
 
-If anything goes wrong, you should find information in the logs.
+If anything goes wrong, you will find information in the logs.
 
 Running
 -------
 
-The framework consists of three parts
+The framework consists of three parts:
 
 1) PluginFramework
     Plugin container
@@ -155,4 +159,4 @@ The framework consists of three parts
 
 Every 403 error is logged. But information about the user is missing
 because the decision is made by plugins and the filter does not know
-how to interpret the request to get the user from it.
+how to interpret the request to get the user from it.