docs changes

Signed-off-by: sandeep.nishad1 <[email protected]>

Author: sandeepnRES

docs/docs/external/getting-started/interop/asset-exchange.md

@@ -62,25 +62,25 @@ run the following steps:
        ./bin/fabric-cli asset exchange-step --step=6 --recipient=bob --locker=alice --target-network=network1 --param=bond01:a03 --secret=<hash-pre-image>
        ```
 
-     Above steps complete a successful asset exchange between two Fabric networks. 
-     In addition to above commands, following are the extra options:
-     - _In case_, `alice` wants to unlock the bond asset, run the following to trigger `alice`'s re-claim for `bond01:a03` locked in `network1`:
+     The above steps complete a successful asset exchange between two Fabric networks. 
+     In addition to the above commands, following are the extra options:
+     - If `alice` wants to unlock the bond asset, run the following to trigger `alice`'s re-claim for `bond01:a03` locked in `network1`:
        ```bash
        ./bin/fabric-cli asset exchange-step --step=7 --locker=alice --recipient=bob --target-network=network1 --param=bond01:a03
        ```
-     - _In case_, `bob` wants to unlock the token asset, run the following to trigger `bob`'s re-claim for `token1:100` locked in `network2`:
+     - If `bob` wants to unlock the token asset, run the following to trigger `bob`'s re-claim for `token1:100` locked in `network2`:
        ```bash
        ./bin/fabric-cli asset exchange-step --step=8 --locker=bob --recipient=alice --target-network=network2 --contract-id=<contract-id>
        ```
 
 ## Fabric with Corda
 
-We will demonstrate asset exchange of a bond in fabric `network1` with tokens on `Corda_Network`.
-For fabric commands, run from `samples/fabric/fabric-cli` folder, and for Corda commands, run from `samples/corda/corda-simple-application` folder. Here `Alice` and `Bob` in fabric `network1` correspond to `PartyA` (`CORDA_PORT=10006`) and `PartyB` (`CORDA_PORT=10009`) in `Corda_Network` respectively. Following are the step-by-step asset exchange process:
+We will demonstrate asset exchange of a bond in Fabric `network1` with tokens on `Corda_Network`.
+For Fabric commands, run from `samples/fabric/fabric-cli` folder, and for Corda commands, run from `samples/corda/corda-simple-application` folder. Here `Alice` and `Bob` in Fabric `network1` correspond to `PartyA` (`CORDA_PORT=10006`) and `PartyB` (`CORDA_PORT=10009`) in `Corda_Network` respectively. Following are the step-by-step asset exchange process:
 
 (_Note: the hash pair used in following steps can be replaced by any valid `sha256` hash pair_)
 
-- Run the following to verify the status of the bond assets owned by `alice` and `bob` in the fabric network `network1` from `samples/fabric/fabric-cli` folder:
+- Run the following to verify the status of the bond assets owned by `alice` and `bob` in the Fabric network `network1` from `samples/fabric/fabric-cli` folder:
  ```bash
  ./scripts/getAssetStatus.sh
  ```
@@ -109,12 +109,12 @@ For fabric commands, run from `samples/fabric/fabric-cli` folder, and for Corda
   ```bash
   CORDA_PORT=10006 ./clients/build/install/clients/bin/clients claim-asset --secret=secrettext --contract-id=<contract-id>
   ```
-  (_Note: Here the `PartyB` can see the node's log to get the revealed the hash preimage, to use it to claim bond in fabric network._)
+  (_Note: Here the `PartyB` can see the node's log to get the revealed the hash preimage, to use it to claim bond in Fabric network._)
 - Run the following to trigger `bob`'s claim for `bond01:a03` locked by `alice` in `network1`:
   ```bash
   ./bin/fabric-cli asset exchange-step --step=6 --recipient=bob --locker=alice --target-network=network1 --param=bond01:a03 --secret=secrettext
   ```
-- Run the following to verify the status of the bond assets owned by `alice` and `bob` in the fabric network `network1` from `samples/fabric/fabric-cli` folder:
+- Run the following to verify the status of the bond assets owned by `alice` and `bob` in the Fabric network `network1` from `samples/fabric/fabric-cli` folder:
    ```bash
    ./scripts/getAssetStatus.sh
    ```
@@ -123,14 +123,13 @@ For fabric commands, run from `samples/fabric/fabric-cli` folder, and for Corda
   ./scripts/getAssetStatus.sh
   ```
 
-
-Above steps complete a successful asset exchange between Fabric and Corda networks. 
-In addition to above commands, following are the extra options:
-- _In case_, `alice` wants to unlock the bond asset, run the following to trigger `alice`'s re-claim for `bond01:a03` locked in `network1`:
+The above steps complete a successful asset exchange between Fabric and Corda networks. 
+In addition to the above commands, following are the extra options:
+- If `alice` wants to unlock the bond asset, run the following to trigger `alice`'s re-claim for `bond01:a03` locked in `network1`:
   ```bash
   ./bin/fabric-cli asset exchange-step --step=7 --locker=alice --recipient=bob --target-network=network1 --param=bond01:a03
   ```
-- _In case_, `PartyB` wants to unlock the token asset, run the following to trigger unlock for `t1:50` locked in `Corda_Network`:
+- If `PartyB` wants to unlock the token asset, run the following to trigger unlock for `t1:50` locked in `Corda_Network`:
   ```bash
   CORDA_PORT=10009 ./clients/build/install/clients/bin/clients unlock-asset --contract-id=<contract-id>
   ```
@@ -167,7 +166,7 @@ We will demonstrate asset exchange of a tokens in `Corda_Network` with tokens on
   ```bash
   CORDA_PORT=30006 ./clients/build/install/clients/bin/clients claim-asset --secret=secrettext --contract-id=<contract-id-2>
   ```
-  (_Note: Here the `PartyB` can see the node's log to get the revealed the hash preimage, to use it to claim bond in fabric network._)
+  (_Note: Here the `PartyB` can see the node's log to get the revealed the hash preimage, to use it to claim bond in Fabric network._)
 - Run the following to trigger `PartyB`'s claim for `30` units of token type `t1` locked by `PartyA` in `Corda_Network`:
   ```bash
   CORDA_PORT=10006 ./clients/build/install/clients/bin/clients claim-asset --secret=secrettext --contract-id=<contract-id-1>
@@ -178,13 +177,13 @@ We will demonstrate asset exchange of a tokens in `Corda_Network` with tokens on
   ```
 
 
-Above steps complete a successful asset exchange between two Corda networks. 
-In addition to above commands, following are the extra options:
-- _In case_, `PartyA` wants to unlock the token `t1:30` asset, run the following to trigger `PartyA`'s re-claim in `Corda_Network`:
+The above steps complete a successful asset exchange between two Corda networks. 
+In addition to the above commands, following are the extra options:
+- If `PartyA` wants to unlock the token `t1:30` asset, run the following to trigger `PartyA`'s re-claim in `Corda_Network`:
   ```bash
   CORDA_PORT=10006 ./clients/build/install/clients/bin/clients unlock-asset --contract-id=<contract-id-1>
   ```
-- _In case_, `PartyB` wants to unlock the token `t2:50` asset, run the following to trigger `PartyB`'s re-claim in `Corda_Network2`:
+- If `PartyB` wants to unlock the token `t2:50` asset, run the following to trigger `PartyB`'s re-claim in `Corda_Network2`:
   ```bash
   CORDA_PORT=30009 ./clients/build/install/clients/bin/clients unlock-asset --contract-id=<contract-id-2>
   ```

docs/docs/external/getting-started/interop/data-sharing.md

@@ -11,7 +11,7 @@ title: Data Sharing
 
 This document lists sample ways in which you can exercise the data-sharing interoperation protocol on the test network [launched earlier](../test-network/overview).
 
-Once the networks, relays, and drivers have been launched, and the ledgers bootstrapped, you can trigger three different interoperation flows corresponding to distinct data-sharing combinations as follows:
+Once the networks, relays, and drivers have been launched, and the ledgers bootstrapped, you can trigger four different interoperation flows corresponding to distinct data-sharing combinations as follows:
 1. **Corda to Corda**: Either Corda network requests state and proof from another Corda network
 2. **Corda to Fabric**: The Corda network requests state and proof from either Fabric network
 3. **Fabric to Corda**: Either Fabric network requests state and proof from the Corda network
@@ -31,11 +31,11 @@ To test the scenario where `Corda_Network` requests the value of the state (key)
     ```bash
     NETWORK_NAME=Corda_Network CORDA_PORT=10006 ./clients/build/install/clients/bin/clients request-state localhost:9081 localhost:9082/Corda_Network2/localhost:30006#com.cordaSimpleApplication.flow.GetStateByKey:H
     ```
-  * If Relays and Drivers are deployed in the Docker containers:
+  * If Relays and Drivers are deployed in Docker containers:
     ```bash
     NETWORK_NAME=Corda_Network CORDA_PORT=10006 ./clients/build/install/clients/bin/clients request-state localhost:9081 relay-corda2:9082/Corda_Network2/corda_network2_partya_1:10003#com.cordaSimpleApplication.flow.GetStateByKey:H
     ```
-- Query the value of the requested state, using key `H` in `Corda_Network` by running the following command:
+- Query the value of the requested state using key `H` in `Corda_Network` by running the following command:
   ```bash
   NETWORK_NAME=Corda_Network CORDA_PORT=10006 ./clients/build/install/clients/bin/clients get-state H
   ```
@@ -93,7 +93,7 @@ To test the scenario where `Corda_Network` requests the value of the state (key)
   NETWORK_NAME=Corda_Network CORDA_PORT=10006 ./clients/build/install/clients/bin/clients get-state Arcturus
   ```
 
-**Note:** You can perform the same data transfer between `Corda_Network2` and either Fabric networks, by setting the env `CORDA_PORT=30006` (the `Corda_Network2` node's RPC port), `NETWORK_NAME=Corda_Network2`, and using `localhost:9082` (the local relay address) as the first argument.
+**Note:** You can perform the same data transfer between `Corda_Network2` and either Fabric networks, by setting the env `CORDA_PORT=30006` (the `Corda_Network2` node's RPC port), `NETWORK_NAME=Corda_Network2`, and using `localhost:9082` (the local relay address) as the argument following request-state.
 
 ## Fabric to Corda
 

docs/docs/external/getting-started/test-network/setup-local-docker.md

@@ -255,11 +255,11 @@ Build the `corda-simple-application` Cordapp as follows:
 
 ### Corda Network
 
-The Corda network code lies in the `tests/network-setups/corda` folder. You can launch  two corda networks (`Corda_Network` and `Corda_Network2`). The networks use `samples/corda/corda-simple-application` by default, which maintains a state of type `SimpleState`, which is a set of key-value pairs (of strings).
+The Corda network code lies in the `tests/network-setups/corda` folder. You can launch two Corda networks (`Corda_Network` and `Corda_Network2`). The networks use `samples/corda/corda-simple-application` by default, which maintains a state of type `SimpleState`, which is a set of key-value pairs (of strings).
 
 Follow the instructions below to build and launch the network:
 - Navigate to the `tests/network-setups/corda` folder.
-- To spin up the Corda networks with the interoperation Cordapp:
+- To spin up the Corda networks with the Interoperation Cordapps:
   - Each consisting of 1 node and a notary (for data-transfer), run:
     ```bash
     make start-local
@@ -320,11 +320,11 @@ Run a Corda driver as follows:
   ```
   DOCKER_IMAGE_NAME=weaver-corda-driver
   ```
-- To deploy corda driver for `Corda_Network`, run:
+- To deploy Corda driver for `Corda_Network`, run:
   ```bash
   make deploy COMPOSE_ARG='--env-file docker-testnet-envs/.env.corda'
   ```
-- To deploy corda driver for `Corda_Network2`, run:
+- To deploy Corda driver for `Corda_Network2`, run:
   ```bash
   make deploy COMPOSE_ARG='--env-file docker-testnet-envs/.env.corda2'
   ```

docs/docs/external/getting-started/test-network/setup-local.md

@@ -277,11 +277,11 @@ Build the `corda-simple-application` Cordapp as follows:
 
 ### Corda Network
 
-The Corda network code lies in the `tests/network-setups/corda` folder. You can launch two corda networks (`Corda_Network` and `Corda_Network2`). This networks use `samples/corda/corda-simple-application` by default, which maintains a state of type `SimpleState`, which is a set of key-value pairs (of strings).
+The Corda network code lies in the `tests/network-setups/corda` folder. You can launch two Corda networks (`Corda_Network` and `Corda_Network2`). These networks use `samples/corda/corda-simple-application` by default, which maintains a state of type `SimpleState`, which is a set of key-value pairs (of strings).
 
 Follow the instructions below to build and launch the network:
 - Navigate to the `tests/network-setups/corda` folder.
-- To spin up the Corda networks with the interoperation Cordapp:
+- To spin up the Corda networks with the Interoperation Cordapps:
   - Each consisting of 1 node and a notary (for data-transfer), run:
     ```bash
     make start-local
@@ -313,7 +313,7 @@ The relay was built earlier, so you just need to use a different configuration f
 Run a relay in host as follows:
 - Navigate to the `core/relay` folder.
 - (Make sure you've already built the relay by running `make`.)
-- Run the following, to start relay for `Corda_Network`:
+- Run the following to start relay for `Corda_Network`:
   ```bash
   RELAY_CONFIG=config/Corda_Relay.toml cargo run --bin server
   ```
@@ -324,7 +324,7 @@ Run a relay in host as follows:
   Relay Name: "Corda_Relay"
   RelayServer listening on [::1]:9081
   ```
-- Run the following, to start relay for `Corda_Network2`:
+- Run the following to start relay for `Corda_Network2`:
   ```bash
   RELAY_CONFIG=config/Corda_Relay2.toml cargo run --bin server
   ```
@@ -353,15 +353,15 @@ Build the Corda driver module as follows:
 
 Run a Corda driver as follows:
 - Navigate to the `core/drivers/corda-driver` folder.
-- Run the following, to start corda driver for `Corda_Network`:
+- Run the following to start Corda driver for `Corda_Network`:
   ```bash
   ./build/install/corda-driver/bin/corda-driver
   ```
   If the driver starts successfully, it should log the following message on your terminal:
   ```
   Corda driver gRPC server started. Listening on port 9099
   ```
-- Run the following, to start corda driver for `Corda_Network2`:
+- Run the following to start Corda driver for `Corda_Network2`:
   ```bash
   DRIVER_PORT=9098 ./build/install/corda-driver/bin/corda-driver
   ```

docs/docs/external/getting-started/test-network/setup-packages-docker.md

@@ -145,7 +145,7 @@ Using the sequence of instructions below, you can start a Corda network and run
 
 ### Corda Network
 
-The Corda network code lies in the `tests/network-setups/corda` folder. You can launch two corda networks (`Corda_Network` and `Corda_Network2`). This networks use `samples/corda/corda-simple-application` by default, which maintains a state of type `SimpleState`, which is a set of key-value pairs (of strings).
+The Corda network code lies in the `tests/network-setups/corda` folder. You can launch two Corda networks (`Corda_Network` and `Corda_Network2`). These networks use `samples/corda/corda-simple-application` by default, which maintains a state of type `SimpleState`, which is a set of key-value pairs (of strings).
 Following steps will build above cordapp and a corda-client as well in `samples/corda/client`.
 
 #### Running with Interoperation Cordapp from Github Packages
@@ -154,7 +154,7 @@ Follow the instructions below to build and launch the network:
 - Navigate to the `tests/network-setups/corda` folder.
 - Create copy of `github.properties.template` as `github.properties`.
 - Replace `<GITHUB email>` with your github email, and `<GITHUB Personal Access Token>` with the access token created [above](#package-access-token).
-- To spin up the Corda networks with the interoperation Cordapp:
+- To spin up the Corda networks with the Interoperation Cordapps:
   - Each consisting of 1 node and a notary (for data-transfer), run:
     ```bash
     make start
@@ -198,11 +198,11 @@ Navigate to the `core/relay` folder and run a relay for `Corda_Network` in docke
 Run a Corda driver as follows:
 - Navigate to the `core/drivers/corda-driver` folder.
 - There's a `.env.corda` file in `docker-testnet-envs` directory, that will be used to start a corda driver in docker.
-- To deploy corda driver for `Corda_Network`, run:
+- To deploy Corda driver for `Corda_Network`, run:
   ```bash
   make deploy COMPOSE_ARG='--env-file docker-testnet-envs/.env.corda'
   ```
-- To deploy corda driver for `Corda_Network2`, run:
+- To deploy Corda driver for `Corda_Network2`, run:
   ```bash
   make deploy COMPOSE_ARG='--env-file docker-testnet-envs/.env.corda2'
   ```

docs/docs/external/getting-started/test-network/setup-packages.md

@@ -193,7 +193,7 @@ Using the sequence of instructions below, you can start a Corda network and run
 
 ### Corda Network
 
-The Corda network code lies in the `tests/network-setups/corda` folder. You can launch two corda networks (`Corda_Network` and `Corda_Network2`). This networks use `samples/corda/corda-simple-application` by default, which maintains a state of type `SimpleState`, which is a set of key-value pairs (of strings).
+The Corda network code lies in the `tests/network-setups/corda` folder. You can launch two Corda networks (`Corda_Network` and `Corda_Network2`). These networks use `samples/corda/corda-simple-application` by default, which maintains a state of type `SimpleState`, which is a set of key-value pairs (of strings).
 Following steps will build above cordapp and a corda-client as well in `samples/corda/client`.
 
 #### Running with Interoperation Cordapp from Github Packages
@@ -202,7 +202,7 @@ Follow the instructions below to build and launch the network:
 - Navigate to the `tests/network-setups/corda` folder.
 - Create a copy of `github.properties.template` as `github.properties`.
 - Replace `<GITHUB email>` with your github email, and `<GITHUB Personal Access Token>` with the access token created [above](#package-access-token).
-- To spin up the Corda networks with the interoperation Cordapp:
+- To spin up the Corda networks with the Interoperation Cordapps:
   - Each consisting of 1 node and a notary (for data-transfer), run:
     ```bash
     make start
@@ -233,7 +233,7 @@ The relay was built earlier, so you just need to use a different configuration f
 
 Run a relay in host as follows:
 - Navigate to the `core/relay` folder.
-- Run the following, to start relay for `Corda_Network`:
+- Run the following to start relay for `Corda_Network`:
   ```bash
   RELAY_CONFIG=config/Corda_Relay.toml cargo run --bin server
   ```
@@ -244,7 +244,7 @@ Run a relay in host as follows:
   Relay Name: "Corda_Relay"
   RelayServer listening on [::1]:9081
   ```
-- Run the following, to start relay for `Corda_Network2`:
+- Run the following to start relay for `Corda_Network2`:
   ```bash
   RELAY_CONFIG=config/Corda_Relay2.toml cargo run --bin server
   ```
@@ -275,15 +275,15 @@ Build the Corda driver module as follows:
 
 Run a Corda driver as follows:
 - Navigate to the `core/drivers/corda-driver` folder.
-- Run the following, to start corda driver for `Corda_Network`:
+- Run the following to start Corda driver for `Corda_Network`:
   ```bash
   ./build/install/corda-driver/bin/corda-driver
   ```
   If the driver starts successfully, it should log the following message on your terminal:
   ```
   Corda driver gRPC server started. Listening on port 9099
   ```
-- Run the following, to start corda driver for `Corda_Network2`:
+- Run the following to start Corda driver for `Corda_Network2`:
   ```bash
   DRIVER_PORT=9098 ./build/install/corda-driver/bin/corda-driver
   ```