fixup! Should I reduce the REST publish timeout?

Author: franrob-projects

src/pages/docs/pub-sub/index.mdx

@@ -441,20 +441,23 @@ if err := channel.Publish(context.Background(), "example", "message data"); err
 
 REST publish operations have a default 10-second timeout. While you may consider reducing this timeout for faster failure feedback, be aware that this can create problems:
 
-**Why short timeouts can be problematic:**
-- Most requests that exceed short timeouts (e.g., <1s) still succeed with normal latency
-- Retrying typically doesn't speed up message delivery and creates additional system load  
-- During high load or scaling operations, retry storms can worsen performance
-- You'll miss important error notifications (rate limits, channel limits) if requests timeout prematurely
-
-**The default 10-second timeout is designed to:**
-- Account for channel activation latency in multi-region deployments
-- Handle network and processing queue variations
-- Provide reliable error reporting for legitimate failures
-
-**When to consider timeout adjustments:**
-- Use `httpOpenTimeout` (default 4s) for connection establishment issues, not `httpRequestTimeout` for the full request
-- Only reduce request timeouts if you have robust retry logic and can handle increased system load
+Short timeouts can be problematic for the following reasons:
+
+- Most requests that exceed short timeouts, for example < 1s, still succeed with normal latency.
+- Retrying typically doesn't speed up message delivery and creates additional system load.
+- During high load or scaling operations, retry storms can worsen performance.
+- You'll miss important error notifications (rate limits, channel limits) if requests timeout prematurely.
+
+The default 10-second timeout is designed to:
+
+- Account for channel activation latency in multi-region deployments.
+- Handle network and processing queue variations.
+- Provide reliable error reporting for legitimate failures.
+
+When to consider timeout adjustments:
+
+- Use `httpOpenTimeout` (default 4s) for connection establishment issues, not `httpRequestTimeout` for the full request.
+- Only reduce request timeouts if you have robust retry logic and can handle increased system load.
 
 <Aside data-type="further-reading">
 You can find out more detail about how [channels](/docs/channels) and [messages](/docs/messages) work.