diff options
| author | Lennart Poettering <lennart@poettering.net> | 2016-01-05 16:42:40 +0100 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2016-01-05 17:30:43 +0100 |
| commit | d57d3973a739fa7aa4c2e6c241588ba92f60e8d3 (patch) | |
| tree | d2c7cc870717393e9a5b27fe2f1192e4b0af1c05 | |
| parent | 79a4c0160af9496e0aff92e12ff61dae0f169625 (diff) | |
man: fix a few typos
| -rw-r--r-- | man/resolved.conf.xml | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/man/resolved.conf.xml b/man/resolved.conf.xml index 8473bbe5c9..786b096ef6 100644 --- a/man/resolved.conf.xml +++ b/man/resolved.conf.xml @@ -161,7 +161,7 @@ lookups are correctly signed, or validly unsigned. If <varname>DNSSEC=</varname> is set to <literal>downgrade-ok</literal> the resolver will - automatically turn of DNSSEC validation in such a case.</para> + automatically turn off DNSSEC validation in such a case.</para> <para>Client programs looking up DNS data will be informed whether lookups could be verified using DNSSEC, or whether the @@ -173,11 +173,11 @@ this be required.</para> <para>It is recommended to set <varname>DNSSEC=</varname> to - true on systems where it is kown that the DNS server supports + true on systems where it is known that the DNS server supports DNSSEC correctly, and where software or trust anchor updates happen regularly. On other systems it is recommended to set <varname>DNSSEC=</varname> to - <literal>missing-ok</literal>.</para> + <literal>downgrade-ok</literal>.</para> </listitem> </varlistentry> |