diff --git a/curriculum/challenges/english/blocks/lecture-working-with-client-side-storage-and-crud-operations/6733ff9d2fb9c449af68ad99.md b/curriculum/challenges/english/blocks/lecture-working-with-client-side-storage-and-crud-operations/6733ff9d2fb9c449af68ad99.md
index 09fb3f66f22..c5c9debf99e 100644
--- a/curriculum/challenges/english/blocks/lecture-working-with-client-side-storage-and-crud-operations/6733ff9d2fb9c449af68ad99.md
+++ b/curriculum/challenges/english/blocks/lecture-working-with-client-side-storage-and-crud-operations/6733ff9d2fb9c449af68ad99.md
@@ -5,7 +5,7 @@ challengeType: 19
 dashedName: what-are-some-negative-patterns-associated-with-client-side-storage
 ---
 
-# --description--
+# --interactive--
 
 Client-side storage allows websites to store data on a user's device. However, like many technologies, it can be misused. 
 
@@ -31,11 +31,15 @@ This technique uses client-side information to create a unique "fingerprint" of
 
 Here's a simple example of how a website can create a fingerprint of you:
 
+:::interactive_editor
+
 ```js
 let fingerprintExample = navigator.userAgent + screen.width + screen.height;
 console.log(fingerprintExample);
 ```
 
+:::
+
 This code combines your browser's user agent with your screen dimensions. While this is a basic example, real fingerprinting methods are much more complex and can be highly accurate in identifying users.
 
 `localStorage` can also be misused as some websites use it to store sensitive information insecurely. For instance: