fix: typos

docs/devdocs/Tutorials/Basic/Writing-The-Contract.md

@@ -199,7 +199,7 @@ contract WrappingERC20 is ERC20 {
         // Make sure the sender has enough tokens.
         FHE.req(amount.lte(_encBalances[msg.sender]));
 
-        // Add to the balance of `to` and subract from the balance of `from`.
+        // Add to the balance of `to` and subtract from the balance of `from`.
         _encBalances[to] = _encBalances[to] + amount;
         _encBalances[msg.sender] = _encBalances[msg.sender] - amount;
     }

docs/devdocs/Writing Smart Contracts/Security-Zones.md

@@ -60,7 +60,7 @@ let second = await client.encrypt_uint32(1332, 0); // This implicitly uses Secur
 await contract.addSecZone0(first, second);
 
 first = await client.encrypt_uint32(5, 1); // To use a non-default SZ, you have to be explicit
-econd = await client.encrypt_uint32(1332, 1);
+second = await client.encrypt_uint32(1332, 1);
 await contract.addSecZone1(first, second);
 ```
 
@@ -72,4 +72,4 @@ In **fhenix.js**, you can specify a Security Zone only in the `encrypt()` functi
 
 :::info[Note]
 The current security zones are implemented to demonstrate the concept with tradeoffs between security and performance. However, they are not indicative of a production deployment.
-:::
+:::