Update custom contracts docs

Signed-off-by: Simon Gellis <[email protected]>

Author: SupernaviX

doc-site/docs/tutorials/custom_contracts/cardano.md

@@ -16,7 +16,9 @@ Cardano dApps typically have two components: off-chain and on-chain.
 
 ## Writing a dApp
 
-First, decide on the contract which your dApp will satisfy. FireFly uses [JSON schema](https://json-schema.org/) to describe its contracts. Create a file named `contract.json`. An example is below:
+> **NOTE:** The source code to this dApp is also available [on GitHub](https://github.com/hyperledger/firefly-cardano/tree/main/wasm/simple-tx).
+
+First, decide on the contract which your dApp will satisfy. FireFly uses [FireFly Interface Format](https://hyperledger.github.io/firefly/latest/reference/firefly_interface_format/) to describe its contracts. Create a file named `contract.json`. An example is below:
 
 ### Contract
 
@@ -493,6 +495,8 @@ After connecting the WebSocket client, send a message to tell FireFly to:
 }
 ```
 
+> **NOTE:** Do not use `autoack` in production, as it can cause your application to miss events. For resilience, your app should instead respond with an "ack" message to each incoming event. For more details, see the [Websockets documentation](../../reference/types/subscription/#using-start-and-ack-explicitly).
+
 ### WebSocket event
 
 After creating the subscription, you should see an event arrive on the connected WebSocket client that looks something like this: