diff --git a/notes/toobigdatadoc-dev-log.md b/notes/toobigdatadoc-dev-log.md
index d81212c..fb8516d 100644
--- a/notes/toobigdatadoc-dev-log.md
+++ b/notes/toobigdatadoc-dev-log.md
@@ -5,7 +5,7 @@
     * NO: parallel directory path to file form `tooroot`
 
 ## TODO
-TODO: unit test package
+TODO: unit test package. make a trash directory, test `too -h`, `too 42 -h poo`, `too big`. destroy.
 
 ## IOYCSWISWYE
 * This is working 100% now
@@ -29,7 +29,7 @@ TODO: unit test package
     - [BLUSH-RESPONSE: too topdir](#blush-response-too-topdir)
     - [VOIGHT-KAMPFF: PASS regular folder](#voight-kampff-pass-regular-folder)
     - [VOIGHT-KAMPFF: PASS git repo folders](#voight-kampff-pass-git-repo-folders)
-    - [CHEW](#chew)
+    - [EMPATHY](#empathy)
 
 ## INCEP-DATE
 ```bash
@@ -133,8 +133,9 @@ Here in bash:
 # toodoc
 mkdir $HOME/toodoc/iterm-colors
 ln -s ../../../toodoc/iterm-colors doc
+```
 
-```py
+```python
 import git
 
 # is it a git repo?
@@ -317,7 +318,7 @@ done | sort
 
 
 ----------
-## CHEW
+## EMPATHY
 [1]: https://github.com/santiagobasulto/hyper-inspector
 
 [python docs: packaging](https://packaging.python.org/en/latest/tutorials/packaging-projects/)
diff --git a/notes/toobigdatadoc-packaging-log.md b/notes/toobigdatadoc-packaging-log.md
index 6ee1b68..695ab59 100644
--- a/notes/toobigdatadoc-packaging-log.md
+++ b/notes/toobigdatadoc-packaging-log.md
@@ -1,4 +1,4 @@
-## desertislandutils.toobigdatadoc package executable
+# desertislandutils.toobigdatadoc package executable
 OK poetry now is time to shine.
 
 >I am developing python packages with poetry in isolated environment, and distributing executables to my home machine. These are utility programs I use all the time, currently bash.  *There is no need to import these modules into other packages.
@@ -11,6 +11,21 @@ OK poetry now is time to shine.
 4. merge to main, initiate CI/CD build on github actions
 5. homebrew to install || script to download to ~/bin
 
+- [desertislandutils.toobigdatadoc package executable](#desertislandutilstoobigdatadoc-package-executable)
+    - [IOYCSWISWYE: TOPLINES](#ioycswiswye-toplines)
+    - [INCEP-DATE: reconsidering shebang](#incep-date-reconsidering-shebang)
+    - [INCEP-DATE](#incep-date)
+        - [**CHEW: how to install executable from a .whl binary?**](#chew-how-to-install-executable-from-a-whl-binary)
+        - [pipx install wheel to global namespace](#pipx-install-wheel-to-global-namespace)
+    - [OFF-WORLD: pipx](#off-world-pipx)
+    - [OFF-WORLD: pyinstall](#off-world-pyinstall)
+    - [OFF-WORLD: **nuitka**](#off-world-nuitka)
+    - [EMPATHY](#empathy)
+
+## IOYCSWISWYE: TOPLINES
+* no need for `nuitka` binary executables right now, poetry -> homebrew good
+* ready to continue migrating the rest of my bash scripts
+
 ## INCEP-DATE: reconsidering shebang
 * like bash scripts, python single file scripts run on a local interpreter
 * but python applications are built within an isolated environment, therefore:
@@ -32,7 +47,7 @@ l dist/
 -rw-r--r-- 1 2.8K Mar 11 20:08 desertislandutils-0.1.0-py3-none-any.whl
 
 ```
-### **Q: how to install executable from a whl binary?**
+### **CHEW: how to install executable from a .whl binary?**
 A: with pip
 
 NOTE: pyproject needs following to get right module name: