Merge "[FAB-17032] Fix some errors in the doc."

hyperledger · Nov 14, 2019 · 048351a · 048351a
2 parents a282f71 + 1e39899
commit 048351a
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/docs/source/developapps/analysis.md b/docs/source/developapps/analysis.md
@@ -181,7 +181,7 @@ proof of the mutual agreement among the two parties that are part of the deal.
 ### Redeem
 
 The **redeem** transaction for paper 00001 represents the end of its lifecycle.
-In our relatively simple example, DigiBank initiates the transaction which
+In our relatively simple example, HedgeMatic initiates the transaction which
 transfers the commercial paper back to MagnetoCorp:
 
 ```

diff --git a/docs/source/developapps/application.md b/docs/source/developapps/application.md
@@ -5,7 +5,7 @@
 An application can interact with a blockchain network by submitting transactions
 to a ledger or querying ledger content. This topic covers the mechanics of how
 an application does this; in our scenario, organizations access PaperNet using
-applications which invoke **issue**, **sell** and **redeem** transactions
+applications which invoke **issue**, **buy** and **redeem** transactions
 defined in a commercial paper smart contract. Even though MagnetoCorp's
 application to issue a commercial paper is basic, it covers all the major points
 of understanding.
@@ -351,7 +351,7 @@ you're interested in what the SDK does under the covers, read the detailed
 That’s it! In this topic you’ve understood how to call a smart contract from a
 sample application by examining how MagnetoCorp's application issues a new
 commercial paper in PaperNet. Now examine the key ledger and smart contract data
-structures are designed by in the [architecture topic](./architecture.md) behind
+structures are designed by in the [architecture topic](./architecture.html) behind
 them.
 
 <!--- Licensed under Creative Commons Attribution 4.0 International License