Manpage: Don't be too specific about TLS backend

It's GnuTLS on my system, but I don't know if it's a hard requirement or
if it will change some days. Also, there is no real need to specify it.

diff --git a/man1/lariza.usage.1 b/man1/lariza.usage.1
index 2b78b8e9de71cbcfe8ea70f53cc562f49c5d85c0..6e571cb751e2aa3b16476ec0b9846c98b7444a1f 100644 (file)
--- a/man1/lariza.usage.1
+++ b/man1/lariza.usage.1
@@ -1,4 +1,4 @@
-.TH lariza 1 "2020-05-02" "lariza" "User Commands"
+.TH lariza 1 "2020-05-03" "lariza" "User Commands"
 .\" --------------------------------------------------------------------
 .SH NAME
 lariza.usage \- extended usage hints
@@ -153,10 +153,10 @@ Those bundled web extensions are automatically compiled when you run
 make sure to link them to the directory mentioned above.
 .\" --------------------------------------------------------------------
 .SH "TRUSTED CERTIFICATES"
-By default, \fBlariza\fP trusts whatever CAs are trusted by WebKit, i.e.
-by your GnuTLS installation. If you wish to trust additional
-certificates, such as self-signed certificates, the first thing you
-should do is try to add the appropriate CAs to your system-wide store.
+By default, \fBlariza\fP trusts whatever CAs are trusted by WebKit. If
+you wish to trust additional certificates, such as self-signed
+certificates, the first thing you should do is try to add the
+appropriate CAs to your system-wide store.
 .P
 If you wish to add simple exceptions, you can grab the certificate and
 store it in the directory \fI~/.config/lariza/certs\fP. The filename