From 5e81e84c86c00cb83b80c955682d038199c541fe Mon Sep 17 00:00:00 2001 From: codefiles <11915375+codefiles@users.noreply.github.com> Date: Fri, 22 Jul 2022 20:33:07 -0400 Subject: [PATCH] man: Fix typo --- man/systemd-resolved.service.xml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/man/systemd-resolved.service.xml b/man/systemd-resolved.service.xml index a7e08f0c801..7f30fa65362 100644 --- a/man/systemd-resolved.service.xml +++ b/man/systemd-resolved.service.xml @@ -315,11 +315,11 @@ search foobar.com barbar.com systemd-resolved maintains the /run/systemd/resolve/stub-resolv.conf file for compatibility with traditional - Linux programs. This file may be symlinked from /etc/resolv.conf. This file lists - the 127.0.0.53 DNS stub (see above) as the only DNS server. It also contains a list of search domains - that are in use by systemd-resolved. The list of search domains is always kept up-to-date. Note that - /run/systemd/resolve/stub-resolv.conf should not be used directly by applications, - but only through a symlink from /etc/resolv.conf. This file may be symlinked from + Linux programs. This file lists the 127.0.0.53 DNS stub (see above) as the only DNS server. It also + contains a list of search domains that are in use by systemd-resolved. The list of search domains is + always kept up-to-date. Note that /run/systemd/resolve/stub-resolv.conf should not + be used directly by applications, but only through a symlink from + /etc/resolv.conf. This file may be symlinked from /etc/resolv.conf in order to connect all local clients that bypass local DNS APIs to systemd-resolved with correct search domains settings. This mode of operation is recommended. -- 2.47.3