aboutsummaryrefslogtreecommitdiff
path: root/docs/tutorials/socket_activation.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/tutorials/socket_activation.md')
-rw-r--r--docs/tutorials/socket_activation.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/tutorials/socket_activation.md b/docs/tutorials/socket_activation.md
index 8275075f0..7eeb1ed80 100644
--- a/docs/tutorials/socket_activation.md
+++ b/docs/tutorials/socket_activation.md
@@ -3,7 +3,7 @@
Socket activation conceptually works by having systemd create a socket (e.g. TCP, UDP or Unix
socket). As soon as a client connects to the socket, systemd will start the systemd service that is
configured for the socket. The newly started program inherits the file descriptor of the socket
-and can then call accept the incoming connection (in other words run the system call `accept()`).
+and can then accept the incoming connection (in other words run the system call `accept()`).
This description corresponds to the default systemd socket configuration
[`Accept=no`](https://www.freedesktop.org/software/systemd/man/systemd.socket.html#Accept=)
that lets the service accept the socket.