From 96e28fd237ca4ebaa40ca5c4e2766f0740846dfd Mon Sep 17 00:00:00 2001
From: TomRicci <44097104+TomRicci@users.noreply.github.com>
Date: Mon, 21 Oct 2024 17:31:26 +0200
Subject: [PATCH] fix: documentation selfAddPersonalAccess.rst

---
 doc/sphinx/plugins/restricted/selfAddPersonalAccess.rst | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/sphinx/plugins/restricted/selfAddPersonalAccess.rst b/doc/sphinx/plugins/restricted/selfAddPersonalAccess.rst
index 68f72bd..f814b90 100644
--- a/doc/sphinx/plugins/restricted/selfAddPersonalAccess.rst
+++ b/doc/sphinx/plugins/restricted/selfAddPersonalAccess.rst
@@ -32,10 +32,10 @@ Add a personal server access to your account
                               must not specify --user in that case. However, for this protocol to be usable under a given
                               remote user, access to the USER@HOST:PORT tuple must also be allowed.
                               PROTO must be one of:
-                              scpup    allow SCP upload, you--bastion-->server
-                              scpdown  allow SCP download, you<--bastion--server
-                              sftp     allow usage of the SFTP subsystem, through the bastion
-                              rsync    allow usage of rsync, through the bastion
+                              scpupload    allow SCP upload, you--bastion-->server
+                              scpdownload  allow SCP download, you<--bastion--server
+                              sftp         allow usage of the SFTP subsystem, through the bastion
+                              rsync        allow usage of rsync, through the bastion
 .. option:: --force
 
    Add the access without checking that the public SSH key is properly installed remotely