From b19cf6dd0680c5ef8c91d809131420cf0fbc033f Mon Sep 17 00:00:00 2001
From: Nathaniel Sabanski <sabanski.n@gmail.com>
Date: Tue, 14 Nov 2023 09:17:31 -0800
Subject: [PATCH] Update README.md

---
 README.md | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index b1b8536..d983bfb 100644
--- a/README.md
+++ b/README.md
@@ -317,10 +317,12 @@ Append / Prepend elements.
 
 ## 🔎 Technical FAQ
 * Can I locally scope functions to `<script>` ?
-  * The recommended way to scope a function is to place it in an event, ex: `me().on('click', ev => { ... })`
-  * The 2nd recommended way is to avoid scoping functions and keep a `common.js` file for global functions.
-  * The 3rd way is using `<script type="module">` but `me()` will no longer see `parentElement` so, an explicit selector is required, ex: `me(".mybutton")`
-    * This is a tradeoff solution, but may be most appropriate in some circumstances.
+  * Recommended: Scope inside an event.
+    * `me().on('click', ev => { /* add and call function here */ })`
+  * Alternative: Use `<script type="module">`
+    * Tradeoff: `me()` will no longer see `parentElement` so, an explicit selector is required: `me(".mybutton")`
+  * Alternative: Keep a `common.js` file for global functions.
+  * Alternative: Uniquely name your function.
 
 ## <a name="plugins"></a>🔌 Adding a function