summaryrefslogtreecommitdiff
path: root/man/systemd.socket.xml
diff options
context:
space:
mode:
authorYu Watanabe <watanabe.yu+github@gmail.com>2021-06-30 20:53:14 +0900
committerYu Watanabe <watanabe.yu+github@gmail.com>2021-06-30 23:32:43 +0900
commit3d62af7d235552af5ea9ec0a812cc522f6516574 (patch)
tree4e14d5b15b8ea224ba14bcd834c3fd534e636cc4 /man/systemd.socket.xml
parent857f0e0ae38179faf07ab628cdec7ede5e596899 (diff)
downloadsystemd-3d62af7d235552af5ea9ec0a812cc522f6516574.tar.gz
tree-wide: fix "the the" and "a a"
Diffstat (limited to 'man/systemd.socket.xml')
-rw-r--r--man/systemd.socket.xml4
1 files changed, 2 insertions, 2 deletions
diff --git a/man/systemd.socket.xml b/man/systemd.socket.xml
index 520a906249..b669e7d15d 100644
--- a/man/systemd.socket.xml
+++ b/man/systemd.socket.xml
@@ -99,8 +99,8 @@
<citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>), receiving only
the sockets configured through socket-activation from the host's namespace. In such a set-up communication within
the host's network namespace is only permitted through the activation sockets passed in while all sockets allocated
- from the service code itself will be associated with the service's own namespace, and thus possibly subject to a a
- much more restrictive configuration.</para>
+ from the service code itself will be associated with the service's own namespace, and thus possibly subject to a
+ restrictive configuration.</para>
</refsect1>
<refsect1>