From b561692828f74df70517e787f6605a06842e54cd Mon Sep 17 00:00:00 2001
From: Valdnet <47037905+Valdnet@users.noreply.github.com>
Date: Mon, 28 Sep 2020 11:26:27 +0200
Subject: [PATCH] Correction of the sentence

---
 user_manual/files/encrypting_files.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/user_manual/files/encrypting_files.rst b/user_manual/files/encrypting_files.rst
index c4392b3cf..0116ff784 100644
--- a/user_manual/files/encrypting_files.rst
+++ b/user_manual/files/encrypting_files.rst
@@ -53,11 +53,11 @@ Can encryption be disabled without the user's password?
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 If you don't have the users password or `file recovery key
-<https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/encryption_configuration.html#enabling-users-file-recovery-keys>`_.
+<https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/encryption_configuration.html#enabling-users-file-recovery-keys>`_,
 
 .. TODO ON RELEASE: Update version number above on release
 
-Then there is no way to decrypt all files. What's more, running it on login
+then there is no way to decrypt all files. What's more, running it on login
 would be dangerous, because you would most likely run into timeouts.
 
 Is it planned to move this to the next user login or a background job?