From f4b2a8226987135a400add13081a196cfef79474 Mon Sep 17 00:00:00 2001
From: sargesmith <58910754+shittuisrael004@users.noreply.github.com>
Date: Tue, 30 Dec 2025 23:25:59 +0100
Subject: [PATCH] Update non-fungible-tokens.md

changed SIP-010 to the correct SIP-009
---
 docs/build/get-started/create-a-token/non-fungible-tokens.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/build/get-started/create-a-token/non-fungible-tokens.md b/docs/build/get-started/create-a-token/non-fungible-tokens.md
index 306b4535e9..a26fc27d1f 100644
--- a/docs/build/get-started/create-a-token/non-fungible-tokens.md
+++ b/docs/build/get-started/create-a-token/non-fungible-tokens.md
@@ -140,7 +140,7 @@ This is the Clarity code we need in order to create an NFT, with one additional
 The token contract example above is passing in an already deployed trait on mainnet into the `impl-trait` function. You can use this same deployed trait for your own NFT contract as well.
 
 {% hint style="success" %}
-Deployed SIP-010 trait contracts you can directly implement in your custom token contract:
+Deployed SIP-009 trait contracts you can directly implement in your custom token contract:
 
 * \[mainnet] SP2PABAF9FTAJYNFZH93XENAJ8FVY99RRM50D2JG9.nft-trait
 * \[testnet] ST1NXBK3K5YYMD6FD41MVNP3JS1GABZ8TRVX023PT.nft-trait