From d67e6a8769177f9192cea6eb658b331d2e66365d Mon Sep 17 00:00:00 2001
From: Valdnet <47037905+Valdnet@users.noreply.github.com>
Date: Mon, 25 Apr 2022 14:33:56 +0200
Subject: [PATCH] Correct spelling (#8213)

Signed-off-by: Valdnet <47037905+Valdnet@users.noreply.github.com>
---
 .../configuration_server/background_jobs_configuration.rst    | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/admin_manual/configuration_server/background_jobs_configuration.rst b/admin_manual/configuration_server/background_jobs_configuration.rst
index f8b4083a4..47dd336b2 100644
--- a/admin_manual/configuration_server/background_jobs_configuration.rst
+++ b/admin_manual/configuration_server/background_jobs_configuration.rst
@@ -43,7 +43,7 @@ The following sections describe the differences between each method.
 AJAX
 ^^^^
 
-**Usecase: Single user instance**
+**Use case: Single user instance**
 
 The AJAX scheduling method is the default option. Unfortunately, however, it is
 also the least reliable. Each time a user visits the Nextcloud page, a single
@@ -59,7 +59,7 @@ requires regular visits to the page for it to be triggered.
 Webcron
 ^^^^^^^
 
-**Usecase: Very small instance** (1-5 users depending on the usage)
+**Use case: Very small instance** (1–5 users depending on the usage)
 
 By registering your Nextcloud ``cron.php`` script address at an external webcron
 service (for example, easyCron_), you ensure that background jobs are executed