add info about the typings of constructor & function arguments to docs

Author: mr-zwets

website/docs/language/contracts.md

@@ -29,12 +29,17 @@ contract HTLC(pubkey sender, pubkey recipient, int expiration, bytes32 hash) {
 }
 ```
 
+:::info
+The typings for the constructor arguments are only semantic and used when initilaizing the contract with the SDK. This means when not using the SDK you could still pass a different byte length item to `bytes32 hash`.
+:::
+
+
 :::note
-Upon initialization of the contract, constructor parameters are encoded and added to the contract's bytecode in the reversed order of their declaration. This can be important when manually initializing contracts for debugging purposes.
+Upon initialization of the contract, constructor parameters are encoded and added to the contract's bytecode in the reversed order of their declaration. This can be important when manually constructing the contract locking script for debugging purposes.
 :::
 
 ## Functions
-The main construct in a CashScript contract is the function. A contract can contain one or multiple functions that can be executed to trigger transactions that spend money from the contract. At its core, the result of a function is just a yes or no answer to the question 'Can money be sent out of this contract?'. However, by using a technique called covenants, it's possible to specify additional conditions — like restricting *where* money can be sent. To read more about this technique, refer to the [CashScript Covenants Guide](/docs/guides/covenants).
+The main construct in a CashScript contract is the function. A contract can contain one or multiple functions that can be executed to trigger transactions that spend money from the contract. At its core, the result of a function is just a yes or no answer to the question 'Can money be sent out of this contract?'. However, by using 'covenants it's possible to specify additional conditions — like restricting *where* money can be sent. To learn more about covenants, refer to the [CashScript Covenants Guide](/docs/guides/covenants).
 
 #### Example
 ```solidity
@@ -51,8 +56,12 @@ contract TransferWithTimeout(pubkey sender, pubkey recipient, int timeout) {
 }
 ```
 
+:::caution
+The typings for the function arguments are only semantic, this means the length of bounded bytes types like `bytes20` are **not** contract enforced automatically. Instead add an explicit length check `require(item.length == 20)`.
+:::
+
 :::note
-Function parameters are passed in the reversed order of their declaration. This can be important when manually creating contract transactions for debugging purposes.
+Function parameters are passed in the reversed order of their declaration. This can be important when debugging or when creating transactions manually.
 :::
 
 ## Statements