Documentation: seccomp: fix reST markup

Signed-off-by: Jakub Wilk <jwilk@jwilk.net>
Acked-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>

diff --git a/Documentation/userspace-api/seccomp_filter.rst b/Documentation/userspace-api/seccomp_filter.rst
index b1b846d8a0946de5e5540e322925bbc4da30d1f5..0f09a63ea9234b98da91cf31963fdc71aeb144d5 100644 (file)
--- a/Documentation/userspace-api/seccomp_filter.rst
+++ b/Documentation/userspace-api/seccomp_filter.rst
@@ -133,7 +133,7 @@ In precedence order, they are:
        call.  If there is no tracer present, ``-ENOSYS`` is returned to
        userland and the system call is not executed.
 
-       A tracer will be notified if it requests ``PTRACE_O_TRACESECCOM``P
+       A tracer will be notified if it requests ``PTRACE_O_TRACESECCOMP``
        using ``ptrace(PTRACE_SETOPTIONS)``.  The tracer will be notified
        of a ``PTRACE_EVENT_SECCOMP`` and the ``SECCOMP_RET_DATA`` portion of
        the BPF program return value will be available to the tracer