Commits

Didier Verna  committed 89db980

Spelling fixes in the doc.

doc/ChangeLog addition:

2011-12-18 Didier Verna <didier@xemacs.org>

* patcher.texi: Spelling fixes.

  • Participants
  • Parent commits 88dd1b9

Comments (0)

Files changed (1)

File doc/patcher.texi

 @c Author:        Didier Verna <didier@xemacs.org>
 @c Maintainer:    Didier Verna <didier@xemacs.org>
 @c Created:       Sun Apr 21 21:34:06 2002
-@c Last Revision: Sun Dec 18 17:52:28 2011
+@c Last Revision: Sun Dec 18 18:01:18 2011
 
 @c This file is part of Patcher.
 
 
 @itemize @bullet
 @item
-Permament subprojects are accessible in exactly the same way as normal
+Permanent subprojects are accessible in exactly the same way as normal
 projects, that is, via the entry point functions (@pxref{Entry Points}).
 A subproject @emph{is} a project, after all. Because of that, projects
-and permament subprojects can't share names. Patcher always looks for
+and permanent subprojects can't share names. Patcher always looks for
 subprojects first, and then regular projects.
 
 @item
 territory. More precisely, Patcher keeps track of which project(s) refer
 to specific source or ChangeLog files, and knows how to associate a
 particular ChangeLog entry with a particular project. However, Patcher
-does not support interactive selection of patches (ala Darcs or Git)
+does not support interactive selection of patches (@`a la Darcs or Git)
 yet, and if you commit one of two overlapping projects, you will most
 likely need to rediff the other one.
 @end itemize
 files are written by hand @pxref{Manual ChangeLogs}. However, in
 automatic mode, we need a way to add them to the index once the
 skeletons are filled in. This is done by another theme that you must add
-explicitely to your project, called
+explicitly to your project, called
 @code{git-index-automatic-change-logs}. This theme uses the two options
 described above to automatically add ChangeLog entries to the staging
 area.
 ChangeLogs}), Patcher can (and does) insert them into the mail buffer
 automatically. However, Patcher cannot tell when you're done filling in
 skeletons (@pxref{Automatic ChangeLogs}), so in such a case you need to
-insert the ChangeLog entries explicitely. This is done by calling the
+insert the ChangeLog entries explicitly. This is done by calling the
 function @code{patcher-mail-insert-change-logs}. It is bound to @kbd{C-c
 C-p l} in the mail buffer.
 
 
 @c Don't add stuff under this line!!
 @c patcher.texi ends here
+
+@c  LocalWords:  Patcher patcher RCS ChangeLog Darcs CVS PRCS MUA SuperProj kbd
+@c  LocalWords:  subproject subdirectory logmsg findex kindex vindex cmtcmd
+@c  LocalWords:  samp cartouche