Use Joe's wording

DuendeSoftware · Jan 24, 2024 · 657eee2 · 657eee2
1 parent 75ac22d
commit 657eee2
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 6 deletions.
diff --git a/IdentityServer/v7/docs/content/data/ef.md b/IdentityServer/v7/docs/content/data/ef.md
@@ -133,9 +133,7 @@ This options class contains properties to control the operational store and *Per
     OneTime usage can be marked as consumed. 
 
 *FuzzTokenCleanupStart* [added in 7.0]
-    The background token cleanup job runs at a configured interval. If multiple nodes run the cleanup
-    job at the same time, update conflicts might occur in the store. To reduce the probability of that happening, the startup time
-    can be fuzzed. When enabled, the first run is scheduled at a random time between the host startup and the configured
+    The background token cleanup job runs at a configured interval. If multiple nodes run the cleanup job at the same time, update conflicts might occur in the store. To reduce the probability of that happening, the startup time can be fuzzed. When enabled, the first run is scheduled at a random time between the host startup and the configured
     TokenCleanupInterval. Subsequent runs are run on the configured TokenCleanupInterval. Defaults to *true*.
 
 

diff --git a/IdentityServer/v7/docs/content/reference/options.md b/IdentityServer/v7/docs/content/reference/options.md
@@ -669,9 +669,7 @@ Settings for [server-side sessions]({{<ref "/ui/server_side_sessions">}}). Added
 * ***FuzzExpiredSessionRemovalStart***
 
     The background session cleanup job runs at a configured interval. If multiple nodes run the cleanup
-    job at the same time there will be updated conflicts in the store. To avoid that, the startup time
-    can be fuzzed. The first run is scheduled at a random time between the host startup and the configured
-    RemoveExpiredSessionsFrequency. Subsequent runs are run on the configured RemoveExpiredSessionsFrequency.
+    job at the same time update conflicts might occur in the store. To reduce the propability of that happening, the startup time can be fuzzed. The first run is scheduled at a random time between the host startup and the configured RemoveExpiredSessionsFrequency. Subsequent runs are run on the configured RemoveExpiredSessionsFrequency.
     Defaults to *true*.
 
 ## Validation