fix: correct readme path

cosmos · Dec 18, 2024 · eb44cd6 · eb44cd6
1 parent 57a1fca
commit eb44cd6
Show file tree

Hide file tree

Showing 5 changed files with 5 additions and 5 deletions.
diff --git a/docs/docs/04-middleware/02-callbacks/01-overview.md b/docs/docs/04-middleware/02-callbacks/01-overview.md
@@ -17,7 +17,7 @@ This setup worked well for off-chain users interacting with IBC applications. Ho
 
 The Callbacks Middleware allows for this functionality by allowing the packets of the underlying IBC applications to register callbacks to secondary applications for lifecycle events. These callbacks are then executed by the Callbacks Middleware when the corresponding packet lifecycle event occurs.
 
-After much discussion, the design was expanded to [an ADR](/architecture/adr-008-app-caller-cbs.md), and the Callbacks Middleware is an implementation of that ADR.
+After much discussion, the design was expanded to [an ADR](../../../architecture/adr-008-app-caller-cbs.md), and the Callbacks Middleware is an implementation of that ADR.
 
 ## Concepts
 

diff --git a/docs/versioned_docs/version-v7.8.x/04-middleware/02-callbacks/01-overview.md b/docs/versioned_docs/version-v7.8.x/04-middleware/02-callbacks/01-overview.md
@@ -17,7 +17,7 @@ This setup worked well for off-chain users interacting with IBC applications. Ho
 
 The Callbacks Middleware allows for this functionality by allowing the packets of the underlying IBC applications to register callbacks to secondary applications for lifecycle events. These callbacks are then executed by the Callbacks Middleware when the corresponding packet lifecycle event occurs.
 
-After much discussion, the design was expanded to [an ADR](/architecture/adr-008-app-caller-cbs.md), and the Callbacks Middleware is an implementation of that ADR.
+After much discussion, the design was expanded to [an ADR](../../../../architecture/adr-008-app-caller-cbs.md), and the Callbacks Middleware is an implementation of that ADR.
 
 ## Concepts
 

diff --git a/docs/versioned_docs/version-v8.5.x/04-middleware/02-callbacks/01-overview.md b/docs/versioned_docs/version-v8.5.x/04-middleware/02-callbacks/01-overview.md
@@ -17,7 +17,7 @@ This setup worked well for off-chain users interacting with IBC applications. Ho
 
 The Callbacks Middleware allows for this functionality by allowing the packets of the underlying IBC applications to register callbacks to secondary applications for lifecycle events. These callbacks are then executed by the Callbacks Middleware when the corresponding packet lifecycle event occurs.
 
-After much discussion, the design was expanded to [an ADR](/architecture/adr-008-app-caller-cbs.md), and the Callbacks Middleware is an implementation of that ADR.
+After much discussion, the design was expanded to [an ADR](../../../../architecture/adr-008-app-caller-cbs.md), and the Callbacks Middleware is an implementation of that ADR.
 
 ## Concepts
 

diff --git a/docs/versioned_docs/version-v9.0.x/04-middleware/02-callbacks/01-overview.md b/docs/versioned_docs/version-v9.0.x/04-middleware/02-callbacks/01-overview.md
@@ -17,7 +17,7 @@ This setup worked well for off-chain users interacting with IBC applications. Ho
 
 The Callbacks Middleware allows for this functionality by allowing the packets of the underlying IBC applications to register callbacks to secondary applications for lifecycle events. These callbacks are then executed by the Callbacks Middleware when the corresponding packet lifecycle event occurs.
 
-After much discussion, the design was expanded to [an ADR](/architecture/adr-008-app-caller-cbs.md), and the Callbacks Middleware is an implementation of that ADR.
+After much discussion, the design was expanded to [an ADR](../../../../architecture/adr-008-app-caller-cbs.md), and the Callbacks Middleware is an implementation of that ADR.
 
 ## Concepts
 

diff --git a/modules/apps/callbacks/README.md b/modules/apps/callbacks/README.md
@@ -6,7 +6,7 @@ This setup worked well for off-chain users interacting with IBC applications. Ho
 
 The Callbacks Middleware allows for this functionality by allowing the packets of the underlying IBC applications to register callbacks to secondary applications for lifecycle events. These callbacks are then executed by the Callbacks Middleware when the corresponding packet lifecycle event occurs.
 
-After much discussion, the design was expanded to [an ADR](/architecture/adr-008-app-caller-cbs.md), and the Callbacks Middleware is an implementation of that ADR.
+After much discussion, the design was expanded to [an ADR](../../../docs/architecture/adr-008-app-caller-cbs.md), and the Callbacks Middleware is an implementation of that ADR.
 
 ## Version Matrix