From f349084b14107cff11efeeda1bfade858ee07005 Mon Sep 17 00:00:00 2001
From: Noah Jelich <12912633+njelich@users.noreply.github.com>
Date: Fri, 26 Jan 2024 15:02:49 +0000
Subject: [PATCH] fix lint

---
 neps/nep-0452.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/neps/nep-0452.md b/neps/nep-0452.md
index 462569f85..3fb1c6472 100644
--- a/neps/nep-0452.md
+++ b/neps/nep-0452.md
@@ -192,7 +192,7 @@ Below are some references for linkdrop contracts.
 1. Linkdrop Creation
    Linkdrop creation involves creating keypairs that, when used, have access to assets such as $NEAR, FTs, NFTs, etc. These keys should be limited access and restricted to specific functionality. For example, they should only have permission to call `claim` and `create_account_and_claim`. Since the keys allow the holder to sign transactions on behalf of the linkdrop contract, without the proper security measures, they could be used in a malicious manner (for example executing private methods or owner-only functions).
 
-Another important security implication of linkdrop creation is to ensure that only one key is mapped to a set of assets at any given time. Externally, assets such as FTs, and NFTs belong to the overall linkdrop contract account rather than a specific access key. It is important to ensure that specific keys can only claim assets that they are mapped to.
+   Another important security implication of linkdrop creation is to ensure that only one key is mapped to a set of assets at any given time. Externally, assets such as FTs, and NFTs belong to the overall linkdrop contract account rather than a specific access key. It is important to ensure that specific keys can only claim assets that they are mapped to.
 
 2. Linkdrop Key Management  
    Key management is a critical safety component of linkdrops. The linkdrop contract should implement a key management strategy for keys such that a reentrancy attack does not occur. For example, one strategy may be to "lock" or mark a key as "in transfer" such that it cannot be used again until the transfer is complete.