1 files changed, 12 insertions, 23 deletions

diff --git a/content/transaction_docs.md b/content/transaction_docs.md
index 05c1534..f9e8947 100644
--- a/content/transaction_docs.md
+++ b/content/transaction_docs.md
@@ -7,17 +7,14 @@ weight = 6
 A transaction request between `source` and `target` to move `amount` Gradecoin.
 
 # Requests
-
 ## GET
 A HTTP `GET` request to [/transaction](/transaction) endpoint will return the current list of pending transactions.
 
 ## POST
-
-A HTTP `POST` request with Authorization using JWT to [/transaction](/transactions) will allow you to propose your own transactions.
+A HTTP `POST` request with Authorization using [JWT](@/JWT.md) to [/transaction](/transaction) will allow you to propose your own transactions.
 
 # Fields
 ```
-by: Fingerprint
 source: Fingerprint
 target: Fingerprint
 amount: unsigned 16 bit integer
@@ -25,28 +22,20 @@ timestamp: ISO 8601 <date>T<time>
 ```
 
 # Hash
-
-`tha` field in [jwt documentation](@/JWT.md) in fact stands for "The Hash", in the case of a post request for a transaction, you need the Md5 hash of the serialized JSON representation of transaction. The resulting JSON string should look something like;
+`tha` field in [jwt documentation](@/JWT.md) in fact stands for "The Hash".
+In the context of a transaction proposal, you need the [Md5](https://en.wikipedia.org/wiki/MD5) hash of the serialized JSON representation of transaction.
+Serializing in this context is a simple JSON to string conversion with key, value pairs enclosed with quotation marks (").
+The resulting JSON string should look something like;
 
 ```
-{"by":"foo","source":"bar","target":"baz","amount":2,"timestamp":"2021-04-18T21:49:00"}
+{"source":"bar","target":"baz","amount":2,"timestamp":"2021-04-18T21:49:00"}
 ```
 
 Or; without any whitespace, separated with `:` and `,`.
 
-# Bank
-
-There is a `bank` account with Fingerprint `31415926535897932384626433832795028841971693993751058209749445923`
-
-{% tidbit() %}
-First 64 digits of Pi
-{% end %}
-
-This is the only account that will let you _withdraw_ from them.
-
-```
-by: this has to be your Fingerprint
-source: this can be either you or the bank
-target: this can be a valid fingerprint or yourself if source is the bank
-...
-```
+# Transaction Rules
+- Transactions should be sent from your account (`source`) to any other account (`target`).
+- Transactions generate traffic which is something we desperately need in Gradecoin, so for every transaction you send, some Gradecoin will be generated out of thin air and will appear on the target.
+- Don't worry if your transaction goes unaccepted! Transactions do not disappear until they are committed into the ledger with a block.
+- Every transaction has a unique ID generated from the `source` and `target` fields. No two transaction with the same ID can appear on the pending transaction list [/transactions](/transaction)
+- Transactions have an upper amount limit.