Replace all references to eepSite with I2P Site

i2p2www/blog/2006/01/03/status.html

@@ -71,7 +71,7 @@ Saying 2005 broke a lot of ground is a bit of an understatement -
 we've improved I2P numerous ways in the 25 releases last year,
 grew the network 5-fold, deployed several new client applications
 (Syndie, I2Phex, I2PSnark, I2PRufus), migrated to postman's and
-cervantes' new irc2p IRC network, and saw some useful I2P sites
+cervantes' new irc2p IRC network, and saw some useful I2P Sites
 bloom (such as zzz's stats.i2p, orion's orion.i2p, and tino's proxy
 and monitoring services, just to name a few).  The community has
 also matured a bit more, in no small part thanks to the support

i2p2www/blog/2006/01/10/status.html

@@ -95,7 +95,7 @@ long requested feature - support for persistent HTTP connections,
 allowing you to send multiple HTTP requests over a single stream,
 receiving multiple replies in return.  I think someone first asked
 for this two years ago or so, and it could help with some types of
-I2P site or outproxying a bunch.  I know the work isn't done yet, but
+I2P Site or outproxying a bunch.  I know the work isn't done yet, but
 its coming along.  Hopefully zzz can give us a status update during
 the meeting.
 

i2p2www/blog/2006/08/01/status.html

@@ -10,7 +10,7 @@ large I2PSnark transfers completing, and with quite sustantial
 transfer rates achieved on individual routers - I've seen
 650KBytes/sec and 17,000 participating tunnels without any
 fireworks.  Routers on the low end of the spectrum seem to be
-doing fine too, browsing I2P sites and irc with 2 hop tunnels
+doing fine too, browsing I2P Sites and irc with 2 hop tunnels
 using under 1KByte/sec average.
 
 It isn't all roses for everyone though, but we're working through
@@ -26,11 +26,11 @@ we are not reverting to TCP-only.
 
 * I2P Site reachability
 
-Remember folks that I2P sites are reachable only when the person
+Remember folks that I2P Sites are reachable only when the person
 who is running it has it up - if they're down, there's nothing
 you can do to reach it ;)  Unfortunately, for the past few days,
 orion.i2p hasn't been reachable, but the net is definitely still
-working - perhaps swing by inproxy.tino.i2p or I2P sites.i2p for
+working - perhaps swing by inproxy.tino.i2p or I2P Sites.i2p for
 your network survey needs.
 
 Anyway, there's lots more going on, but it'd be a bit premature

i2p2www/blog/2006/10/03/status.html

@@ -133,7 +133,7 @@ being worked on.  First, from irc (and the not-yet-out-there FAQ):
 
  <bar> a question i've been pondering is, who is later going to have
        balls big enough to host syndie production servers/archives?
- <bar> aren't those going to be as easy to track down as the I2P sites
+ <bar> aren't those going to be as easy to track down as the I2P Sites
        are today?
  <jrandom> public syndie archives do not have the ability to
        *read* the content posted to forums, unless the forums publish