Fix typos

www.i2p2/pages/i2cp.html

@@ -176,7 +176,7 @@ It should be refactored to pass the Message objects directly.
 </li><li>
 The protocol is highly inefficient, with three I2CP messages for every outgoing message,
 and four I2CP messages for every incoming message.
-Perhaps the acknowledgements and queueing could be eliminated, especially for the in-JVM version.
+Perhaps the acknowledgments and queueing could be eliminated, especially for the in-JVM version.
 This would eliminate a lot of data structures and memory for holding
 unacknowledged messages.
 </li><li>

www.i2p2/pages/supported_applications.html

@@ -430,7 +430,7 @@ subversive, or with similarly counterproductive affectations:
       ><strong
 	>Robert</strong
 	></a
-      > — ua fork of rufus that uses the Basic Open Bridge (BOB) and hasw many improvements, including using the latest wxwidgets and python. It also supports use of seedless if installed for trackerless torrents and magnet-link like fetching of torrents within i2p. <sup
+      > — a fork of rufus that uses the Basic Open Bridge (BOB) and has many improvements, including using the latest wxwidgets and python. It also supports use of seedless if installed for trackerless torrents and magnet-link like fetching of torrents within i2p. <sup
       ><em
 	>[plugin, standalone]</em
 	></sup

www.i2p2/pages/techintro.html

@@ -771,7 +771,7 @@ What other tunnel peer selection and ordering strategies should be available?
     needs for security and anonymity. Rather than building its own content distribution 
     network, Syndie is designed to run on top of existing networks, syndicating 
     content through eepsites, Tor hidden services, Freenet freesites, normal websites, 
-    usenet newgroups, email lists, RSS feeds, etc. Data published with Syndie 
+    usenet newsgroups, email lists, RSS feeds, etc. Data published with Syndie 
     is done so as to offer pseudonymous authentication to anyone reading or archiving 
     it. </p>