📝 bytes and string.

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

@@ -1,4 +1,4 @@
-# uint8, uint128, uint256
+# `uint8`, `uint128`, `uint256`
 
 Unsigned integers are stored in memory based on the size of bytes they have. While sm all uint values like uint8 have 1 byte, uint256 has 32 bytes. Solidity's storage is designed in such a way that it can contain up to 32 bytes of value in one slot. In a situation where a variable doesn't contain up to 32 bytes, the value is stored and the next variable will be **packed** into the same slot, on the condition that when the bytes are added to the slot, it doesn't exceed 32 bytes.
 

book/src/4-yul-implementations/4-2-variable-storage-in-storage/4-2-2-bytes1-bytes16-bytes32.md

@@ -1,4 +1,4 @@
-# bytes1, bytes16, bytes32
+# `bytes1`, `bytes16`, `bytes32`
 
 `bytes[n]` are fixed length byte arrays, as opposed to `bytes` that are variable length byte arrays. The storage of `bytes[n]` in storage is such that it takes up a slot when it is of `bytes32` and is packed in cases of bytes below `32`. It is very similar to the `uint` type.
 

book/src/4-yul-implementations/4-2-variable-storage-in-storage/4-2-3-bytes.md

@@ -1,4 +1,4 @@
-# bytes
+# `bytes`
 
 `bytes` are dynamic byte arrays. While the length of a `bytes[n]` is known as `n`, bytes do not have a specific 
 length and can stretch up to `128` or even more.

book/src/4-yul-implementations/4-2-variable-storage-in-storage/4-2-4-string.md

@@ -1,9 +1,9 @@
-# string
+# `string`
 
-`string` are first converted into its `bytes` type by converting each individual ASCII character to its hexadecimal 
+`string` is first converted into its `bytes` type by converting each individual ASCII character to its hexadecimal 
 value. It is then stored in the exact way `bytes` are stored.
 
-Example, a `string` type, `"hello"` would be first converted into `0x68656c6c6f`, and then stored just the way 
+Example, a `string` type, `"hello"` would be first converted into `0x68656c6c6f`, a concatenation of each hexadecimal value of each character, and then stored just the way 
 `bytes` are stored.
 
 To get a knowledge of what the hexadecimal values of ASCII characters are, you can look up this table at 

book/src/4-yul-implementations/4-2-variable-storage-in-storage/4-2-5-address.md

@@ -0,0 +1 @@
+# `address`