Fix documentation typos

doc/org.texi

@@ -3708,7 +3708,7 @@ after the minimum of 2 days has elapsed, and will appear overdue on Oct 19,
 after four days have elapsed.
 
 What's really useful about habits is that they are displayed along with a
-conistency graph, to show how consistent you've been at getting that task
+consistency graph, to show how consistent you've been at getting that task
 done in the past.  This graph shows every day that the task was done over the
 past three weeks, with colors for each day.  The colors used are:
 
@@ -3733,7 +3733,7 @@ habits are displayed in the agenda.
 @table @code
 @item org-habit-graph-column
 The buffer column at which the consistency graph should be drawn.  This will
-overwite any text in that column, so it's a good idea to keep your habits'
+overwrite any text in that column, so it's a good idea to keep your habits'
 titles brief and to the point.
 @item org-habit-preceding-days
 The amount of history, in days before today, to appear in consistency graphs.
@@ -3840,7 +3840,7 @@ this issue.
 
 @vindex org-hierarchical-todo-statistics
 If you would like to have the statistics cookie count any TODO entries in the
-subtree (not just direct children), confgure the variable
+subtree (not just direct children), configure the variable
 @code{org-hierarchical-todo-statistics}.  To do this for a single subtree,
 include the word @samp{recursive} into the value of the @code{COOKIE_DATA}
 property.
@@ -4612,8 +4612,8 @@ optional.  The individual parts have the following meaning:
 @end example
 
 @noindent
-Be aware that you can only have use one summary type for any property you
-include. Subsequent columns referencing the same property will al display the
+Be aware that you can only have one summary type for any property you
+include. Subsequent columns referencing the same property will all display the
 same summary information.
 
 Here is an example for a complete columns definition, along with allowed
@@ -4653,7 +4653,7 @@ in the subtree.
 @vindex org-columns-default-format
 Turn on column view.  If the cursor is before the first headline in the file,
 column view is turned on for the entire file, using the @code{#+COLUMNS}
-definition.  If the cusor is somewhere inside the outline, this command
+definition.  If the cursor is somewhere inside the outline, this command
 searches the hierarchy, up from point, for a @code{:COLUMNS:} property that
 defines a format.  When one is found, the column view table is established
 for the tree starting at the entry that contains the @code{:COLUMNS:}
@@ -5229,7 +5229,7 @@ Insert @samp{DEADLINE} keyword along with a stamp.  The insertion will happen
 in the line directly following the headline.  When called with a prefix arg,
 an existing deadline will be removed from the entry.  Depending on the
 variable @code{org-log-redeadline}@footnote{with corresponding
-@code{#+STARTUP} keyqwords @code{logredeadline}, @code{lognoteredeadline},
+@code{#+STARTUP} keywords @code{logredeadline}, @code{lognoteredeadline},
 and @code{nologredeadline}}, a note will be taken when changing an existing
 deadline.
 @c FIXME Any CLOSED timestamp will be removed.????????
@@ -10350,7 +10350,7 @@ This may be necessary in particular if files include other files via
 
 Emacs would not be Emacs without completion, and Org-mode uses it whenever it
 makes sense.  If you prefer an @i{iswitchb}- or @i{ido}-like interface for
-some of the completion prompts, you can specify your preferece by setting at
+some of the completion prompts, you can specify your preference by setting at
 most one of the variables @code{org-completion-use-iswitchb}
 @code{org-completion-use-ido}.
 
@@ -12126,7 +12126,7 @@ the view, only the current agenda files will be searched.
 
 @node History and Acknowledgments, Main Index, MobileOrg, Top
 @appendix History and Acknowledgments
-@cindex acknowledgments
+@cindex acknowledgements
 @cindex history
 @cindex thanks
 
@@ -12381,7 +12381,7 @@ and contributed various ideas and code snippets.
 
 This is not a complete index of variables and faces, only the ones that are
 mentioned in the manual.  For a more complete list, use @kbd{M-x
-org-customize @key{RET}} and then klick yourself through the tree.
+org-customize @key{RET}} and then click yourself through the tree.
 
 @printindex vr
 

doc/orgcard.tex

@@ -575,7 +575,7 @@ after  ``{\tt :}'', and dictionary words elsewhere.
 %\key{... scroll calendar back/forward one month}{< / >}
 %\key{... forward/backward one day}{S-LEFT/RIGHT}
 %\key{... forward/backward one week}{S-UP/DOWN}
-%\key{... forward/backward one month}{M-S-LEFT/RIGT}
+%\key{... forward/backward one month}{M-S-LEFT/RIGHT}
 \key{toggle custom format display for dates/times}{C-c C-x C-t}
 
 \newcolumn
@@ -622,14 +622,14 @@ after  ``{\tt :}'', and dictionary words elsewhere.
 {\bf Change display}
 
 \key{delete other windows}{o}
-\key{view mode dipatcher}{v}
+\key{view mode dispatcher}{v}
 \key{switch to day/week/month/year view}{d w vm vy}
 \key{toggle diary entries / time grid / habits}{D / G / K}
 \key{toggle entry text / clock report}{E / R}
 \key{toggle display of logbook entries}{l / v l/L}
 \key{toggle inclusion of archived trees/files}{v a/A}
 \key{refresh agenda buffer with any changes}{r / g}
-\key{filter with repect to a tag}{/}
+\key{filter with respect to a tag}{/}
 \key{save all org-mode buffers}{s}
 \key{display next/previous day,week,...}{f / b}
 \key{goto today / some date (prompt)}{. / j}

doc/orgcard.txt

@@ -362,7 +362,7 @@ toggle time grid for daily schedule               G
 toggle display of logbook entries                 l
 toggle inclusion of archived trees/files          v / C-u v}
 refresh agenda buffer with any changes            r / g
-filter agenda with repect to a tag                /
+filter agenda with respect to a tag               /
 save all org-mode buffers                         s
 display the next/previous day, week,...           RIGHT/LEFT
 goto today                                        .