From 2f89a732fe2de2eda0fe3c49727d61479d5c2c1e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Alexander=20M=C3=BCller?=
 <28591861+alexanderdd@users.noreply.github.com>
Date: Sun, 3 Mar 2024 09:10:29 +0100
Subject: [PATCH] in text: "bruteforce" > "brute force"
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

In description text we should use correct spelling which is "brute force" or "brute-force", not "bruteforce".

In other parts of the documentation, "brute force" is used: https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/bruteforce_configuration.html

See also https://en.wikipedia.org/wiki/Brute-force_attack

Signed-off-by: Alexander Müller <28591861+alexanderdd@users.noreply.github.com>
---
 config/config.sample.php | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/config/config.sample.php b/config/config.sample.php
index 79f813a4dae..c21291cd3da 100644
--- a/config/config.sample.php
+++ b/config/config.sample.php
@@ -368,7 +368,7 @@ $CONFIG = [
 'token_auth_activity_update' => 60,
 
 /**
- * Whether the bruteforce protection shipped with Nextcloud should be enabled or not.
+ * Whether the brute force protection shipped with Nextcloud should be enabled or not.
  *
  * Disabling this is discouraged for security reasons.
  *
@@ -377,9 +377,9 @@ $CONFIG = [
 'auth.bruteforce.protection.enabled' => true,
 
 /**
- * Whether the bruteforce protection shipped with Nextcloud should be set to testing mode.
+ * Whether the brute force protection shipped with Nextcloud should be set to testing mode.
  *
- * In testing mode bruteforce attempts are still recorded, but the requests do
+ * In testing mode brute force attempts are still recorded, but the requests do
  * not sleep/wait for the specified time. They will still abort with
  * "429 Too Many Requests" when the maximum delay is reached.
  * Enabling this is discouraged for security reasons