branch: master
commit ec20ba01a18a812ae78e3c91ac73736fda6a99c3
Author: Don March <[email protected]>
Commit: GitHub <[email protected]>
Update README.md: fix small typos
---
README.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/README.md b/README.md
index 563db03..c250d4e 100644
--- a/README.md
+++ b/README.md
@@ -5,7 +5,7 @@
The rational behind module is to be able to write small Emacs
functions or modules in a larger multi-file Emacs package and
facilitate running from the source tree without having to "install"
-the code or fiddle with evil *load-path*'s . See my [NYC Lisp
talk](https://github.com/rocky/emacs-load-relative/wiki/NYC-Lisp-talk) for more
background on this.
+the code or fiddle with evil *load-path*'s. See my [NYC Lisp
talk](https://github.com/rocky/emacs-load-relative/wiki/NYC-Lisp-talk) for more
background on this.
## Contents ##
@@ -84,7 +84,7 @@ extension) as the name of the thing you want to provide.
Using this
forces the *provide* names to be the same as the filename, but I
consider that a good thing.
-*provide-me* also takes an optional string which will be prepended to the
provide name. This is useful if you have a multi-file package and want the
files to bue prefaced with the name of the package.
+*provide-me* also takes an optional string which will be prepended to the
provide name. This is useful if you have a multi-file package and want the
files to be prefaced with the name of the package.
Assume your package *foo* and contains simply file `foo.el`. Then
adding:
