branch: master
commit 89dd2ac64e403ab3fc04b4a75db445a6ae4f4a71
Author: Junpeng Qiu <qjpchm...@gmail.com>
Commit: Junpeng Qiu <qjpchm...@gmail.com>
Fix some wording in README
---
README.org | 8 +++-----
parsec.el | 8 ++++----
2 files changed, 7 insertions(+), 9 deletions(-)
diff --git a/README.org b/README.org
index a189cf1..6738fce 100644
--- a/README.org
+++ b/README.org
@@ -138,11 +138,9 @@ So we can
The =*-s= and =*-as-string= variants are the same, except the =*-s= variants
have a shorter name. Using these =*-s= functions are recommended if you're
- using these variants more frequently. These variants accept the same
- arguments. The only difference is the return value. In most cases I found
- myself using these variants instead of the original versions that return a
- list.
-
+ dealing with strings very frequently in your code. These variants accept the
+ same arguments and have the same behavior as their original counterpart that
+ returns a list. The only difference is the return value.
* Code Examples
Some very simple examples are given here. You can see many code examples in
the test files in this GitHub repo.
diff --git a/parsec.el b/parsec.el
index 2663960..70209e8 100644
--- a/parsec.el
+++ b/parsec.el
@@ -209,10 +209,10 @@
;; The `*-s' and `*-as-string' variants are the same, except the `*-s'
;; variants have a shorter name. Using these `*-s' functions are
-;; recommended if you're using these variants more frequently. These
-;; variants accept the same arguments. The only difference is the return
-;; value. In most cases I found myself using these variants instead of
-;; the original versions that return a list.
+;; recommended if you're dealing with strings very frequently in your
+;; code. These variants accept the same arguments and have the same
+;; behavior as their original counterpart that returns a list. The only
+;; difference is the return value.
;; 3 Code Examples
