spelling fix, date fix

data/entries.html

@@ -3,7 +3,7 @@
 <article
   id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e"
   title="I2P 2.6.0 Released"
-  href="http://i2p-projekt.i2p/en/blog/post/2024/07/15/i2p_2.6.0_released"
+  href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released"
   author="idk"
   published="2024-07-19T22:00:00Z"
   updated="2024-07-19T22:00:00Z">
@@ -15,7 +15,7 @@ This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and
 </p>
 <p>
 Newer routers will be favored when selecting floodfill routers.
-I2PSnark recieved features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
+I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
 Legacy transport protocols are being removed, simplifying the code in the UDP transports.
 Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
 Additional tweaks were made to peer selection strategies.
@@ -24,7 +24,7 @@ Additional tweaks were made to peer selection strategies.
 I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
 We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
 If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
-Non-Exit relays and Tor clients are unaffected by this and do not need to change anything.
+Non-exit relays and Tor clients are unaffected by this and do not need to change anything.
 </p>
 <p>
 As usual, we recommend that you update to this release.