summaryrefslogtreecommitdiff
path: root/src/third_party/wiredtiger/src/docs/tune-cache.dox
diff options
context:
space:
mode:
Diffstat (limited to 'src/third_party/wiredtiger/src/docs/tune-cache.dox')
-rw-r--r--src/third_party/wiredtiger/src/docs/tune-cache.dox2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/third_party/wiredtiger/src/docs/tune-cache.dox b/src/third_party/wiredtiger/src/docs/tune-cache.dox
index fc42fc80046..78e4b8181d9 100644
--- a/src/third_party/wiredtiger/src/docs/tune-cache.dox
+++ b/src/third_party/wiredtiger/src/docs/tune-cache.dox
@@ -98,7 +98,7 @@ same level.
By default, WiredTiger cache eviction is handled by a single, separate
thread. In a large, busy cache, a single thread will be insufficient
(especially when the eviction thread must wait for I/O). The
-\c eviction=(threads_min) and \c eviction=(threads_max) configuration
+\c "eviction=(threads_min)" and \c "eviction=(threads_max)" configuration
values can be used to configure the minimum and maximum number of
additional threads WiredTiger will create to keep up with the
application eviction load. Finally, if the Wiredtiger eviction threads