for consistency:
  s/slice_ctrl.request/slice_ctrl::request/
  s/reqeust/request

Please fold.

Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
---
 Documentation/userspace-api/rseq.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/userspace-api/rseq.rst b/Documentation/userspace-api/rseq.rst
index c7d1c651514a5..e1fdb0d5ce695 100644
--- a/Documentation/userspace-api/rseq.rst
+++ b/Documentation/userspace-api/rseq.rst
@@ -75,13 +75,13 @@ field via the ``RSEQ_CS_FLAG_SLICE_EXT_AVAILABLE_BIT`` and the
 space and only for informational purposes.
 
 If the mechanism was enabled via prctl(), the thread can request a time
-slice extension by setting rseq::slice_ctrl.request to 1. If the thread is
+slice extension by setting rseq::slice_ctrl::request to 1. If the thread is
 interrupted and the interrupt results in a reschedule request in the
 kernel, then the kernel can grant a time slice extension and return to
 userspace instead of scheduling out. The length of the extension is
 determined by the ``rseq_slice_extension_nsec`` sysctl.
 
-The kernel indicates the grant by clearing rseq::slice_ctrl::reqeust and
+The kernel indicates the grant by clearing rseq::slice_ctrl::request and
 setting rseq::slice_ctrl::granted to 1. If there is a reschedule of the
 thread after granting the extension, the kernel clears the granted bit to
 indicate that to userspace.
-- 
2.51.0