[TWN team] Recent changes to the wiki pages

[Lunar]

===========================================================================
=== https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews/2014/25 ===
===========================================================================

version 50
Author: harmony
Date:   2014-06-24T13:36:59+00:00

   and another/remove double space

--- version 49
+++ version 50
@@ -47,7 +47,7 @@
 repositories from 0.2.3.25 to 0.2.4.22. Among the chief motives for
 doing so is that “about a quarter of the Tor network (just considering
 the relays, not any clients), is on 0.2.3.25, presumably because they
-run Debian stable.  If they all upgraded to the 0.2.4.x tree, the
+run Debian stable. If they all upgraded to the 0.2.4.x tree, the
 network as a whole would become a lot more secure as 0.2.4.x allows
 clients to use stronger crypto for connections built through these
 nodes.” Other benefits, including the various measures taken to defend
@@ -167,7 +167,7 @@
 If the Tor Browser stalls while “loading the network status”, please
 double-check that the system clock is accurate; the same goes for the
 timezone and daylight saving time settings. Tor needs an accurate clock
-in order to prevent several class of attacks on its protocol. It won’t
+in order to prevent several classes of attacks on its protocol. It won’t
 work properly when the local time does not match the one used by other
 network participants.
 

version 49
Author: harmony
Date:   2014-06-24T13:33:02+00:00

   one more

--- version 48
+++ version 49
@@ -31,7 +31,7 @@
 
 You can download the source tarball [3], or install the package by
 following the instructions for your system [4]. This release is also now
-available in Debian’s [5] and Tor Project’s repository [6].
+available in the Debian [5] and Tor Project [6] repositories.
 
    [2]: https://lists.torproject.org/pipermail/tor-talk/2014-June/033347.html
    [3]: https://www.torproject.org/dist/

version 48
Author: harmony
Date:   2014-06-24T13:30:45+00:00

   language fixes

--- version 47
+++ version 48
@@ -144,19 +144,19 @@
   [32]: https://crypto.stanford.edu/flashproxy/
   [33]: https://packages.debian.org/sid/pt-websocket
 
-A couple weeks ago Roger Dingledine wondered “how many relays are
+A couple of weeks ago, Roger Dingledine wondered “how many relays are
 firewalling certain outbound ports (and thus messing with connectivity
 inside the Tor network)”. ra has just published the results [34] of a
-three weeks long test of the interconnectivity between 6730 relays.
-Contacting the relay operators of the problematic relay is probably the
-next step for who wish to keep the network at its best.
+three-week-long test of the interconnectivity between 6730 relays.
+Contacting the operators of problematic relays is probably the next step
+for those who wish to keep the network at its best.
 
   [34]: https://bugs.torproject.org/12131#comment:11
 
 George Kadianakis slipped on his storyteller costume to guide us [35]
 through layers of the Tor core, motivated by the quest for knowledge.
-The cursing riddle, “Why does Roger has so many guards?”, has now an
-answer. Be ready for a “beautiful stalagmite” and the “truly amazing”
+That accursed riddle, “Why does Roger have so many guards?”, now has an
+answer. Be prepared for a “beautiful stalagmite” and the “truly amazing”
 nature of Tor!
 
   [35]: https://lists.torproject.org/pipermail/tor-dev/2014-June/007042.html
@@ -164,12 +164,12 @@
 Tor help desk roundup
 ---------------------
 
-When the Tor Browser stalls while “loading the network status”, please
-double check that the system clock is accurate. Same for the timezone
-and daylight saving change. Tor needs an accurate clock to prevent from
-several class of attacks on its protocol. It won’t work properly when
-the local time does not match the one used by other network
-participants.
+If the Tor Browser stalls while “loading the network status”, please
+double-check that the system clock is accurate; the same goes for the
+timezone and daylight saving time settings. Tor needs an accurate clock
+in order to prevent several class of attacks on its protocol. It won’t
+work properly when the local time does not match the one used by other
+network participants.
 
 Easy development tasks to get involved with
 -------------------------------------------
@@ -180,8 +180,8 @@
 the listener. One warning should be enough. We had a friendly volunteer
 two years ago who sketched out possible fixes and even wrote a patch,
 but then concluded that his patch had a problem and went away. If you’re
-up to some digging into tor’s configuration file handling and want to
-clean up a two years old patch potentially to be included in tor 0.2.6,
+up to some digging into tor’s configuration file handling, and want to
+clean up a two-year-old patch potentially to be included in tor 0.2.6,
 please find the details in the ticket [36]. It’s tagged as easy, so how
 hard can it be?
 



-- 
Your friendly TWN monitoring script

      In case of malfunction, please reach out for lunar at torproject.org
          or for the worst cases, tell weasel at torproject.org to kill me.