From 08f9055bf0e2fb9be3bceefb85ede10a6e51495a Mon Sep 17 00:00:00 2001 From: Avi Atkin <103125634+avious00@users.noreply.github.com> Date: Sun, 3 Dec 2023 18:51:21 -0500 Subject: [PATCH] fix more broken links --- docs/guides/v2-to-v3-migration.mdx | 2 +- docs/operate/config-reference.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/guides/v2-to-v3-migration.mdx b/docs/guides/v2-to-v3-migration.mdx index d5bf543c..273f78ba 100644 --- a/docs/guides/v2-to-v3-migration.mdx +++ b/docs/guides/v2-to-v3-migration.mdx @@ -33,7 +33,7 @@ interface IMailbox { } ``` -This is a departure from the existing [interchain gas payment](https://docs.hyperlane.xyz/docs/apis-and-sdks/interchain-gas-paymaster-api) and [hook](https://docs.hyperlane.xyz/docs/apis-and-sdks/hooks) interfaces but should be almost entirely backwards compatible. Mirroring the [interchain security modules](../reference/ISM/specify-your-ISM.mdx) pre-handle lifecycle hook, the architectural change is introducing post-dispatch lifecycle hooks which receive authenticated message content from the mailbox and perform some additional task, like paying interchain gas to relayers or using a different transport layer. +This is a departure from the existing [interchain gas payment](../reference/hooks/interchain-gas.mdx) and [hook](../reference/hooks/overview.mdx) interfaces but should be almost entirely backwards compatible. Mirroring the [interchain security modules](../reference/ISM/specify-your-ISM.mdx) pre-handle lifecycle hook, the architectural change is introducing post-dispatch lifecycle hooks which receive authenticated message content from the mailbox and perform some additional task, like paying interchain gas to relayers or using a different transport layer. ![v3 hook diagram](../../static/img/v3-hook-diagram.png) diff --git a/docs/operate/config-reference.mdx b/docs/operate/config-reference.mdx index d26588d0..0c93e0a1 100644 --- a/docs/operate/config-reference.mdx +++ b/docs/operate/config-reference.mdx @@ -8,7 +8,7 @@ import TabItem from '@theme/TabItem'; **Description:** (Env only) List of additional configuration file paths to load in order (such as those in `hyperlane-monorepo/rust/config`). They will be merged first to last, so if both the first one and the last one specify a specific config path, the value set in the last file listed will be used. -These files must be accessible within the filesystem your agent has access to. If you're running in Docker, see [#config-files-with-docker](./#config-files-with-docker "mention") for tips on mounting your config files into your Docker container. +These files must be accessible within the filesystem your agent has access to. If you're running in Docker, see [the agent configuration guide](./agent-config.mdx#config-files-with-docker) for tips on mounting your config files into your Docker container. **Optional:** Yes