diff --git a/www.i2p2/pages/applications.html b/www.i2p2/pages/applications.html
index 5d93c69d..34fa9647 100644
--- a/www.i2p2/pages/applications.html
+++ b/www.i2p2/pages/applications.html
@@ -163,6 +163,16 @@ The <a href="streaming.html">full streaming library</a> is now the standard
 interface. It allows programming using TCP-like sockets, as explained in the <a href="#start.streaming">Streaming development guide</a>.
 </p>
 
+<h3>BOB</h3>
+<p>BOB is the <a href="BOB.html">Basic Open Bridge</a>,
+allowing an application in any language to make streaming connections 
+to and from I2P. At this point in time it lacks UDP support, but UDP support
+is planned in the near future. BOB also contains several tools, such as 
+destination key generation, and verification that an address conforms to 
+I2P specifications. Up to date info and applications that use BOB can be 
+found at this <a href="http://bob.i2p/">eepsite</a>.</p>
+
+
 <h3>SAM, SAM V2, SAM V3</h3>
 
 <p><i>SAM is not recommended. SAM V2 is okay, SAM V3 is beta.</i></p>
@@ -179,7 +189,7 @@ and event based handling.  SAM supports three styles of operation:</p>
 </ul>
 <p>SAM V3<p> aims at the same goal as SAM and SAM V2, but does not require
 multiplexing/demultiplexing. Each I2P stream is handled by its own socket between the application
-and the SAM bride. Besides, datagrams can be sent and received by the application through datagram
+and the SAM bridge. Besides, datagrams can be sent and received by the application through datagram
 communications with the SAM bridge.
 
 </p>
@@ -491,7 +501,7 @@ Contact us if you would like to help.
 <a href="http://forum.i2p2.de/viewforum.php?f=25">(outside I2P)</a>
 </li><li>I2PRufus - contact codevoid
 </li><li>I2P-BT - contact sponge
-</li><li>BOB - contact sponge
+</li><li><a href="http://bob.i2p">BOB</a> - contact sponge
 </li></ul>
 
 <h2>Application Ideas</h2>