chore: update github.com/cosmos/ics to github.com/cosmos/ibc in markd…

…own files
cosmos · Dec 18, 2024 · fea6d9b · fea6d9b
1 parent c52a246
commit fea6d9b
Show file tree

Hide file tree

Showing 9 changed files with 11 additions and 11 deletions.
diff --git a/docs/architecture/adr-015-ibc-packet-receiver.md b/docs/architecture/adr-015-ibc-packet-receiver.md
@@ -295,5 +295,5 @@ Proposed
 
 ## References
 
-- Relevant comment: [cosmos/ics#289](https://github.com/cosmos/ics/issues/289#issuecomment-544533583)
+- Relevant comment: [cosmos/ics#289](https://github.com/cosmos/ibc/issues/289#issuecomment-544533583)
 - [ICS26 - Routing Module](https://github.com/cosmos/ibc/tree/master/spec/core/ics-026-routing-module)
diff --git a/docs/architecture/adr-026-ibc-client-recovery-mechanisms.md b/docs/architecture/adr-026-ibc-client-recovery-mechanisms.md
@@ -84,7 +84,7 @@ No neutral consequences.
 
 ## References
 
-- [Prior discussion](https://github.com/cosmos/ics/issues/421)
-- [Epoch number discussion](https://github.com/cosmos/ics/issues/439)
-- [Upgrade plan discussion](https://github.com/cosmos/ics/issues/445)
+- [Prior discussion](https://github.com/cosmos/ibc/issues/421)
+- [Epoch number discussion](https://github.com/cosmos/ibc/issues/439)
+- [Upgrade plan discussion](https://github.com/cosmos/ibc/issues/445)
 - [Migration from gov v1beta1 to gov v1](https://github.com/cosmos/ibc-go/issues/3672)
diff --git a/docs/docs/01-ibc/01-overview.md b/docs/docs/01-ibc/01-overview.md
@@ -157,7 +157,7 @@ under the path and a proof to the counterparty chain.
 Proofs are passed from core IBC to light clients as bytes. It is up to light client implementations to interpret these bytes appropriately.
 
 - The paths that all IBC implementations must use for committing IBC messages is defined in
-[ICS-24 Host State Machine Requirements](https://github.com/cosmos/ics/tree/master/spec/core/ics-024-host-requirements).
+[ICS-24 Host State Machine Requirements](https://github.com/cosmos/ibc/tree/master/spec/core/ics-024-host-requirements).
 - The proof format that all implementations must be able to produce and verify is defined in [ICS-23 Proofs](https://github.com/cosmos/ics23) implementation.
 
 ### [Ports](https://github.com/cosmos/ibc-go/blob/main/modules/core/05-port)

diff --git a/docs/versioned_docs/version-v4.6.x/01-ibc/01-overview.md b/docs/versioned_docs/version-v4.6.x/01-ibc/01-overview.md
@@ -137,7 +137,7 @@ under the path and a proof to the counterparty chain.
 Proofs are passed from core IBC to light-clients as bytes. It is up to light client implementation to interpret these bytes appropriately.
 
 - The paths that all IBC implementations must use for committing IBC messages is defined in
-[ICS-24 Host State Machine Requirements](https://github.com/cosmos/ics/tree/master/spec/core/ics-024-host-requirements). 
+[ICS-24 Host State Machine Requirements](https://github.com/cosmos/ibc/tree/master/spec/core/ics-024-host-requirements). 
 - The proof format that all implementations must be able to produce and verify is defined in [ICS-23 Proofs](https://github.com/confio/ics23) implementation.
 
 ### [Capabilities](https://github.com/cosmos/cosmos-sdk/blob/main/docs/learn/advanced/10-ocap.md)

diff --git a/docs/versioned_docs/version-v5.4.x/01-ibc/01-overview.md b/docs/versioned_docs/version-v5.4.x/01-ibc/01-overview.md
@@ -137,7 +137,7 @@ under the path and a proof to the counterparty chain.
 Proofs are passed from core IBC to light-clients as bytes. It is up to light client implementation to interpret these bytes appropriately.
 
 - The paths that all IBC implementations must use for committing IBC messages is defined in
-[ICS-24 Host State Machine Requirements](https://github.com/cosmos/ics/tree/master/spec/core/ics-024-host-requirements). 
+[ICS-24 Host State Machine Requirements](https://github.com/cosmos/ibc/tree/master/spec/core/ics-024-host-requirements). 
 - The proof format that all implementations must be able to produce and verify is defined in [ICS-23 Proofs](https://github.com/confio/ics23) implementation.
 
 ### [Capabilities](https://github.com/cosmos/cosmos-sdk/blob/main/docs/learn/advanced/10-ocap.md)

diff --git a/docs/versioned_docs/version-v6.3.x/01-ibc/01-overview.md b/docs/versioned_docs/version-v6.3.x/01-ibc/01-overview.md
@@ -137,7 +137,7 @@ under the path and a proof to the counterparty chain.
 Proofs are passed from core IBC to light-clients as bytes. It is up to light client implementation to interpret these bytes appropriately.
 
 - The paths that all IBC implementations must use for committing IBC messages is defined in
-[ICS-24 Host State Machine Requirements](https://github.com/cosmos/ics/tree/master/spec/core/ics-024-host-requirements). 
+[ICS-24 Host State Machine Requirements](https://github.com/cosmos/ibc/tree/master/spec/core/ics-024-host-requirements). 
 - The proof format that all implementations must be able to produce and verify is defined in [ICS-23 Proofs](https://github.com/confio/ics23) implementation.
 
 ### [Capabilities](https://github.com/cosmos/cosmos-sdk/blob/main/docs/learn/advanced/10-ocap.md)

diff --git a/docs/versioned_docs/version-v7.8.x/01-ibc/01-overview.md b/docs/versioned_docs/version-v7.8.x/01-ibc/01-overview.md
@@ -137,7 +137,7 @@ under the path and a proof to the counterparty chain.
 Proofs are passed from core IBC to light-clients as bytes. It is up to light client implementation to interpret these bytes appropriately.
 
 - The paths that all IBC implementations must use for committing IBC messages is defined in
-[ICS-24 Host State Machine Requirements](https://github.com/cosmos/ics/tree/master/spec/core/ics-024-host-requirements). 
+[ICS-24 Host State Machine Requirements](https://github.com/cosmos/ibc/tree/master/spec/core/ics-024-host-requirements). 
 - The proof format that all implementations must be able to produce and verify is defined in [ICS-23 Proofs](https://github.com/cosmos/ics23) implementation.
 
 ### [Capabilities](https://github.com/cosmos/cosmos-sdk/blob/main/docs/learn/advanced/10-ocap.md)

diff --git a/docs/versioned_docs/version-v8.5.x/01-ibc/01-overview.md b/docs/versioned_docs/version-v8.5.x/01-ibc/01-overview.md
@@ -157,7 +157,7 @@ under the path and a proof to the counterparty chain.
 Proofs are passed from core IBC to light-clients as bytes. It is up to light client implementation to interpret these bytes appropriately.
 
 - The paths that all IBC implementations must use for committing IBC messages is defined in
-[ICS-24 Host State Machine Requirements](https://github.com/cosmos/ics/tree/master/spec/core/ics-024-host-requirements).
+[ICS-24 Host State Machine Requirements](https://github.com/cosmos/ibc/tree/master/spec/core/ics-024-host-requirements).
 - The proof format that all implementations must be able to produce and verify is defined in [ICS-23 Proofs](https://github.com/cosmos/ics23) implementation.
 
 ### [Capabilities](https://github.com/cosmos/cosmos-sdk/blob/main/docs/learn/advanced/10-ocap.md)

diff --git a/docs/versioned_docs/version-v9.0.x/01-ibc/01-overview.md b/docs/versioned_docs/version-v9.0.x/01-ibc/01-overview.md
@@ -157,7 +157,7 @@ under the path and a proof to the counterparty chain.
 Proofs are passed from core IBC to light clients as bytes. It is up to light client implementations to interpret these bytes appropriately.
 
 - The paths that all IBC implementations must use for committing IBC messages is defined in
-[ICS-24 Host State Machine Requirements](https://github.com/cosmos/ics/tree/master/spec/core/ics-024-host-requirements).
+[ICS-24 Host State Machine Requirements](https://github.com/cosmos/ibc/tree/master/spec/core/ics-024-host-requirements).
 - The proof format that all implementations must be able to produce and verify is defined in [ICS-23 Proofs](https://github.com/cosmos/ics23) implementation.
 
 ### [Ports](https://github.com/cosmos/ibc-go/blob/main/modules/core/05-port)