From 7a73eb333c24d9c58073c0091dd127949740af00 Mon Sep 17 00:00:00 2001
From: AJ ONeal <aj@therootcompany.com>
Date: Thu, 9 Jul 2020 11:54:13 +0000
Subject: [PATCH] update docs

---
 webi/README.md | 24 ++++++++++++++++--------
 1 file changed, 16 insertions(+), 8 deletions(-)

diff --git a/webi/README.md b/webi/README.md
index 0cde5be..5680034 100644
--- a/webi/README.md
+++ b/webi/README.md
@@ -17,7 +17,7 @@ Since `webi` is just a small helper script, it's always update on each use.
 
 > `webi` is what you would have created if you automated how you install your
 > common tools yourself: Simple, direct downloads from official sources,
-> unpacked into `$HOME/.local`, added to `PATH`, symlinked for easy version
+> unpacked into `~/.local`, added to `PATH`, symlinked for easy version
 > switching, with minimal niceties like resuming downloads and 'stable' tags.
 
 - Easy to remember.
@@ -34,25 +34,33 @@ Or via `webi`, the tiny `curl | bash` shortcut command that comes with each
 install:
 
 ```bash
-webi node@latest
+webi node@lts golang@stable flutter@beta rustlang
 ```
 
+### webi PATHs
+
+You can see exactly what PATHs have been edited:
+
 ```bash
-webi golang@v1.14
+pathman list
 ```
 
+And where:
+
 ```bash
-webi rustlang
+cat ~/.config/envman/PATH.env
 ```
 
-You can see exactly what PATHs have been edited:
+### Uninstall `webi`
+
+`webi` uses standard paths and touches very little.
 
 ```bash
-pathman list
+rm -rf ~/.local/opt ~/.local/bin
 ```
 
-And where:
+If you haven't used `pathman` for anything else, you can also remove its config:
 
 ```bash
-cat $HOME/.config/envman/PATH.env
+rm -f ~/.config/envman/PATH.env
 ```
-- 
2.25.1