Skip to content

Commit 69d9375

Browse files
authoredJan 13, 2025··
typos README.md (#1183)
1 parent 221f635 commit 69d9375

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed
 

‎spec/ics-001-ics-standard/README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -11,23 +11,23 @@ modified: 2019-08-25
1111

1212
## What is an ICS?
1313

14-
An inter-chain standard (ICS) is a design document describing a particular protocol,
14+
An interchain standard (ICS) is a design document describing a particular protocol,
1515
standard, or feature expected to be of use to the Cosmos ecosystem.
1616
An ICS should list the desired properties of the standard, explain the design rationale, and
1717
provide a concise but comprehensive technical specification. The primary ICS author
1818
is responsible for pushing the proposal through the standardisation process, soliciting
1919
input and support from the community, and communicating with relevant stakeholders to
2020
ensure (social) consensus.
2121

22-
The inter-chain standardisation process should be the primary vehicle for proposing
22+
The interchain standardisation process should be the primary vehicle for proposing
2323
ecosystem-wide protocols, changes, and features, and ICS documents should persist after
2424
consensus as a record of design decisions and an information repository for future implementers.
2525

26-
Inter-chain standards should *not* be used for proposing changes to a particular blockchain
26+
Interchain standards should *not* be used for proposing changes to a particular blockchain
2727
(such as the Cosmos Hub), specifying implementation particulars (such as language-specific data structures),
2828
or debating governance proposals on existing Cosmos blockchains (although it is possible
2929
that individual blockchains in the Cosmos ecosystem may utilise their governance processes
30-
to approve or reject inter-chain standards).
30+
to approve or reject interchain standards).
3131

3232
## Components
3333

0 commit comments

Comments
 (0)
Please sign in to comment.