News for release 0.38.3

[notmuch-wiki] / news / release-0.19.mdwn

diff --git a/news/release-0.19.mdwn b/news/release-0.19.mdwn
index fe9b462fe775340aa6ce2a12063eda2b938036b1..436763cfca3b2e8e5b5a399fc07a3dc471d62a7c 100644 (file)
--- a/news/release-0.19.mdwn
+++ b/news/release-0.19.mdwn
@@ -25,13 +25,13 @@ dump which would cause the dump to fail. Note, if another notmuch
 process already has the write lock the dump will not start, so
 script callers should still check the return value.
 
-### `notmuch insert` requires succesful message indexing for success status
+### `notmuch insert` requires successful message indexing for success status
 
 Previously the `notmuch insert` subcommand indicated success even if
 the message indexing failed, as long as the message was delivered to
 file system. This could have lead to delivered messages missing
 tags, etc. `notmuch insert` is now more strict, also requiring
-succesful indexing for success status. Use the new `--keep` option
+successful indexing for success status. Use the new `--keep` option
 to revert to the old behaviour (keeping the delivered message file
 and returning success even if indexing fails).
 
@@ -143,7 +143,7 @@ nmbug
 
 The Perl script has been translated to Python; you'll need Python 2.7
 or anything from the 3.x line.  Most of the user-facing interface is
-the same, but `nmbug help` is not `nmbug --help`, and the following nmbug
+the same, but `nmbug help` is now `nmbug --help`, and the following nmbug
 commands have slightly different interfaces: `archive`, `commit`,
 `fetch`, `log`, `pull`, `push`, and `status`.  For details on the
 new interface for a given command, run `nmbug COMMAND --help`.
@@ -161,7 +161,7 @@ from the config file.  Use something like:
          ...
       },
       ...
-    },
+    }
 
 Python Bindings
 ---------------