initial README links added to docs and training.corda.net

Author: anixon604

.gitignore

@@ -5,7 +5,7 @@
 **/bin/
 */.gradle/
 */.idea/*
-*/.vscode/*
+**/.vscode/*
 **/out/
 **/logs/
 corda-nodeinfo/corda-nodeinfo.iml

Accounts/README.md

@@ -1,14 +1,17 @@
 ## samples-java/Accounts
 
-This folder features Corda Accounts sample projects.
+This folder features Corda Accounts sample projects. Learn more about [Accounts](https://training.corda.net/libraries/accounts-lib/).
 
 ### [Supply Chain](./supplychain):
+
+<img src="../webIDE.png" />
+
 This CorDapp mimics a supply chain transaction, where the deal is incorporated among different teams in the companies on both side of the trade.
 
 ### [Tic Tac Thor](./tictacthor):
-This CorDapp recreates the game of Tic Tac Toe via Corda. It primarilly demonstrates how you can have linear state transactions between cross-node accounts. 
+This CorDapp recreates the game of Tic Tac Toe via Corda. It primarily demonstrates how you can have [LinearState](https://docs.corda.net/docs/corda-os/api-states.html#linearstate) transactions between cross-node accounts. 
 
 
 ### [Worldcup Ticket Booking](./worldcupticketbooking):
-This CorDapp demonstrates an ticket booking system with a collaboration of Corda Account Libray and TokenSDK.
+This CorDapp demonstrates an ticket booking system with a collaboration of Corda [Accounts](https://training.corda.net/libraries/accounts-lib/) and [Tokens](https://training.corda.net/libraries/tokens-sdk/).
 

Accounts/supplychain/README.md

@@ -7,7 +7,8 @@ This sample describes a mock/simple supply chain business flow.
 <p align="center">
   <img src="./Business%20Flow.png" alt="Corda" width="500">
 </p>
-From the above chart, you can see the flow is going back and forth between different parties' accounts. Please follow the instruction below to experience the Accounts library. 
+
+From the above chart, you can see the flow is going back and forth between different parties' accounts. Please follow the instruction below to experience the [Accounts](https://training.corda.net/libraries/accounts-lib/) library. 
 
 # Setting up
 Go into the project directory and build the project
@@ -44,9 +45,9 @@ flow start ShareAccountTo acctNameShared: SellerSales, shareTo: Buyer
 flow start ShareAccountTo acctNameShared: SellerFinance, shareTo: Buyer
 flow start ShareAccountTo acctNameShared: SellerInventory, shareTo: ShippingCo
 ```
-This is creating 3 accounts under Seller's node and sharing with their specific conterpartie's node or account.
+This is creating 3 accounts under Seller's node and sharing with their specific conterparty's node or account.
 
-[Optional]: You can run a vaultQuery to see the accoutnInfo that been stored at each node by using: 
+[Optional]: You can run a vaultQuery to see the [AccountInfo](https://training.corda.net/libraries/accounts-lib/#design) that been stored at each node by using: 
 ```
 run vaultQuery contractStateType: com.r3.corda.lib.accounts.contracts.states.AccountInfo
 ```
@@ -70,7 +71,7 @@ flow start InternalMessage fromWho: BuyerProcurement, whereTo: BuyerFinance, mes
 [Optional verification]: run ```flow start ViewInboxByAccount acctname: BuyerFinance``` at Buyer' node terminal
 
 ## Step 3: Buyer's finance team send a payment to Seller's finance team
-Navigatie to Buyer's node terminal and type in:
+Navigate to Buyer's node terminal and type in:
 ```
 flow start SendPayment whoAmI: BuyerFinance, whereTo: SellerFinance, amount: 500
 ```

Accounts/tictacthor/README.md

@@ -1,5 +1,6 @@
 # Tic Tac Thor
-This CorDapp recreates the game of Tic Tac Toe via Corda. It primarilly demonstrates how you can have linear state transactions between cross-node accounts.
+This CorDapp recreates the game of Tic Tac Toe via Corda. It primarilly demonstrates how you can have [LinearState](https://docs.corda.net/docs/corda-os/api-states.html#linearstate) transactions between cross-node accounts.
+
 <p align="center">
   <img src="https://upload.wikimedia.org/wikipedia/commons/thumb/3/32/Tic_tac_toe.svg/1024px-Tic_tac_toe.svg.png" alt="Corda" width="200">
 </p>
@@ -30,10 +31,10 @@ From here, you can start play the game by changing the very last number from the
 │3│4│5│        ->        │ │X│ │
 │6│7│8│                  │ │ │ │
 ```
-The Game will automatically end when one player win the game. 
+The Game will automatically end when one player wins the game. 
 You can also run `run vaultQuery contractStateType: net.corda.samples.tictacthor.states.BoardState` at any given time to see the board games stored in vault. 
 
-now if you want to fast fard the game, Play the following moves in order:
+now if you want to fast forward the game, Play the following moves in order:
 According to syntax: we should have `http://localhost:8080/submitMove/PeterLi/DavidWinner/3` for the first move below.
 ```
 * Peter: 3                                  │O│ │ │
@@ -48,7 +49,7 @@ We can play a bit more about the accounts. Now let's create two accounts, a new
 * Create an account on SoE node: `http://localhost:8090/createAccount/ThorG`
 Now, try to have Anthony play a game with Thor while start a new game between Peter and David. It worked! 
 
-One key feature about account is that, each account's data is segregated, meaning each account will not be able to see other account's data. In this sample cordapp, the game is queried by account name. Therefore, we see that each account only knows about the game that he participated. Account Peter doesn't know anything about the game between Thor and Anthony. 
+One key feature about account is that, each account's data is segregated, meaning that it can be enforced that each account will not be able to see other account's data. In this sample cordapp, the game is queried by account name. Therefore, we see that each account only knows about the game that he participated. Account Peter doesn't know anything about the game between Thor and Anthony. 
 
 ## Credit 
 This project is inspired and evolved from a simple [tic-tac-toe](https://github.com/thorgilman/tictactoe) game on Corda by Thor Gilman. 

Accounts/worldcupticketbooking/README.md

@@ -3,7 +3,7 @@
 
 ## Introduction
 This sample shows you how to integrate accounts and tokens. This sample talks about a scenario where typically when the Cricket season starts, BCCI (Board of Control for Cricket) starts selling tickets.
-As of now there are multiple dealers whom the BCCI issues tickets and further these dealers sell tickets to their client. We are trying to simulate similar functionality maintaining the entore issuance and selling
+As of now there are multiple dealers whom the BCCI issues tickets and further these dealers sell tickets to their client. We are trying to simulate similar functionality maintaining the entire issuance and selling
 of the tickets on Corda Platform.
 
 ## Flow logic of the sample application 
@@ -57,7 +57,7 @@ Run the above command on the Bank node, which will issue 20 USD to buyer1 accoun
 flow start QuerybyAccount whoAmI: buyer1
 ```
 You can check balance of buyer1 account at Dealer1's node
-[Option] You can also run the below command to confirm if 20 USD fungible tokens are stored at Dealer1's node. The current holder field in the output will be an AnonymousParty which specifies an account.
+[Option] You can also run the below command to confirm if 20 USD fungible tokens are stored at Dealer1's node. The current holder field in the output will be an [AnonymousParty](https://docs.corda.net/docs/corda-os/4.4/api-identity.html#party) which specifies an account.
 ```
 run vaultQuery contractStateType : com.r3.corda.lib.tokens.contracts.states.FungibleToken
 ```
@@ -94,7 +94,7 @@ Note that, the current holder it will be a key representing the account.
 flow start DVPAccountsOnSameNode tokenId: <XXX-XXX-XXXX-XXXXX>, buyerAccountName: buyer1, sellerAccountName: agent1, costOfTicket: 5, currency: USD
 ```
 
-This is the DVP flow where the buyer(buyer1 account on Dealer1 node) account will pay cash to seller account(agent1 account on Dealer1 node), and the seller accountwill transfer the ticket token to the buyer. Again, replace the `<XXX-XXX-XXXX-XXXXX>` with the uuid generated in step 6.
+This is the DVP flow where the buyer(buyer1 account on Dealer1 node) account will pay cash to seller account(agent1 account on Dealer1 node), and the seller account will transfer the ticket token to the buyer. Again, replace the `<XXX-XXX-XXXX-XXXXX>` with the uuid generated in step 6.
 
 ### Step 7
 Now lets continue the flow logic to intiate an ticket sale between buyer1 and buyer3. Go to Dealer2 node and run the following code:
@@ -121,7 +121,7 @@ At Dealer2 node
 flow start QuerybyAccount whoAmI: buyer3
 
 ```
-Confirm who owns the FungibleToken (cash) and NonFungibleToken (ticket) again by running this on Dealer1's node.
+Confirm who owns the [FungibleToken](https://training.corda.net/libraries/tokens-sdk/#fungibletoken) (cash) and [NonFungibleToken](https://training.corda.net/libraries/tokens-sdk/#nonfungibletoken) (ticket) again by running this on Dealer1's node.
 
 
 ## Further Reading

Advanced/README.md

@@ -3,8 +3,8 @@
 This folder features Advanced sample projects, each of them demonstrates a complex cordapp that uses multiple features of Corda.
 
 ### [auction cordapp](./auction-cordapp):
-An blockchain application that leverages different features of Corda like SchedulableState, StatePointer
-and OwnableState. It also demonstrates how to perform a DvP (Delivery vs Payment) transaction on Corda.
+An blockchain application that leverages different features of Corda like [SchedulableState](https://docs.corda.net/docs/corda-os/event-scheduling.html#how-to-implement-scheduled-events), [StatePointer](https://docs.corda.net/docs/corda-os/api-states.html#state-pointers)
+and [OwnableState](https://docs.corda.net/docs/corda-os/api-states.html#ownablestate). It also demonstrates how to perform a DvP (Delivery vs Payment) transaction on Corda.
 
 ### [negotiation cordapp](./negotiation-cordapp):
 An application that depicts the businsess negotiation and communication process over a distributed ledger system.

Advanced/auction-cordapp/README.md

@@ -1,7 +1,7 @@
 # auction cordapp
 
 This CorDapp serves as a demo of building an auction application on Corda. It leverages
-different features of Corda like `SchedulableState`, `StatePointer` and `OwnableState`. It also demonstrate
+different features of Corda like [SchedulableState](https://docs.corda.net/docs/corda-os/event-scheduling.html#how-to-implement-scheduled-events), [StatePointer](https://docs.corda.net/docs/corda-os/api-states.html#state-pointers) and [OwnableState](https://docs.corda.net/docs/corda-os/api-states.html#ownablestate). It also demonstrate
 how to perform a DvP (Delivery vs Payment) transaction on Corda.
 
 It has a full-functional client included and an angular UI to interact with the nodes.

Advanced/negotiation-cordapp/README.md

@@ -1,4 +1,4 @@
-.# negotiation cordapp
+# negotiation cordapp
 
 This CorDapp shows how multi-party negotiation is handled on the Corda ledger, in the absence of an API for user
 interaction.
@@ -22,7 +22,7 @@ We start with the proposal flow implemented in [ProposalFlow.java](./workflows/s
 The modification of the proposal is implemented in [ModificationFlow.java](./workflows/src/main/java/negotiation/flows/ModificationFlow.java#L42-L49).
 
 
-In the [AcceptanceFlow](./workflows/src/main/java/negotiation/flows/AcceptanceFlow.java#L42-L75), we receive the modified ProposalState and it's converted into a TradeState.
+In the [AcceptanceFlow.java](./workflows/src/main/java/negotiation/flows/AcceptanceFlow.java#L42-L75), we receive the modified ProposalState and it's converted into a TradeState.
 
 
 

Advanced/obligation-cordapp/README.md

@@ -20,7 +20,7 @@ The first flows are the ones that issue the original cash and assets. You can fi
 The next flow is the one that transfers ownership of that asset over to another party. That can be found in [IOUTransferFlow.java](./workflows/src/main/java/net/corda/samples/flows/IOUTransferFlow.java#L132-L159).
 
 
-Finally, once we have the ability to transfer assets, we just need to settle up. That functiionality can be found [here in IOUSettleFlow.java](./workflows/src/main/java/net/corda/samples/flows/IOUSettleFlow.java#L54-L116)
+Finally, once we have the ability to transfer assets, we just need to settle up. That functiionality can be found here in [IOUSettleFlow.java](./workflows/src/main/java/net/corda/samples/flows/IOUSettleFlow.java#L54-L116)
 
 
 

Basic/README.md

@@ -1,6 +1,6 @@
 ## samples-java/basic-cordapps
 
-This folder features basic sample projects, each of them demonstrates low level cordapp functionalities, such rpc connection, messing, and etc.
+This folder features basic sample projects, each of them demonstrates low level cordapp functionalities, such [RPC connection](https://docs.corda.net/docs/corda-os/api-rpc.html#api-rpc-operations), messaging, etc.
 
 ### [database access](./flow-database-access):
 This CorDapp provides a simple example of how the node database can be accessed within flows. In this case, the flows maintain a table of cryptocurrency values in the node's database.