From ab2711c1ee9563aace536a936eba71334159c6cf Mon Sep 17 00:00:00 2001
From: Spite <spite.moriarty@gmail.com>
Date: Fri, 22 Dec 2023 02:49:34 +0400
Subject: [PATCH] update 1 & 2 tasks descriptions

---
 descriptions/1.md | 11 ++++++++---
 descriptions/2.md |  4 ++--
 2 files changed, 10 insertions(+), 5 deletions(-)

diff --git a/descriptions/1.md b/descriptions/1.md
index 8a8a998..035845b 100644
--- a/descriptions/1.md
+++ b/descriptions/1.md
@@ -13,9 +13,14 @@ After this time (the number of seconds passed in locked_for) any user can call e
 **Contract Store:**
 - public_key: uint256
 - execution_time: uint32
-- receiver: MsgAddressInt
+- receiver: uint32
 - seqno: uint32
 
+TL-B:
+```tlb
+storage$_ public_key:uint256 execution_time:uint32 receiver:MsgAddressInt seqno:uint32 = Storage;
+```
+
 ### Function 0x9df10277
 
 The body of the message `op = 0x9df10277` must have a signature and 1 ref that will point to the cell with locked_for and new_seqno. 
@@ -35,7 +40,7 @@ The checks go strictly in the following order:
 - If execution_time < now(), you should throw error 122. Checking that execution_time has not passed yet.
 - If now + locked_for < execution_time, throw error 123. Checking that the deferral of the will is strictly greater than the value by which it has already been deferred.
 
-If all checks pass, then you need to update the execution_time field in the contract.
+If all checks pass, then you need to update the `execution_time` ans `seqno` fields in the contract.
 
 The logic is as follows:
 
@@ -47,7 +52,7 @@ If execution_time has already occurred, then any user can send a message with `o
 
 TL-B:
 ```tlb
-take_ownership#bb4be234 public_key:uint256 = ExtInMsgBody
+claim#bb4be234 = ExtInMsgBody
 ```
 
 - If execution_time has not occurred, error 124 should be thrown.
diff --git a/descriptions/2.md b/descriptions/2.md
index 3a1c7b1..203d9ea 100644
--- a/descriptions/2.md
+++ b/descriptions/2.md
@@ -2,7 +2,7 @@
 
 [File with solution](../contracts/task2.fc)
 
-Create a contract that is capable of accepting TON and tokens, and then distributing them to users according to their shires. 
+Create a contract that is capable of accepting TON and tokens, and then distributing them to users according to their shares. 
 
 The contract can accept a total of four operations:
 - 0x368ddef3 -> Add User
@@ -27,7 +27,7 @@ The contract must contain the following fields in its storage after deployment:
 - users: (HashmapE 267 uint32)
 
 You can add new fields, but these fields must always be first and in the order,
-in the order specified here. In testing, these fields will be written on defloat, so you need to take that into account.
+in the order specified here. In testing, these fields will be written on default, so you need to take that into account.
 
 ### Add User