X-Git-Url: https://git.notmuchmail.org/git?p=notmuch;a=blobdiff_plain;f=lib%2Fnotmuch.h;h=d3e50a79536c37283e3cd42fc74b5e7c79ad1d88;hp=15c9db40657d444006a2ec49e76c86503f528d06;hb=7a9bacac6786729d7f28495b0ef30f9b6ded7696;hpb=c340c1bd1140c0a1b7e0f24ef3ebac806f5fc3e6

diff --git a/lib/notmuch.h b/lib/notmuch.h
index 15c9db40..d3e50a79 100644
--- a/lib/notmuch.h
+++ b/lib/notmuch.h
@@ -864,7 +864,7 @@ notmuch_message_remove_all_tags (notmuch_message_t *message);
  * notmuch_message_remove_all_tags), will not be committed to the
  * database until the message is thawed with notmuch_message_thaw.
  *
- * Multiple calls to freeze/thaw are valid and these calls with
+ * Multiple calls to freeze/thaw are valid and these calls will
  * "stack". That is there must be as many calls to thaw as to freeze
  * before a message is actually thawed.
  *
@@ -882,7 +882,7 @@ notmuch_message_remove_all_tags (notmuch_message_t *message);
  *    notmuch_message_thaw (message);
  *
  * With freeze/thaw used like this, the message in the database is
- * guaranteed to have either the full set of original tag value, or
+ * guaranteed to have either the full set of original tag values, or
  * the full set of new tag values, but nothing in between.
  *
  * Imagine the example above without freeze/thaw and the operation