diff --git a/docs/using-the-api/webhooks/troubleshooting.md b/docs/using-the-api/webhooks/troubleshooting.md
index f58e24cff..50f7507d3 100644
--- a/docs/using-the-api/webhooks/troubleshooting.md
+++ b/docs/using-the-api/webhooks/troubleshooting.md
@@ -29,10 +29,10 @@ A webhook consumer endpoint which is disabled after the 5 min retry, but then re
 
 ## Message Status
 
-- "Success" indicates that there was at least one attempt for that message that succeeded against it's endpoint. 
-- "Failure" indicates that all attempts were exhausted, and none of them succeeded.
-- "Attempting" indicates that at least one attempt has been sent and there are further attempts scheduled as part of the retry policy.
-- "Sending" indicates that the process of sending the webhook has begun but there have been no delivery attempts yet. 
+- **Success** indicates that there was at least one attempt for that message that succeeded against it's endpoint. 
+- **Failure** indicates that all attempts were exhausted, and none of them succeeded.
+- **Attempting** indicates that at least one attempt has been sent and there are further attempts scheduled as part of the retry policy.
+- **Sending** indicates that the process of sending the webhook has begun but there have been no delivery attempts yet. 
 
 ## Recover failed and missed messages
 
@@ -67,7 +67,7 @@ Then, click the triple-dot menu on the right and choose one of the applicable op
 
 For more granular date control, you can scroll to the endpoint's message attempts, click the triple-dot options menu of a specific message, and choose **Replay > Replay all failed messages since this time**.
 
-During the recovery of mutiple messages, all messages will be sent at once with some jitter applied in order to prevent overloading the webhook consumer endpoint. If your system has rate-limiting in place, the number of messages to recover may be an important consideration to avoid further failures. Please reach out to Codat Support if unsure.
+During the recovery of mutiple messages, all messages will be sent at once with some jitter applied in order to prevent overloading the webhook consumer endpoint. If your system has rate-limiting in place, the number of messages to recover may be an important consideration to avoid further failures. [Please see our docs around rate limiting endpoints](/using-the-api/webhooks/create-consumer).
 
 ### Idempotency