From 79688c97f5b32db2b84e1939a6676543073051d7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Colin=20Axn=C3=A9r?=
 <25233464+colin-axner@users.noreply.github.com>
Date: Wed, 22 Dec 2021 16:21:22 +0100
Subject: [PATCH] fix broken link

---
 docs/ibc/relayer.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/ibc/relayer.md b/docs/ibc/relayer.md
index c839c14b60f..c846f2c7320 100644
--- a/docs/ibc/relayer.md
+++ b/docs/ibc/relayer.md
@@ -14,7 +14,7 @@ order: 6
 Events are emitted for every transaction processed by the base application to indicate the execution
 of some logic clients may want to be aware of. This is extremely useful when relaying IBC packets.
 Any message that uses IBC will emit events for the corresponding TAO logic executed as defined in
-the [IBC events spec](https://github.com/cosmos/ibc-go/blob/main/modules/core/spec/06_events.md).
+the [IBC events document](./events.md).
 
 In the SDK, it can be assumed that for every message there is an event emitted with the type `message`,
 attribute key `action`, and an attribute value representing the type of message sent