summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorVan L <van@scratch.space>2019-01-03 20:42:47 -0500
committerKyle Meyer <kyle@kyleam.com>2019-01-03 20:43:01 -0500
commit98407c111d4da7895faae6afd7f63784edf975cd (patch)
tree79c35d0d270cbd6bdb55259f8357805dba026ba1
parent284799a2e86be0d95abe3e5404a48e2c4f1fc8fc (diff)
downloadorg-mode-98407c111d4da7895faae6afd7f63784edf975cd.tar.gz
Fix two docstring typos
* lisp/org.el (org-read-date-force-compatible-dates): Fix docstring typos. TINYCHANGE
-rw-r--r--lisp/org.el4
1 files changed, 2 insertions, 2 deletions
diff --git a/lisp/org.el b/lisp/org.el
index 8e1486e..e54bc30 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -3329,7 +3329,7 @@ Depending on the system Emacs is running on, certain dates cannot
be represented with the type used internally to represent time.
Dates between 1970-1-1 and 2038-1-1 can always be represented
correctly. Some systems allow for earlier dates, some for later,
-some for both. One way to find out it to insert any date into an
+some for both. One way to find out is to insert any date into an
Org buffer, putting the cursor on the year and hitting S-up and
S-down to test the range.
@@ -3337,7 +3337,7 @@ When this variable is set to t, the date/time prompt will not let
you specify dates outside the 1970-2037 range, so it is certain that
these dates will work in whatever version of Emacs you are
running, and also that you can move a file from one Emacs implementation
-to another. WHenever Org is forcing the year for you, it will display
+to another. Whenever Org is forcing the year for you, it will display
a message and beep.
When this variable is nil, Org will check if the date is