From 5afe6732f9c01b94b421ec8aac5e13c42b12430d Mon Sep 17 00:00:00 2001 From: Leo Date: Wed, 7 Jul 2021 21:35:59 +0200 Subject: [PATCH] design: fix a typo Change-Id: I49f1e3b35737ee87c3ed6bef5f880a0b8e627a9d --- design/0001_generic_message_passing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/design/0001_generic_message_passing.md b/design/0001_generic_message_passing.md index 7d97384f7..80f17c7f3 100644 --- a/design/0001_generic_message_passing.md +++ b/design/0001_generic_message_passing.md @@ -182,7 +182,7 @@ differently shaped problem, leading to a different design. IBC specifies a cross-chain communication protocol with high-level semantics like channels, ports, acknowledgements, ordering and timeouts. It is a stream abstraction on top of a packet/datagram transport, vaguely similar to the TCP/IP -protocol. IBC is part of the Cosmos Internet of Blockchain vision scalability vision, with hundreds or even thousands of +protocol. IBC is part of the Cosmos Internet of Blockchain scalability vision, with hundreds or even thousands of sovereign IBC-compatible chains (called "zones") communicating via IBC using a hub-and-spoke topology. Data availability is provided by permissionless relayers.