Some rewording

diff --git a/doc/features.texi b/doc/features.texi
index 27f58819f8d8c81d6ccf90ad10c9a63b0d086804b1e32df585a62a77581e7ae1..2d6c6950bfac18a97f799d83270ee195de2dd3f999ab0954dd7aef0c81aeb947 100644 (file)
--- a/doc/features.texi
+++ b/doc/features.texi
@@ -7,18 +7,19 @@
 server, while it copies it to other clients. However, as a rule, there
 is single client speaking at one time.
 
-@item 20ms frames with  Opus-encoded audio with PLC (Packet Loss
-Concealment) and DTX (discontinuous transmission) features enabled.
-Optional VAD (voice activity detection).
+@item 20ms frames with @url{https://opus-codec.org/, Opus}-encoded audio
+with PLC (Packet Loss Concealment) and DTX (discontinuous transmission)
+features enabled. Optional @ref{VAD} (voice activity detection).
 
-@item Noise protocol-based 0-RTT handshake over TCP between client and
-server for creating authenticated encrypted channel and authentication
-based on server's public key knowledge.
+@item @url{http://noiseprotocol.org/, Noise}-NK protocol-based 0-RTT
+single round-trip handshake over TCP between client and server for
+creating authenticated encrypted channel and authentication based on
+server's public key knowledge.
 
 @item Fast ChaCha20 encryption with SipHash24 message authentication.
 
 @item Rooms, optionally password protected.
 
-@item Fancy TUI client with mute-toggle ability.
+@item Fancy TUI client with mute-toggle ability by external utilities.
 
 @end itemize

diff --git a/doc/index.texi b/doc/index.texi
index b1c2fb92c984dcac6778daf581001651506cd0356798a9218df06f612e2cb6c7..8abdef441dd0a946153817c551ad4a6fb61eca8f118db0b21762ed8ed57d956a 100644 (file)
--- a/doc/index.texi
+++ b/doc/index.texi
@@ -19,7 +19,8 @@ monsters by complexity and size, hardly possible to debug and having
 frequent compatibility problems. They work mainly only if you use the
 same kind of software and codecs, for example Chromium, that requires
 dozens of gigabytes of disk space and much RAM, CPU time to build it.
-Is not it pure insanity for such relatively simple task?
+Taking an enormous amount of CPU power to slowly work with it. Is not
+it pure insanity for such relatively simple task?
 
 Mumble has wonderful simplicity and workability, but even its server
 side is still written on Qt, which requires hundreds of megabytes of
@@ -28,8 +29,8 @@ its newer client versions quality and convenience.
 
 So let's write as simple VoIP talking client as it is possible, without
 compromising convenience and simplicity for the user! I just want a
-simple command, which only requires to specify the server's address to
-just immediately talk with someone.
+simple command, which only requires to specify the server's address with
+the key to just immediately talk with someone.
 
 @itemize
 
@@ -38,21 +39,17 @@ application? But a fancy real-time refreshing TUI would be desirable.
 Mumble tends to output no information, sometimes hiding the fact of a
 problem and that everything stopped working.
 
-@item No NAT-traversal possibility. It is the year 2024 year already,
-stop trying to use and revive legacy obsolete IPv4. Either use some
-overlay network on top of it, or VPN, whatever.
+@item Mono-cypher, mono-codec protocol.
 
-@item Mono-cypher, mono-codec protocol. The @url{https://opus-codec.org/, Opus}
-audio codec is perfect for VoIP tasks. ChaCha20 is more than
-appropriate and satisfies as fast and secure encryption solution.
+@item Maximal easiness of usage: here is your address, key, do me good.
+
+@end itemize
 
 @float
 @image{screenshots/example,,,Server and two clients,.webp}
 @caption{Server (above) and two clients (left and right) in a terminal multiplexer}
 @end float
 
-@end itemize
-
 @include features.texi
 @include install.texi
 @include usage.texi