📝 Delete arrays, might add later.

book/src/4-yul-implementations/4-2-variable-storage-in-storage/4-2-11-uint8[]-uint128[]-uint256[].md

@@ -62,11 +62,8 @@ more than enough to fit into the next slot, then, we can load the next storage l
 
 ## General `<type>[]` Deduction.
 
-Once the concept of type storages is understood, you can use that to figure out how the array versions of that type 
-will be stored.
+Once the concept of type storages is understood, you can use that to figure out how the array versions of that type will be stored.
 
-You can use the knowledge of arrays to write to any array index, or read from an array index.
+To retrieve an element from a packed array is quite tricky and is not readily advised.
 
-To retrieve an element from a packed array is quite trick and is not readily advised.
-
-> 🚨 The use of Yul to read and write arrays is not advised. It is a very tricky business.
+> 🚨 The use of Yul to read and write arrays is not advised. It is a very tricky business, considering the fact that small types are packed and large types occupy one slot, it is a whole new level of stress to take in packing, and other considerations while storing values into an array from Yul. Allow Solidity to handle the intricacies for you.

book/src/4-yul-implementations/4-2-variable-storage-in-storage/4-2-2-int8-int128-int256.md

@@ -38,4 +38,6 @@ contract Yul {
 }
 ```
 
-> 🚨 Due to the tricky nature of the storage of `int[n]` types, apply more care when storing and manipulating values from storage.
+> 🚨 Due to the tricky nature of the storage of `int[n]` types, apply more care when storing and manipulating values from storage.
+
+> 🚨 Do not store negative `int[n]` values directly from your Yul block of code, Yul treats it as a `uint[n]` type overflow, meaning that `-1` will be converted to `(2^256) - 1`. This can lead to security breaches.