From 7a823a9299375dea5d6e9e53de9a3b9161ab046c Mon Sep 17 00:00:00 2001 From: ymekuria Date: Fri, 12 Jul 2024 10:59:04 -0700 Subject: [PATCH] docs(custom-tokens.mdx): remove unnecessary empty line for better readability and consistency --- docs/zkapps/writing-a-zkapp/feature-overview/custom-tokens.mdx | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/zkapps/writing-a-zkapp/feature-overview/custom-tokens.mdx b/docs/zkapps/writing-a-zkapp/feature-overview/custom-tokens.mdx index 3a0a1a620..eee17f0e2 100644 --- a/docs/zkapps/writing-a-zkapp/feature-overview/custom-tokens.mdx +++ b/docs/zkapps/writing-a-zkapp/feature-overview/custom-tokens.mdx @@ -55,7 +55,6 @@ A token manager smart contract sets the rules around minting, burning, and sendi Use the `TokenContract` class to perform common token operations, such as minting, burning, and sending tokens. In o1js, the `TokenContract` class is your blueprint for custom token implementations. - As shown in this [example code](https://github.com/o1-labs/o1js/blob/main/src/lib/mina/token/token-contract.unit-test.ts#L13), you inherit from the `TokenContract` class: ```ts