From 2c369aedf52fdcde8b0c1b30bea1e78dc3623d70 Mon Sep 17 00:00:00 2001
From: albertony <12441419+albertony@users.noreply.github.com>
Date: Thu, 10 Jul 2025 14:03:30 +0200
Subject: [PATCH] docs: fix markdownlint issue md037/no-space-in-emphasis

---
 docs/content/docs.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/content/docs.md b/docs/content/docs.md
index 1d445a296..95828592c 100644
--- a/docs/content/docs.md
+++ b/docs/content/docs.md
@@ -1979,9 +1979,9 @@ if `--vfs-cache-mode` is set to `writes` or above.
 
 Most multi-thread transfers do not take additional memory, but some do
 (for example uploading to s3). In the worst case memory usage can be
-at maximum `--transfers` * `--multi-thread-chunk-size` *
+at maximum `--transfers` \* `--multi-thread-chunk-size` \*
 `--multi-thread-streams` or specifically for the s3 backend
-`--transfers` * `--s3-chunk-size` * `--s3-concurrency`. However you
+`--transfers` \* `--s3-chunk-size` \* `--s3-concurrency`. However you
 can use the the [--max-buffer-memory](/docs/#max-buffer-memory) flag
 to control the maximum memory used here.