From 039f48d6dc66bd73e3cc21eb7457a2256ee48f51 Mon Sep 17 00:00:00 2001
From: TXH2020 <1001.tejas@gmail.com>
Date: Wed, 13 Dec 2023 14:57:31 +0530
Subject: [PATCH] docs(README): corrected spelling mistakes in flavours,
workflows and different.
These are the corrections:
flavors-> flavours(line 17)
workfow-> workflow(line 17)
differemt-> different(line 21).
Signed-off-by: TXH2020 <1001.tejas@gmail.com>
---
README.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/README.md b/README.md
index 6fa501420f..5db19da20c 100644
--- a/README.md
+++ b/README.md
@@ -14,11 +14,11 @@ the [Hyperledger Project Incubation Exit Criteria document](https://wiki.hyperle
## Scope of Project
-The existence of several blockchain and distributed ledger technologies of different flavors in the market as well as networks of varying scopes and sizes built on them necessitates the need for interoperability and integration, lest we end up with a fragmented ecosystem where digital assets and the workfows (often contracts) governing them remain isolated in silos. The solution to this is not to force all chains to coalesce (i.e., "*a single chain to rule them all*") but rather enable the networks to orchestrate transactions spanning their boundaries without sacrificing security, privacy, or governance autonomy (i.e., self-sovereignty). Hyperledger Cacti offers a family of protocols, modules, libraries, and SDKs, that can enable one network to be interoperable with, and carry out transactions directly with, another while eschewing the need for a central or common settlement chain. Cacti will allow networks to share ledger data, and exchange and transfer assets atomically, and manage identities, across their boundaries, as illustrated in the figure below.
+The existence of several blockchain and distributed ledger technologies of different flavours in the market as well as networks of varying scopes and sizes built on them necessitates the need for interoperability and integration, lest we end up with a fragmented ecosystem where digital assets and the workflows (often contracts) governing them remain isolated in silos. The solution to this is not to force all chains to coalesce (i.e., "*a single chain to rule them all*") but rather enable the networks to orchestrate transactions spanning their boundaries without sacrificing security, privacy, or governance autonomy (i.e., self-sovereignty). Hyperledger Cacti offers a family of protocols, modules, libraries, and SDKs, that can enable one network to be interoperable with, and carry out transactions directly with, another while eschewing the need for a central or common settlement chain. Cacti will allow networks to share ledger data, and exchange and transfer assets atomically, and manage identities, across their boundaries, as illustrated in the figure below.
-As a fusion of two earlier systems (Cactus and Weaver) that have similar philosophies and goals, yet offer distinct mechanisms backed by differemt design and trust assumptions, Cacti offers a spectrum of selectable and configurable features for cross-network transaction orchestrations. An example illustrated below shows how distributed applications running on Fabric and Besu ledgers respectively can carry out the same set of cross-network transactions using the **Node Server** (Cactus legacy) or through **Relays** (Weaver legacy).
+As a fusion of two earlier systems (Cactus and Weaver) that have similar philosophies and goals, yet offer distinct mechanisms backed by different design and trust assumptions, Cacti offers a spectrum of selectable and configurable features for cross-network transaction orchestrations. An example illustrated below shows how distributed applications running on Fabric and Besu ledgers respectively can carry out the same set of cross-network transactions using the **Node Server** (Cactus legacy) or through **Relays** (Weaver legacy).
@@ -62,4 +62,4 @@ We welcome contributions to Hyperledger Cacti in many forms, and there’s alway
Please review [contributing](/CONTRIBUTING.md) guidelines to get started.
## License
-This distribution is published under the Apache License Version 2.0 found in the [LICENSE](/LICENSE) file.
+This distribution is published under the Apache License Version 2.0 found in the [LICENSE](/LICENSE) file.
\ No newline at end of file