summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--doc/misc/ChangeLog4
-rw-r--r--doc/misc/org.texi6
2 files changed, 7 insertions, 3 deletions
diff --git a/doc/misc/ChangeLog b/doc/misc/ChangeLog
index 3218a788be7..d51ab55db43 100644
--- a/doc/misc/ChangeLog
+++ b/doc/misc/ChangeLog
@@ -1,3 +1,7 @@
+2009-01-13 Peter Tury <tury.peter@gmail.com> (tiny change)
+
+ * org.texi: Fix some typos.
+
2009-01-09 Katsumi Yamaoka <yamaoka@jpl.org>
* gnus.texi (Group Parameters): Add note for local variables.
diff --git a/doc/misc/org.texi b/doc/misc/org.texi
index 3bc6741ff3b..8c5731878e7 100644
--- a/doc/misc/org.texi
+++ b/doc/misc/org.texi
@@ -3506,7 +3506,7 @@ the variables @code{org-use-tag-inheritance} and
When a headline matches during a tags search while tag inheritance is turned
on, all the sublevels in the same tree will (for a simple match form) match
-as well@footnote{This is only true if the the search does not involve more
+as well@footnote{This is only true if the search does not involve more
complex tests including properties (@pxref{Property searches}).}. The list
of matches may then become very long. If you only want to see the first tags
match in a subtree, configure the variable
@@ -4463,7 +4463,7 @@ the given day/month is @i{before} today, it will assume that you mean a
future date@footnote{See the variable
@code{org-read-date-prefer-future}.}.
-For example, lets assume that today is @b{June 13, 2006}. Here is how
+For example, let's assume that today is @b{June 13, 2006}. Here is how
various inputs will be interpreted, the items filled in by Org mode are
in @b{bold}.
@@ -4472,7 +4472,7 @@ in @b{bold}.
14 --> @b{2006}-@b{06}-14
12 --> @b{2006}-@b{07}-12
Fri --> nearest Friday (defaultdate or later)
-sep 15 --> @b{2006}-11-15
+sep 15 --> @b{2006}-09-15
feb 15 --> @b{2007}-02-15
sep 12 9 --> 2009-09-12
12:45 --> @b{2006}-@b{06}-@b{13} 12:45