[TWN team] Recent changes to the wiki pages

[Lunar]

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

version 29
Author: karsten
Date:   2014-07-15T19:38:00+00:00

   Make some minor tweaks.

--- version 28
+++ version 29
@@ -17,7 +17,7 @@
 Roundup of research on incentives for running Tor relays
 ---------------------------------------------------------
 
-As an hors-d’œuvre to the now on-going the Privacy Enhancing Technoloy
+As an hors-d’œuvre to the now on-going the Privacy Enhancing Technology
 Symposium [1], Rob Jansen wrote a long blog post covering the
 last five years of research on incentives for running Tor relays [2].
 
@@ -25,11 +25,11 @@
 model” and mentions that “has succeeded so far: Tor now consists of over
 5000 relays transferring between 4 and 5 GiB/s in aggregate”. Rob lists
 several possible reasons why volunteers run relays right now. They are
-all intrisic motivations: current operators run relays because they
+all intrinsic motivations: current operators run relays because they
 really want to.
 
 Is only relying on volunteers going to limit the growth of the Tor
-network in the future? They are already not-for-profit
+network in the future? There are already not-for-profit
 organizations [3] operating relays based on donations, but growing
 them too much would also be problematic. Another area being explored 
 are extrinsic motivations: making Tor clients faster when someone runs a
@@ -39,7 +39,7 @@
 interact with the current set of volunteers.
 
 The problem keeps interesting researchers, and Rob details no less
-than six schemes: the oldest are PAR [5] and Gold Star [6] and which
+than six schemes: the oldest are PAR [5] and Gold Star [6] which
 introduced anonymity problems, BRAIDS [7] where double spending of
 rewards is prevented without leaking timing information, LIRA [8]
 which focused on scalability, TEARS [9] where a publicly auditable
@@ -82,18 +82,18 @@
 “keeping our middle nodes more static”. The idea is to slow down the
 attacks based on repeated circuit destruction by reusing the
 same “middle nodes for 3-4 days instead of choosing new ones for every
-circuit”. Introducing this new behaviour will slow down the attack,
+circuit”. Introducing this new behavior will slow down the attack,
 but George asks “are there any serious negative implications?”
 
 The idea is not new, as Paul Syverson pointed out [14]: “Lasse and I
 suggested and explored the idea of layered guards when we introduced
 guards”. He adds “there are lots of possibilities here”.
 
-George worries than middle nodes would then “always see your traffic
+George worries that middle nodes would then “always see your traffic
 coming through your guard (assuming a single guard per client)”. Ian
 Goldberg added [15] “the exit will now know that circuits coming from
 the same middle are more likely to be the same client”. Restricting the
-change to only hidden services and not every clients mean that it will
+change to only hidden services and not every client means that it will
 be “easy for an entry guard to learn whether a client has static middle
 nodes or not”.
 
@@ -125,8 +125,8 @@
 ------------------
 
 The various roadmaps that came out of the 2014 summer dev. meeting [21]
-has been transcribed [22] in a joint effort by George Kadianakis,
-Yawning Angel, Karsten Loesing and an anonymous person. Most items
+have been transcribed [22] in a joint effort by George Kadianakis,
+Yawning Angel, Karsten Loesing, and an anonymous person. Most items
 will probably be matched with a ticket soon. 
 
   [21]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014SummerDevMeeting
@@ -201,7 +201,7 @@
 Users often ask about for assistance setting up Tor Cloud instances.
 Sina Rabbani is taking over the maintenance of Tor Cloud and is working
 on updating the packages and documentation. Until new documentation
-on using the up-to-date  images and Amazon Web Services interface lands,
+on using the up-to-date images and Amazon Web Services interface lands,
 users not already familiar with AWS may want to use a different virtual
 server provider to host their bridges.
 



-- 
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.