summaryrefslogtreecommitdiff
path: root/src/editfns.c
diff options
context:
space:
mode:
authorJuanma Barranquero <lekktu@gmail.com>2011-02-23 20:56:30 +0100
committerJuanma Barranquero <lekktu@gmail.com>2011-02-23 20:56:30 +0100
commit8307f92370e7d86aea2c78d0dbc06c5ace9c6f11 (patch)
tree0f4b65eac80f244ac7610b5317e2163d668f22cb /src/editfns.c
parentf1cffc3d52a56eef7ee17392f912f3201a52b5d6 (diff)
downloademacs-8307f92370e7d86aea2c78d0dbc06c5ace9c6f11.tar.gz
emacs-8307f92370e7d86aea2c78d0dbc06c5ace9c6f11.tar.bz2
emacs-8307f92370e7d86aea2c78d0dbc06c5ace9c6f11.zip
Fix typos.
Diffstat (limited to 'src/editfns.c')
-rw-r--r--src/editfns.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/editfns.c b/src/editfns.c
index fe5b039625f..a751d6df3b2 100644
--- a/src/editfns.c
+++ b/src/editfns.c
@@ -3623,12 +3623,12 @@ usage: (format STRING &rest OBJECTS) */)
int multibyte = 0;
/* When we make a multibyte string, we must pay attention to the
byte combining problem, i.e., a byte may be combined with a
- multibyte charcter of the previous string. This flag tells if we
+ multibyte character of the previous string. This flag tells if we
must consider such a situation or not. */
int maybe_combine_byte;
unsigned char *this_format;
/* Precision for each spec, or -1, a flag value meaning no precision
- was given in that spec. Element 0, corresonding to the format
+ was given in that spec. Element 0, corresponding to the format
string itself, will not be used. Element NARGS, corresponding to
no argument, *will* be assigned to in the case that a `%' and `.'
occur after the final format specifier. */