branch: elpa/ws-butler
commit a02607ef638d9ad89471b4bac10717e12771e661
Author: Chris Martin <[email protected]>
Commit: Chris Martin <[email protected]>
Some minor grammatical fixes
---
README.md | 17 +++++++++--------
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/README.md b/README.md
index 4b2404b261..0d5a5005ef 100644
--- a/README.md
+++ b/README.md
@@ -4,30 +4,31 @@
- Only lines touched get trimmed. If the white space at end of buffer is
changed, then blank lines at the end of buffer are truncated respecting
- `require-final-newline`
+ `require-final-newline`.
- Trimming only happens when saving.
## What does unobtrusive mean?
-The user is not made explicitly aware when trimming happens. He keep working
-and the butler takes care of white-space for you.
+The user is not made explicitly aware when trimming happens. You keep working
+and the butler takes care of whitespace for you.
This means if point is at a location that was trimmed, point is not moved, but
the data on disk has been cleaned up (revert the buffer to confirm).
-## history
+## History
-1. I started by to trim all spaces at EOL in source code in a
- "write-file-hook", when I started programming. It seemed like a great idea.
+1. I started by trimming all spaces at EOL in source code in a
+ "write-file-hook" when I started programming. It seemed like a great idea.
2. Then I got a job working on a code base where no one else trimmed spaces,
so my commits became super noisy. I wanted to stop being the "white space"
police, so switched to [ws-trim][].
* ws-trim works in a `post-command-hook` and trims white space while you
edit.
- * This was too eager for me, for example I would stop scroll away to look
- at some code and when I get back to continue, my indentation is gone.
+ * This was too eager for me. For example, I would stop and scroll away to
+ look at some code, and when I get back to continue, my indentation is
+ gone.
* It caused some problems with other customizations which also rely on
`post-command-hook`.
