From 0df256f97079e31a592be71999e0ac047bc4fdda Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Wed, 29 Nov 2023 16:10:31 -0500 Subject: [PATCH] MDX comments are {/* comment */} --- docs/smart-contracts.mdx | 2 +- docs/tutorials/smart-rollup.mdx | 8 ++++---- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/smart-contracts.mdx b/docs/smart-contracts.mdx index 07883337b..6a6a8d8ae 100644 --- a/docs/smart-contracts.mdx +++ b/docs/smart-contracts.mdx @@ -103,7 +103,7 @@ The origination of a Tezos smart contract must define: After the contract is deployed, it cannot be changed or removed from the blockchain. - +{/* TODO link to ./smart-contracts/deploying */} ### Call of a Tezos smart contract diff --git a/docs/tutorials/smart-rollup.mdx b/docs/tutorials/smart-rollup.mdx index 57635b475..0cb4c192f 100644 --- a/docs/tutorials/smart-rollup.mdx +++ b/docs/tutorials/smart-rollup.mdx @@ -35,9 +35,9 @@ Smart Rollups can run any kind of applications that they want, such as: - Applications that run complex logic on NFTs or other types of tokens - Applications that communicate with other blockchains - +*/} Rollups maintain consensus by publishing the hash of their state to Tezos, which other nodes can use to verify the rollup's behavior. The specific way that rollups publish their states and maintain consensus is beyond the scope of this tutorial. @@ -69,9 +69,9 @@ Smart Rollups are like separate horizontally scaled teams, with Tezos layer 1 as To run this tutorial, make sure that the following tools are installed: - +*/} - [Docker](https://www.docker.com/)