diff options
author | Neil Jerram <neil@ossau.uklinux.net> | 2009-05-20 18:50:52 +0100 |
---|---|---|
committer | Neil Jerram <neil@ossau.uklinux.net> | 2009-05-20 18:51:03 +0100 |
commit | 877f06c33829ac2a5ba263826454f880d5460ee8 (patch) | |
tree | 3c7390fa28c0ab8746d7a1a556e720fae38343f7 /doc/ref/api-init.texi | |
parent | 58df2e43937bb86fbf751f48db7bf13934d7c87e (diff) | |
download | guile-877f06c33829ac2a5ba263826454f880d5460ee8.tar.gz |
Fix `explicitely' typos, should be `explicitly'
Diffstat (limited to 'doc/ref/api-init.texi')
-rw-r--r-- | doc/ref/api-init.texi | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/ref/api-init.texi b/doc/ref/api-init.texi index 0e4e8b8b7..f9714c3b6 100644 --- a/doc/ref/api-init.texi +++ b/doc/ref/api-init.texi @@ -61,7 +61,7 @@ Arrange things so that all of the code in the current thread executes as if from within a call to @code{scm_with_guile}. That is, all functions called by the current thread can assume that @code{SCM} values on their stack frames are protected from the garbage collector (except when the -thread has explicitely left guile mode, of course). +thread has explicitly left guile mode, of course). When @code{scm_init_guile} is called from a thread that already has been in guile mode once, nothing happens. This behavior matters when you |