summaryrefslogtreecommitdiff
path: root/doc/ref/libguile-foreign-objects.texi
diff options
context:
space:
mode:
Diffstat (limited to 'doc/ref/libguile-foreign-objects.texi')
-rw-r--r--doc/ref/libguile-foreign-objects.texi8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/ref/libguile-foreign-objects.texi b/doc/ref/libguile-foreign-objects.texi
index 11941d566..29e1f8619 100644
--- a/doc/ref/libguile-foreign-objects.texi
+++ b/doc/ref/libguile-foreign-objects.texi
@@ -279,10 +279,10 @@ Note that the finalizer may be invoked in ways and at times you might
not expect. In particular, if the user's Guile is built with support
for threads, the finalizer may be called from any thread that is running
Guile. In Guile 2.0, finalizers are invoked via ``asyncs'', which
-interleaves them with running Scheme code; @pxref{System asyncs}. In
-Guile 2.2 there will be a dedicated finalization thread, to ensure that
-the finalization doesn't run within the critical section of any other
-thread known to Guile.
+interleaves them with running Scheme code; @pxref{Asyncs}. In Guile 2.2
+there will be a dedicated finalization thread, to ensure that the
+finalization doesn't run within the critical section of any other thread
+known to Guile.
In either case, finalizers run concurrently with the main program, and
so they need to be async-safe and thread-safe. If for some reason this