summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJakub Wilk <jwilk@jwilk.net>2018-08-31 17:22:52 +0200
committerAndrew Gallant <jamslam@gmail.com>2018-08-31 11:59:28 -0400
commit328f4369e60bb2ecaef03c55306625659402f1a0 (patch)
treea34c141cd9c8a97cad76151c21e7d925e9bd72cd
parent04518e32e7470b78283c7ebaf6a292b54cbf93f9 (diff)
doc: fix typos
-rw-r--r--GUIDE.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/GUIDE.md b/GUIDE.md
index 313c89ad..ffcbff9f 100644
--- a/GUIDE.md
+++ b/GUIDE.md
@@ -227,7 +227,7 @@ with the following contents:
```
ripgrep treats `.ignore` files with higher precedence than `.gitignore` files
-(and treats `.rgignore` files with higher precdence than `.ignore` files).
+(and treats `.rgignore` files with higher precedence than `.ignore` files).
This means ripgrep will see the `!log/` whitelist rule first and search that
directory.
@@ -580,7 +580,7 @@ override it.
If you're confused about what configuration file ripgrep is reading arguments
from, then running ripgrep with the `--debug` flag should help clarify things.
-The debug output should note what config file is being loaded and the arugments
+The debug output should note what config file is being loaded and the arguments
that have been read from the configuration.
Finally, if you want to make absolutely sure that ripgrep *isn't* reading a