>From 9e1bca3d800e03bcfe53ecdc671097b94183098c Mon Sep 17 00:00:00 2001
From: William Liquorce <william@howhill.com>
Date: Fri, 9 Apr 2021 15:00:14 +0100
Subject: [PATCH 5/5] Proofreading changes and corrections to faq.html.j2

---
 template/faq.html.j2 | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/template/faq.html.j2 b/template/faq.html.j2
index 7c395dc..6c9a66a 100644
--- a/template/faq.html.j2
+++ b/template/faq.html.j2
@@ -182,9 +182,9 @@
           <p>
           {% trans %}
           A: There is currently no proxy (like fproxy in Freenet) for GNUnet that would
-          make it accessible with a browser. It is possible to build such a proxy and
-          all one needs to know is the protocol used between browser and proxy and a
-          swift look at the GNUnet code for file-sharing.
+          make it accessible via a browser. It is possible to build such a proxy and
+          all one needs to know is the protocol used between the browser and the proxy and 
+          the GNUnet code for file-sharing.
           {% endtrans %}
           </p>
         </section>
@@ -207,7 +207,7 @@
         </section>
 
         <section>
-          <h3>{{ _("On top of which operating systems does GNUnet run?") }}</h3>
+          <h3>{{ _("Which operating systems does GNUnet run on?") }}</h3>
           <p>
           {% trans %}
           A: GNUnet is being developed and tested primarily under Debian GNU/Linux.
@@ -283,7 +283,7 @@
         </section>
 
         <section>
-          <h3>{{ _("How does GNS compare to other name systems") }}</h3>
+          <h3>{{ _("How does GNS compare to other name systems?") }}</h3>
           <p>
           {% trans %}
           A: A scientific paper on this topic 
@@ -397,8 +397,8 @@
           there are still registrars that determine who owns a name.
           <br><br>
           With GNS, we decentralize the database and also decentralize the
-          responsibility for naming: each user runs his own personal root zone and is
-          thus in complete control of the names he uses. GNS also has many additional
+          responsibility for naming: each user runs their own personal root zone and is
+          thus in complete control of the names they use. GNS also has many additional
           features (to keep names short and enable migration) which don't even make
           sense in the context of CoDoNS.
 
@@ -442,9 +442,9 @@
           A: Handshake is a blockchain-based method for root zone governance.
           Hence, it does not address the name resolution process itself but
           delegates resolution into DNS after the initial TLD resolution.
-          Not taking sustainablility considerations into account, handshake
+          Not taking sustainablility considerations into account, Handshake
           could be used as an additional supporting GNS root zone governance
-          model but we currently do not have such plans in mind.
+          model, but we currently do not have such plans in mind.
           {% endtrans %}
           </p>
         </section>
@@ -918,7 +918,7 @@
           Here, there are differences in terms of application domain and how
           specifically anonymity is achieved.
           Anonymous routing is a hard research topic, so for a superficial
-          comparisson like this one we focus on the latency.
+          comparison like this one we focus on the latency.
           Another important factor is the programming language.
           Type-safe languages may offer certain security benefits; however, this may come at the cost of significant increases in resource consumption which in turn may reduce anonymity.
           {% endtrans %}
-- 
2.25.1