summaryrefslogtreecommitdiff
path: root/README.org
diff options
context:
space:
mode:
authorDaniel Mendler <mail@daniel-mendler.de>2022-01-12 02:17:32 +0100
committerGitHub <noreply@github.com>2022-01-12 02:17:32 +0100
commitacc33a38dd43e4466317945f867123731d142bf7 (patch)
treed14496e2a8de1a8d1de8f23717cd8f932d4619fa /README.org
parentcf31199bed3f3b542cb4bc5ca52e372b5e3ac6e3 (diff)
parent8ab924edc5b8f697ea3dd139cdfdf33438a3482a (diff)
Merge pull request #21 from vifon/patch-1
Fix a typo in README.org
Diffstat (limited to 'README.org')
-rw-r--r--README.org2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.org b/README.org
index 55f7330..d2964fd 100644
--- a/README.org
+++ b/README.org
@@ -28,7 +28,7 @@ trigger the respective completion at point. You can bind them directly to a key
in your user configuration. Notable commands/capfs are ~cape-line~ for completion
of a line from the current buffer and ~cape-file~ for completion of a file name.
The command ~cape-symbol~ is particularily useful for documentation of Elisp
-packages or configurations, since it completes elisp symbols anywere.
+packages or configurations, since it completes elisp symbols anywhere.
On the more experimental side, Cape has the super power to transform Company
backends into Capfs and merge multiple Capfs into a Super-Capf! These