Changeset 32

Timestamp:

07/06/07 14:25:16 (5 years ago)

Author:

matighet

Message:

spell check

Files:

• trunk/docs/pbadmin/help_content.html (modified) (10 diffs)

trunk/docs/pbadmin/help_content.html

@@ -350 +350 @@
 
 <p>
-Let us assume that 3 weak checks, A, B and C succeded with weights w1, w2 and w3.
+Let us assume that 3 weak checks, A, B and C succeeded with weights w1, w2 and w3.
 First, we combine them individually. Thus, the first order terms in our aggregation 
 scheme are the individual weights.
@@ -364 +364 @@
 In the example, there is no higher than 3 order terms.
 Clearly, the number of weak checks that succeeded will determine the highest ordered 
-term possible. The current implementation actually limits its computation to upto 3rd 
+term possible. The current implementation actually limits its computation to up to 3rd 
 order terms--even if higher ordered terms are possible, the computation ignores it.
 <p>
 There is a weight assigned to each ordered term. These weights must be chosen such that 
-their sum is 1. In the current implementation, since we consider upto 3rd order terms, 
+their sum is 1. In the current implementation, since we consider up to 3rd order terms, 
 we have 3 weights O1, O2 and O3 such that O2 is highest and O1 is the lowest, but O1 and 
-O3 are close. This weigting implies that we give more credence to the 2nd order terms--
+O3 are close. This weighting implies that we give more credence to the 2nd order terms--
 i.e., if two checks flag an HTTP transaction that is more likely to be bad. 
 If one wants to be more liberal, i.e., need 3 checks to flag in order to be believable, 
@@ -450 +450 @@
 <h3>Starting</h3>
 <p>PhishBouncer&trade; is automatically started by the installer. However, on
-certain platforms (ie Gentoo Linux)
+certain platforms (i.e., Gentoo Linux)
 this is not supported.When restarting, you will be prompted to enter
 the PhishBouncer&trade; Server Passphrase.
@@ -476 +476 @@
 <div class="settings">
 <div class="settings-title">
-<h2><strong>Writing Custom PhishBouncer Plugins</strong></h2>
+<h2><strong>Writing Custom PhishBouncer Plug-ins</strong></h2>
 </div>
 
 <div class="settings-content">
 You can easily extend the existing set of Checks, Probes, and DataCollectors 
-via writing a custom plugin.
+via writing a custom plug-in.
 <br><p>
 
-<h3> Implementing Custom Plugins </h3>
+<h3> Implementing Custom Plug-ins </h3>
 <br><p>
 Take a look at
@@ -492 +492 @@
 pb/src/foo/bar/TestDataCollectorPlugin.java
 </pre>
-for a list of templates on how to implement a custom plugin.
+for a list of templates on how to implement a custom plug-in.
 <br><p>
 
-<h3> Registering Custom Plugins with PhishBouncer </h3>
+<h3> Registering Custom Plug-ins with PhishBouncer </h3>
 <br><p>
 <h4> Changing CLASSPATH </h4>
-Edit jetty/shared.source to include the jars of your custom plugins into the PLUGINS variable
+Edit jetty/shared.source to include the jars of your custom plug-ins into the PLUGINS variable
 
 <br><p>
-<h4> Changing PhishBouncer Plugin File </h4>
-Edit jetty/etc/pb.plugins to include the main of your main plugin class
+<h4> Changing PhishBouncer Plug-in File </h4>
+Edit jetty/etc/pb.plugins to include the main of your main plug-in class
 
 </div>
@@ -518 +518 @@
 <div class="settings-content">
 
-<h3>Certificate Suspicous Tests<br>
+<h3>Certificate Suspicious Tests<br>
 </h3>
 
@@ -567 +567 @@
 2. rm jetty/vergin   (it may already be gone)
 
-3. On the host which runs your webbrowser and phishbouncer proxy, add a local DNS entry for
+3. On the host which runs your web browser and PhishBouncer proxy, add a local DNS entry for
    ip_of_test_server   test1
 
-4. Also, set your system time on the box on which you are running the phishbouner
-   proxy and your webbrowser to July 9 2006.
+4. Also, set your system time on the box on which you are running the PhishBouner
+   proxy and your web browser to July 9 2006.
    On Linux, you can do this via
    date -s "07/09/2006 12:12:00"
@@ -582 +582 @@
 6. For ease of testing, you can create the following file
       echo "key_abc123" > jetty/keyStorePwd
-   This will prevent phishbouncer from asking for a keystore password everytime it starts up.
-
-7. Start up phishbouncer and configure all probes, checks, and dataplugins to be disabled
+   This will prevent PhishBouncer from asking for a keystore password every time it starts up.
+
+7. Start up PhishBouncer and configure all probes, checks, and dataplugins to be disabled
    except for the CertificateSuspicious check. You can do this via the Aggregation menu.
 </pre>
@@ -590 +590 @@
 <h4> Running Tests </h4>
 
-The tests for the certificate suspicous check cover the following
+The tests for the certificate suspicious check cover the following
 functionality:
 <pre>
@@ -645 +645 @@
 <p>Visit the PhishBouncer&trade; <a href="http://www.phishbouncer.com"> Homepage
 </a>, or contact the developers via email to <a
- href="mailto:matighet@bbn.com">matighet@bbn.com</a>.
+ href="mailto:pb@bbn.com">pb@bbn.com</a>.
 <br>
 <br>