summaryrefslogtreecommitdiffstats
path: root/man/systemd-resolved.service.xml
diff options
context:
space:
mode:
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2020-04-14 10:37:40 +0200
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2020-04-21 16:58:04 +0200
commit38b38500c6011d6bc59171ee23d92fba46bd131e (patch)
treeafdb5bd5328ead493714c9a713a268f31cd122c0 /man/systemd-resolved.service.xml
parentman: reorder hostname1(5) (diff)
downloadsystemd-38b38500c6011d6bc59171ee23d92fba46bd131e.tar.xz
systemd-38b38500c6011d6bc59171ee23d92fba46bd131e.zip
tree-wide: use "hostname" spelling everywhere
It's not that I think that "hostname" is vastly superior to "host name". Quite the opposite — the difference is small, and in some context the two-word version does fit better. But in the tree, there are ~200 occurrences of the first, and >1600 of the other, and consistent spelling is more important than any particular spelling choice.
Diffstat (limited to 'man/systemd-resolved.service.xml')
-rw-r--r--man/systemd-resolved.service.xml6
1 files changed, 3 insertions, 3 deletions
diff --git a/man/systemd-resolved.service.xml b/man/systemd-resolved.service.xml
index a30c5f72b8..2aa5fec218 100644
--- a/man/systemd-resolved.service.xml
+++ b/man/systemd-resolved.service.xml
@@ -53,7 +53,7 @@
(<citerefentry project='man-pages'><refentrytitle>nss</refentrytitle><manvolnum>5</manvolnum></citerefentry>).
Usage of the glibc NSS module
<citerefentry><refentrytitle>nss-resolve</refentrytitle><manvolnum>8</manvolnum></citerefentry> is
- required in order to allow glibc's NSS resolver functions to resolve host names via
+ required in order to allow glibc's NSS resolver functions to resolve hostnames via
<command>systemd-resolved</command>.</para></listitem>
<listitem><para>Additionally, <command>systemd-resolved</command> provides a local DNS stub listener on
@@ -120,8 +120,8 @@
<listitem><para>Single-label names are routed to all local interfaces capable of IP multicasting, using
the LLMNR protocol. Lookups for IPv4 addresses are only sent via LLMNR on IPv4, and lookups for IPv6
- addresses are only sent via LLMNR on IPv6. Lookups for the locally configured host name and the
- <literal>_gateway</literal> host name are never routed to LLMNR.</para></listitem>
+ addresses are only sent via LLMNR on IPv6. Lookups for the locally configured hostname and the
+ <literal>_gateway</literal> hostname are never routed to LLMNR.</para></listitem>
<listitem><para>Multi-label names with the domain suffix <literal>.local</literal> are routed to all
local interfaces capable of IP multicasting, using the MulticastDNS protocol. As with LLMNR IPv4