[wiki] [sites] Refine wording || Laslo Hunhold

From: <git_AT_suckless.org>
Date: Fri, 24 Jan 2020 09:04:45 +0100

commit 08a6015b1edd21c53135788ea78f8c5743754272
Author: Laslo Hunhold <dev_AT_frign.de>
Date: Fri Jan 24 09:03:22 2020 +0100

    Refine wording
    
    Signed-off-by: Laslo Hunhold <dev_AT_frign.de>

diff --git a/tools.suckless.org/quark/index.md b/tools.suckless.org/quark/index.md
index 7a29e09b..46d7ce34 100644
--- a/tools.suckless.org/quark/index.md
+++ b/tools.suckless.org/quark/index.md
_AT_@ -48,11 +48,11 @@ DoS the form handler, the serving of content is still unaffected.
 TLS-support
 -----------
 quark does not natively support TLS. A more suckless approach than to
-implement TLS into it is to use a TLS reverse tunnel (e.g. [tlstunnel](https://github.com/hannesm/tlstunnel),
+implement TLS into it is to use a TLS reverse proxy (e.g. [tlstunnel](https://github.com/hannesm/tlstunnel),
 [hitch](https://hitch-tls.org/) or [stunnel](https://www.stunnel.org/)).
-A TLS-tunnel accepts encrypted TLS connections and forwards them as unencrypted
-TLS to a server. In this case, one can run stunnel on an intended IP
-address and forward the requests to a local port or UNIX-domain socket.
+It accepts encrypted TLS connections and forwards them as unencrypted
+requests to a server. In this case, one can run such a reverse proxy to listen
+on a public IP address and forward the requests to a local port or UNIX-domain socket.
 
 Solutions
 ---------
Received on Fri Jan 24 2020 - 09:04:45 CET

This archive was generated by hypermail 2.3.0 : Fri Jan 24 2020 - 09:12:33 CET