aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMartin Schanzenbach <mschanzenbach@posteo.de>2021-04-14 10:59:47 +0200
committerMartin Schanzenbach <mschanzenbach@posteo.de>2021-04-14 10:59:47 +0200
commitfd2a64bcaea97ca8a515c989fa89f6642da987a8 (patch)
tree4f49f068ba9c60c8af90dcdee4c9991644d7887f
parent775a35088e6aa7a96cf356bd0617910e46ea9831 (diff)
downloadwww-fd2a64bcaea97ca8a515c989fa89f6642da987a8.tar.gz
www-fd2a64bcaea97ca8a515c989fa89f6642da987a8.zip
Add spelling corrections by William Liquorice
-rw-r--r--template/applications.html.j26
-rw-r--r--template/architecture.html.j210
-rw-r--r--template/engage.html.j212
-rw-r--r--template/ev.html.j24
-rw-r--r--template/faq.html.j220
5 files changed, 26 insertions, 26 deletions
diff --git a/template/applications.html.j2 b/template/applications.html.j2
index 43b0dd2f..1b47258a 100644
--- a/template/applications.html.j2
+++ b/template/applications.html.j2
@@ -19,7 +19,7 @@
19 hierarchy, GNS uses a directed graph. Naming conventions 19 hierarchy, GNS uses a directed graph. Naming conventions
20 are similar to DNS, but queries and replies are private even 20 are similar to DNS, but queries and replies are private even
21 with respect to peers providing the answers. The integrity of 21 with respect to peers providing the answers. The integrity of
22 records and privacy of look-ups is cryptographically secured. 22 records and privacy of look-ups are cryptographically secured.
23 <!-- Too technical: GNS integrates 23 <!-- Too technical: GNS integrates
24 a robust, efficient and instant key revocation mechanism. --> 24 a robust, efficient and instant key revocation mechanism. -->
25 {% endtrans %} 25 {% endtrans %}
@@ -162,7 +162,7 @@
162 {% trans %} 162 {% trans %}
163 <a href="https://gitlab.com/gnunet-messenger/cadet-gtk">Cadet-GTK</a> 163 <a href="https://gitlab.com/gnunet-messenger/cadet-gtk">Cadet-GTK</a>
164 is a convenient but feature-rich graphical application 164 is a convenient but feature-rich graphical application
165 providing messaging using especially the CADET subsystem. It is 165 providing messaging using the CADET subsystem. It is
166 developed using GTK and libhandy for a convergent design. 166 developed using GTK and libhandy for a convergent design.
167 {% endtrans %} 167 {% endtrans %}
168 </p> 168 </p>
@@ -181,7 +181,7 @@
181 <p> 181 <p>
182 {% trans %} 182 {% trans %}
183 <a href="https://git.gnunet.org/groupchat.git/">groupchat</a> 183 <a href="https://git.gnunet.org/groupchat.git/">groupchat</a>
184 is a terminal user interface providing messaging using especially the CADET subsystem. It is 184 is a terminal user interface providing messaging using the CADET subsystem. It is
185 developed using nim. Cadet-GTK and groupchat are planned to be compatible. 185 developed using nim. Cadet-GTK and groupchat are planned to be compatible.
186 {% endtrans %} 186 {% endtrans %}
187 </p> 187 </p>
diff --git a/template/architecture.html.j2 b/template/architecture.html.j2
index 4165c860..04067749 100644
--- a/template/architecture.html.j2
+++ b/template/architecture.html.j2
@@ -25,7 +25,7 @@
25 messaging layer (CADET), a public key infrastructure 25 messaging layer (CADET), a public key infrastructure
26 (GNS) and a pluggable transport system (TRANSPORT).<br> 26 (GNS) and a pluggable transport system (TRANSPORT).<br>
27 Using public keys for addresses 27 Using public keys for addresses
28 and self-organized decentralized routing algorithms, 28 and self-organizing decentralized routing algorithms,
29 these subsystems replace the traditional TCP/IP stack. 29 these subsystems replace the traditional TCP/IP stack.
30 {% endtrans %} 30 {% endtrans %}
31 </p> 31 </p>
@@ -38,7 +38,7 @@
38 {% trans %} 38 {% trans %}
39 GNUnet is implemented using a multi-process architecture. 39 GNUnet is implemented using a multi-process architecture.
40 Each subsystem runs as a separate process, providing 40 Each subsystem runs as a separate process, providing
41 fault-isolation and enabling tight permissions to be 41 fault isolation and enabling tight permissions to be
42 granted to each subsystem. Naturally, the 42 granted to each subsystem. Naturally, the
43 implementation is a <a href="https://www.gnu.org/">GNU</a> 43 implementation is a <a href="https://www.gnu.org/">GNU</a>
44 package, and will always remain free software. 44 package, and will always remain free software.
@@ -51,13 +51,13 @@
51 <div class="col-md"> 51 <div class="col-md">
52 <h2>{{ _("System architecture") }}</h2> 52 <h2>{{ _("System architecture") }}</h2>
53 <p> 53 <p>
54 Read more about the system architecure in the respective section of our <a href="https://docs.gnunet.org/handbook/gnunet.html#System-Architecture" target="_blank">handbook</a>. 54 Read more about the system architecture in the corresponding section of our <a href="https://docs.gnunet.org/handbook/gnunet.html#System-Architecture" target="_blank">handbook</a>.
55 </p> 55 </p>
56 </div> 56 </div>
57 <div class="col-md"> 57 <div class="col-md">
58 <h2>{{ _("Subsystems") }}</h2> 58 <h2>{{ _("Subsystems") }}</h2>
59 <p> 59 <p>
60 Read more about the subsystems (or GNUnet services) in the respective section of our <a href="https://docs.gnunet.org/handbook/gnunet.html#Code-overview" target="_blank">handbook</a>. 60 Read more about the subsystems (or GNUnet services) in the corresponding section of our <a href="https://docs.gnunet.org/handbook/gnunet.html#Code-overview" target="_blank">handbook</a>.
61 </p> 61 </p>
62 </div> 62 </div>
63 </div> 63 </div>
@@ -72,7 +72,7 @@
72 <div class="col-md"> 72 <div class="col-md">
73 <h2>{{ _("APIs") }}</h2> 73 <h2>{{ _("APIs") }}</h2>
74 <p> 74 <p>
75 GNUnet offers variaty of APIs for <a href="https://docs.gnunet.org/handbook/gnunet.html#Interprocess-communication-API-_0028IPC_0029" target="_blank">accessing services</a> (using IPC), <a href="https://docs.gnunet.org/handbook/gnunet.html#Service-API">running services</a>, <a href="https://docs.gnunet.org/handbook/gnunet.html#Message-Queue-API">message queues</a>, or <a href="https://docs.gnunet.org/handbook/gnunet.html#Cryptography-API" target="_blank">cryptographic operations</a>. 75 GNUnet offers a variety of APIs for <a href="https://docs.gnunet.org/handbook/gnunet.html#Interprocess-communication-API-_0028IPC_0029" target="_blank">accessing services</a> (using IPC), <a href="https://docs.gnunet.org/handbook/gnunet.html#Service-API">running services</a>, <a href="https://docs.gnunet.org/handbook/gnunet.html#Message-Queue-API">message queues</a>, or <a href="https://docs.gnunet.org/handbook/gnunet.html#Cryptography-API" target="_blank">cryptographic operations</a>.
76 </p> 76 </p>
77 </div> 77 </div>
78 </div> 78 </div>
diff --git a/template/engage.html.j2 b/template/engage.html.j2
index 000396ab..5bbaf9f3 100644
--- a/template/engage.html.j2
+++ b/template/engage.html.j2
@@ -26,14 +26,14 @@
26 </p> 26 </p>
27 <h4>Mumble</h4> 27 <h4>Mumble</h4>
28 <p> 28 <p>
29 We have a monthly get-together on mumble where we talk about recent developments, strategies, and politics.<br> 29 We have a monthly get-together on Mumble where we talk about recent developments, strategies, and politics.<br>
30 We come together on that day of the month, where n.day==n.month. E.g. we’ll meet on 6th of June, 7th of July, 8th of August, 9th of September, 10th of October and so on. We will usually start around 8 PM CEST, but try to be there earlier and stay longer just to hang around together.<br> 30 We come together on that day of the month, where n.day==n.month. E.g. we’ll meet on 6th of June, 7th of July, 8th of August, 9th of September, 10th of October and so on. We will usually start around 8 PM CEST, but try to be there earlier and stay longer just to hang around together.<br>
31 To connect just enter "gnunet.org" as server into your mumble client; leave everything else as default. 31 To connect just enter "gnunet.org" as server into your Mumble client; leave everything else as default.
32 </p> 32 </p>
33 </p> 33 </p>
34 <h4>PSYC</h4> 34 <h4>PSYC</h4>
35 <p> 35 <p>
36 You find some of us on PSYC using the following adresses: 36 You find some of us on PSYC using the following adresses:
37 <ul> 37 <ul>
38 <li>psyc://loupsycedyglgamf.onion/@welcome</li> 38 <li>psyc://loupsycedyglgamf.onion/@welcome</li>
39 <li>irc://loupsycedyglgamf.onion:67/welcome</li> 39 <li>irc://loupsycedyglgamf.onion:67/welcome</li>
@@ -46,7 +46,7 @@
46 <div class="col-md"> 46 <div class="col-md">
47 <h2>Install GNUnet!</h2> 47 <h2>Install GNUnet!</h2>
48 <p> 48 <p>
49 Another thing you might want now is your own GNUnet installation. As we haven’t packaged the new versions yet (June 2019) we provide <a href="https://gnunet.org/en/install.html">some tutorials how to install step-by-step</a>. 49 Another thing you might want now is your own GNUnet installation. As we haven’t packaged the new versions yet (as of June 2019) we provide <a href="https://gnunet.org/en/install.html">some tutorials how to install step-by-step</a>.
50 </p> 50 </p>
51 <h2>Use GNUnet!</h2> 51 <h2>Use GNUnet!</h2>
52 <p> 52 <p>
@@ -62,8 +62,8 @@
62 <li>If you do not want to use the public bug tracker, you can also eMail to bug-gnunet@gnu.org.</li> 62 <li>If you do not want to use the public bug tracker, you can also eMail to bug-gnunet@gnu.org.</li>
63 <li>Please inform us if your operating system or package manager applies any vendor changes to GNUnet which you know about (to exclude potential problems introduced by third parties).</li> 63 <li>Please inform us if your operating system or package manager applies any vendor changes to GNUnet which you know about (to exclude potential problems introduced by third parties).</li>
64 <li>Wait until your bug report is acknowledged/replied to. Note that only volunteers work on this, responses may take a while.</li> 64 <li>Wait until your bug report is acknowledged/replied to. Note that only volunteers work on this, responses may take a while.</li>
65 <li>Please follow up with eventual questions about the bug. </li> 65 <li>Please follow up on any questions about the bug.</li>
66 <li>Once a fix is there: Check if it&#39;s working as expected, so that we can properly close the bug report and/or give you credits :)</li> 66 <li>Once a fix is there: Check if it&#39;s working as expected, so that we can properly close the bug report and/or give you credit :)</li>
67 </ul> 67 </ul>
68 <h2>Contribute!</h2> 68 <h2>Contribute!</h2>
69 <p> 69 <p>
diff --git a/template/ev.html.j2 b/template/ev.html.j2
index d8589b11..d35480f4 100644
--- a/template/ev.html.j2
+++ b/template/ev.html.j2
@@ -40,7 +40,7 @@
40 to support GNUnet e.V. and in particularly contribute to the 40 to support GNUnet e.V. and in particularly contribute to the
41 technical development within their means. For further 41 technical development within their means. For further
42 details, we refer to the 42 details, we refer to the
43 <a href="https://git.gnunet.org/gnunet-ev.git/">Satzung</a> 43 <a href="https://git.gnunet.org/gnunet-ev.git/">Satzung (Charter)</a>
44 (currently only available in German, translations welcome). 44 (currently only available in German, translations welcome).
45 {% endtrans %} 45 {% endtrans %}
46 </p> 46 </p>
@@ -52,7 +52,7 @@
52 <h3>{{ _("Governance") }}</h3> 52 <h3>{{ _("Governance") }}</h3>
53 <p> 53 <p>
54 {% trans %} 54 {% trans %}
55 You can find our "Satzung", and the list of members under 55 You can find our charter, and the list of members under
56 <a href="https://git.gnunet.org/gnunet-ev.git/tree/satzung.tex">https://git.gnunet.org/gnunet-ev.git/tree/satzung.tex</a>. 56 <a href="https://git.gnunet.org/gnunet-ev.git/tree/satzung.tex">https://git.gnunet.org/gnunet-ev.git/tree/satzung.tex</a>.
57 The current board consists of: 57 The current board consists of:
58 <dl><dt>Vorsitz</dt> 58 <dl><dt>Vorsitz</dt>
diff --git a/template/faq.html.j2 b/template/faq.html.j2
index 7c395dc0..67811b52 100644
--- a/template/faq.html.j2
+++ b/template/faq.html.j2
@@ -182,9 +182,9 @@
182 <p> 182 <p>
183 {% trans %} 183 {% trans %}
184 A: There is currently no proxy (like fproxy in Freenet) for GNUnet that would 184 A: There is currently no proxy (like fproxy in Freenet) for GNUnet that would
185 make it accessible with a browser. It is possible to build such a proxy and 185 make it accessible via a browser. It is possible to build such a proxy and
186 all one needs to know is the protocol used between browser and proxy and a 186 all one needs to know is the protocol used between the browser and the proxy and
187 swift look at the GNUnet code for file-sharing. 187 the GNUnet code for file-sharing.
188 {% endtrans %} 188 {% endtrans %}
189 </p> 189 </p>
190 </section> 190 </section>
@@ -207,7 +207,7 @@
207 </section> 207 </section>
208 208
209 <section> 209 <section>
210 <h3>{{ _("On top of which operating systems does GNUnet run?") }}</h3> 210 <h3>{{ _("Which operating systems does GNUnet run on?") }}</h3>
211 <p> 211 <p>
212 {% trans %} 212 {% trans %}
213 A: GNUnet is being developed and tested primarily under Debian GNU/Linux. 213 A: GNUnet is being developed and tested primarily under Debian GNU/Linux.
@@ -283,7 +283,7 @@
283 </section> 283 </section>
284 284
285 <section> 285 <section>
286 <h3>{{ _("How does GNS compare to other name systems") }}</h3> 286 <h3>{{ _("How does GNS compare to other name systems?") }}</h3>
287 <p> 287 <p>
288 {% trans %} 288 {% trans %}
289 A: A scientific paper on this topic 289 A: A scientific paper on this topic
@@ -397,8 +397,8 @@
397 there are still registrars that determine who owns a name. 397 there are still registrars that determine who owns a name.
398 <br><br> 398 <br><br>
399 With GNS, we decentralize the database and also decentralize the 399 With GNS, we decentralize the database and also decentralize the
400 responsibility for naming: each user runs his own personal root zone and is 400 responsibility for naming: each user runs their own personal root zone and is
401 thus in complete control of the names he uses. GNS also has many additional 401 thus in complete control of the names they use. GNS also has many additional
402 features (to keep names short and enable migration) which don't even make 402 features (to keep names short and enable migration) which don't even make
403 sense in the context of CoDoNS. 403 sense in the context of CoDoNS.
404 404
@@ -442,9 +442,9 @@
442 A: Handshake is a blockchain-based method for root zone governance. 442 A: Handshake is a blockchain-based method for root zone governance.
443 Hence, it does not address the name resolution process itself but 443 Hence, it does not address the name resolution process itself but
444 delegates resolution into DNS after the initial TLD resolution. 444 delegates resolution into DNS after the initial TLD resolution.
445 Not taking sustainablility considerations into account, handshake 445 Not taking sustainablility considerations into account, Handshake
446 could be used as an additional supporting GNS root zone governance 446 could be used as an additional supporting GNS root zone governance
447 model but we currently do not have such plans in mind. 447 model, but we currently do not have such plans in mind.
448 {% endtrans %} 448 {% endtrans %}
449 </p> 449 </p>
450 </section> 450 </section>
@@ -918,7 +918,7 @@
918 Here, there are differences in terms of application domain and how 918 Here, there are differences in terms of application domain and how
919 specifically anonymity is achieved. 919 specifically anonymity is achieved.
920 Anonymous routing is a hard research topic, so for a superficial 920 Anonymous routing is a hard research topic, so for a superficial
921 comparisson like this one we focus on the latency. 921 comparison like this one we focus on the latency.
922 Another important factor is the programming language. 922 Another important factor is the programming language.
923 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. 923 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.
924 {% endtrans %} 924 {% endtrans %}