From f5d59c2e2108d46efb8fff4a084f423004066137 Mon Sep 17 00:00:00 2001
From: Major Studio <118572301+aegis72@users.noreply.github.com>
Date: Tue, 9 Jan 2024 17:21:44 -0600
Subject: [PATCH] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index aba44c0..31490b6 100644
--- a/README.md
+++ b/README.md
@@ -5,7 +5,7 @@ These nodes were created to solve challenges in developing AegisFlow Shima, a mo
 The Utility nodes have a variety of "Passer" nodes that can both passs through items targeted by Use Everywhere nodes, as well as secure an input that requires one. This is necessary because Comfy will try to "fix" those inputs using any output that matches, even if that doesn't work, breaking the wf (this is an "all workflows problem, not an AegisFlow problem.
 The key thing is that the INPUTS of these passers are optional, and as such they don't trigger whatever "autofixing" seems to go on behind the scenes. They are a bit of a namable target AND a plug for the end of a cell's receptors, preventing the WF disease of "let's just wire this to that for giggles."
 
-Most commonly used is an "image" passer, but you can do others like latents,masks, CLIP etc. There is also a "Placeholder Tuple" for times when you need to fill a Tuple but aren't going to actually use it. This is helpful in developing template workflows that are frequently broken when inputs are left unoccupied (ask me how I know?)
+Most commonly used is an "image" passer, but you can do others like latents, masks, CLIP etc. There is also a "Placeholder Tuple" for times when you need to fill a Tuple but aren't going to actually use it. This is helpful in developing template workflows that are frequently broken when inputs are left unoccupied (ask me how I know?). If you need a passer included, suggest it and I'll work on making one.
 
 ![image](https://github.com/aegis72/aegisflow_utility_nodes/assets/118572301/f1157839-d454-4622-b5cd-b39a26678fec)