From 062b4a294aca6e83c3a850e6e7c980272420fce1 Mon Sep 17 00:00:00 2001 From: Paul Balaji Date: Tue, 16 Jan 2024 10:57:13 +0000 Subject: [PATCH] hardcode step number --> 'steps above' Signed-off-by: Paul Balaji --- docs/partials/deploy-hyperlane/_send-test-messages.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/partials/deploy-hyperlane/_send-test-messages.mdx b/docs/partials/deploy-hyperlane/_send-test-messages.mdx index a9fdab1a..2fba9227 100644 --- a/docs/partials/deploy-hyperlane/_send-test-messages.mdx +++ b/docs/partials/deploy-hyperlane/_send-test-messages.mdx @@ -5,4 +5,4 @@ Initiate the message with the CLI. It will ask for a set of core deployment arti hyperlane send message --key $PRIVATE_KEY ``` -The `send message` command will inform you when the message is dispatched. After a short wait, a confirmation of delivery will be displayed. If the message delivery times out, it is likely that there's an issue with the Validator or Relayer setup in steps 3 and 4 above. To troubleshoot start by looking at the origin chain relayer logs. If you need further help, reach out on [Discord](https://discord.gg/hyperlane). +The `send message` command will inform you when the message is dispatched. After a short wait, a confirmation of delivery will be displayed. If the message delivery times out, it is likely that there's an issue with the Validator or Relayer setup in the steps above. To troubleshoot start by looking at the origin chain relayer logs. If you need further help, reach out on [Discord](https://discord.gg/hyperlane).