doc: fix typo in docs about system profile fallback

Docs for the system profile fallback syntax accidentally repeated
the "@" marker before each keyword. The "@" marker only indicates
the start of the profile field, and individual names are merely
separated by a comma, per the impl in 6b6d9dd44e.

Fixes 6f425b0fd7d860e9d78b7ba0d9c4d3165d824d7c
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

diff --git a/doc/cha-config.texi b/doc/cha-config.texi
index 5a7cae5c5e58427de5ce060c432fa825bb615c29..a74713a8459a77511edc7d9f8b71aac173c97d04 100644 (file)
--- a/doc/cha-config.texi
+++ b/doc/cha-config.texi
@@ -48,8 +48,9 @@ The format is '@code{KEYWORD = VALUE}', e.g.,
 
 When used they may be followed by additional options that will be appended to the
 system string (e.g., '@code{@@EXAMPLE-PRIORITY:+SRP}'). '@code{EXAMPLE-PRIORITY=NORMAL:+ARCFOUR-128}'.
-Since version 3.5.1 applications are allowed to specify fallback keywords such as
-@@KEYWORD1,@@KEYWORD2, and the first valid keyword will be used.
+Since version 3.5.1 it is allowed to specify fallback keywords by
+separating them with a comma, such as @@KEYWORD1,KEYWORD2, and the
+first valid keyword will be used.
 
 The following example configuration defines a priority string called @code{@@SYSTEM}.
 When set, its full settings can be queried using @code{gnutls-cli --priority @@SYSTEM --list}.

diff --git a/doc/cha-gtls-app.texi b/doc/cha-gtls-app.texi
index 9dccf06bfc1e0d330751f8ac39edc554f22db16b..22b5f4143cf41b0e06149af634dce05f5accd7d7 100644 (file)
--- a/doc/cha-gtls-app.texi
+++ b/doc/cha-gtls-app.texi
@@ -1318,8 +1318,9 @@ It may be followed by additional options that will be appended to the
 system string (e.g., "@@SYSTEM:+SRP"). The system file should have the
 format 'KEYWORD=VALUE', e.g., 'SYSTEM=NORMAL:+ARCFOUR-128'.
 
-Since version 3.5.1 it is allowed to specify fallback keywords such
-as @@KEYWORD1,@@KEYWORD2, and the first valid keyword will be used.
+Since version 3.5.1 it is allowed to specify fallback keywords by
+separating them with a comma, such as @@KEYWORD1,KEYWORD2, and the
+first valid keyword will be used.
 
 @item PERFORMANCE @tab
 All the known to be secure ciphersuites are enabled,