summaryrefslogtreecommitdiffstats
path: root/FAQ.md
diff options
context:
space:
mode:
authorYevgen Antymyrov <turist@gmail.com>2019-09-25 14:13:27 +0200
committerAndrew Gallant <jamslam@gmail.com>2019-09-25 08:13:27 -0400
commit8892bf648cfec111e6e7ddd9f30e932b0371db68 (patch)
treeac3e7f8d98aa360c6764659050578b00c6d41245 /FAQ.md
parent8cb7271b647f63420530ac04bc13ed8ea7353690 (diff)
doc: fix typo in FAQ
Diffstat (limited to 'FAQ.md')
-rw-r--r--FAQ.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/FAQ.md b/FAQ.md
index 061fdf82..cf70a18c 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -934,7 +934,7 @@ Here are some cases where you might *not* want to use ripgrep. The same caveats
for the previous section apply.
* Are you writing portable shell scripts intended to work in a variety of
- environments? Great, probably not a good idea to use ripgrep! ripgrep is has
+ environments? Great, probably not a good idea to use ripgrep! ripgrep has
nowhere near the ubiquity of grep, so if you do use ripgrep, you might need
to futz with the installation process more than you would with grep.
* Do you care about POSIX compatibility? If so, then you can't use ripgrep