commit - aedcc736985355c4444e7374d135a81df843b622
commit + 235b16c14be3954ce3dabe19c975a1e8d0ad84fa
blob - a52398fbb22a5b2b9ba65e41897e2113cc9bb404
blob + 26a2e970b121ed732f8e1ded02308de84bc2a969
--- README.md
+++ README.md
@@ -1,6 +1,6 @@
 # bxhkd
 
-A very basix X hotkey daemon, a.k.a Brett's X hotkey daemon.
+A very basix X hotkey daemon.
 
 ## Doing One Thing and Doing It Well
 
@@ -9,15 +9,15 @@ in their codebases from bundling extraneous features i
 binary. Just my opinion.
 
 I chose a different path. __bxhkd__ is an independent, modular  
-companion to my primary window manager, __bxwm__. By offloading key  
+companion to my window manager, __bxwm__. By offloading key  
 handling management, I ensure that both the window manager and the  
-hotkey daemon remain focused, llightweight, and easily maintainable.
+hotkey daemon remain focused, lightweight, and easily maintainable.
 
 __bxhkd__ isn't just about managing keys. This hotkey daemon  
 is another project I am using for transitioning from writing shell  
 scripts for automating workflow to writing robust C that prioritizes  
-minimal runtime overhead, adherence to the Unix philosophy, and clean, 
- readable API design.
+minimal runtime overhead, adherence to the Unix philosophy, and  
+clean, readable API design.
 
 ## Build
 
@@ -46,9 +46,9 @@ make uninstall
 
 ## Configuration
 
-__bxhkd__ is configured at compile-time by editing config.def.h. After  
-making changes, the program must be recompiled and reinstalled. See  
-bxhkd(1) for details.
+__bxhkd__ is configured in config.def.h. User customizations should be  
+made in config.h after the initial compile. After making changes, the  
+program must be recompiled and reinstalled. See bxhkd(1) for details.
 
 ## Design & Functionality