From 8c48482e8c46633de4f59bb59797fd6754fc354a Mon Sep 17 00:00:00 2001
From: Yigit Sever
Date: Sat, 16 Apr 2022 17:31:28 +0300
Subject: Update for 2022 spring

---
 content/block_docs.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

(limited to 'content/block_docs.md')

diff --git a/content/block_docs.md b/content/block_docs.md
index 228277c..2eec2ac 100644
--- a/content/block_docs.md
+++ b/content/block_docs.md
@@ -7,8 +7,8 @@ weight = 10
 > Blocks commit proposed transactions into the ledger.
 > A transaction that do not appear on a valid block is not accepted by the network.
 
-Blocks in Gradecoin are proposed to commit [Transactions](@/transaction_docs.md) that were proposed previously to the system.
-`transaction_list` of the Block should be filled with valid transactions to be committed.
+We use Blocks to commit proposed [Transactions](@/transaction_docs.md) to the ledger in order to realize them.
+`transaction_list` of the Block is filled with valid transactions.
 Blocks are valid when they are proposed with a `nonce` that produces a `hash` value with 6 zeroes (24 bits) at the left hand side.
 
 We are _mining_ using [blake2s](https://www.blake2.net/) algorithm, which produces 256 bit hashes.
@@ -53,7 +53,7 @@ If the resulting hash is valid, then you can create a `Block` JSON object with t
 Fill this with the `hash` value you found during the mining process.
 
 # Block Rules
-- Blocks should include some minimum number of transactions.
+- Blocks have to include a minimum number of transactions.
 - Blocks cannot have duplicate transactions.
 
 # References
-- 
cgit v1.2.3-70-g09d2