summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMartin Michlmayr <tbm@cyrius.com>2018-04-14 09:25:24 +0200
committerMartin Michlmayr <tbm@cyrius.com>2018-04-14 09:25:24 +0200
commit2e54b3e9e9faac1e0a7b3a10596a2ed8dc663bb1 (patch)
tree2503d1571c752b7e12a45d0e958c0c019bbf320a
parent56508f0f96e7ed614ed47a9da1cb584fcb9ed31f (diff)
Fix typo
-rw-r--r--emacstips.mdwn2
-rw-r--r--howto.mdwn2
-rw-r--r--remoteusage/124.mdwn2
3 files changed, 3 insertions, 3 deletions
diff --git a/emacstips.mdwn b/emacstips.mdwn
index 4999cdb..083746e 100644
--- a/emacstips.mdwn
+++ b/emacstips.mdwn
@@ -372,7 +372,7 @@ available:
cc -o addrlookup addrlookup.c `pkg-config --cflags --libs gobject-2.0` -lnotmuch
* Shell/fgrep/perl combination [nottoomuch-addresses.sh](https://github.com/domo141/nottoomuch/blob/master/nottoomuch-addresses.rst).
- This tools maintains it's own address "database" gathered from email
+ This tools maintains its own address "database" gathered from email
files notmuch knows and search from that "database" is done by `fgrep(1)`.
* python/sqlite combination [notmuch-abook](https://github.com/guyzmo/notmuch-abook/)
diff --git a/howto.mdwn b/howto.mdwn
index 9d029d8..a37149d 100644
--- a/howto.mdwn
+++ b/howto.mdwn
@@ -12,7 +12,7 @@ Notmuch does not fetch mail for you. For that, you need to use an
external mail syncing utility. Some recommended utilities are listed
below.
-Notmuch requires that every individual message be in it's own file.
+Notmuch requires that every individual message be in its own file.
The well-supported [maildir](http://cr.yp.to/proto/maildir.html) or
"mh"-style storage formats are compatible with notmuch. Basically any
setup in which each mail is in a file of its own will work. The older
diff --git a/remoteusage/124.mdwn b/remoteusage/124.mdwn
index d7da3f7..9a4fd45 100644
--- a/remoteusage/124.mdwn
+++ b/remoteusage/124.mdwn
@@ -70,7 +70,7 @@ Write the following code to a file, for example `remote-notmuch.sh`.
Note the `0.1` in ssh command line. It is used to avoid any opportunistic
behaviour ssh might do; for example if control socket is not alive ssh
-would attempt to do it's own ssh connection to remote ssh server. As
+would attempt to do its own ssh connection to remote ssh server. As
address `0.1` is invalid this attempt will fail early.
## Test