summaryrefslogtreecommitdiff
path: root/doc/ref/api-deprecated.texi
diff options
context:
space:
mode:
Diffstat (limited to 'doc/ref/api-deprecated.texi')
-rw-r--r--doc/ref/api-deprecated.texi2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/ref/api-deprecated.texi b/doc/ref/api-deprecated.texi
index 76f099727..049052ff9 100644
--- a/doc/ref/api-deprecated.texi
+++ b/doc/ref/api-deprecated.texi
@@ -12,7 +12,7 @@ Guile's @dfn{deprecation} is a mechanism that can help you cope with
this.
When you use a feature that is deprecated, you will likely get a warning
-message at run-time. Also, if you have a new enough toolchain, using a
+message at run-time. Also, if you have a new enough toolchain, using a
deprecated function from @code{libguile} will cause a link-time warning.
The primary source for information about just what interfaces are