From 28e84131a6f728dedb69d7e7ca45daa6bd5b42f2 Mon Sep 17 00:00:00 2001
From: Matthew Flatt <mflatt@racket-lang.org>
Date: Tue, 29 Sep 2009 15:49:37 +0000
Subject: [PATCH] fix insidemz doc bug (merge to 4.2.2)

svn: r16167
---
 collects/scribblings/inside/custodians.scrbl | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

diff --git a/collects/scribblings/inside/custodians.scrbl b/collects/scribblings/inside/custodians.scrbl
index 863cee515a..e2cffb78d7 100644
--- a/collects/scribblings/inside/custodians.scrbl
+++ b/collects/scribblings/inside/custodians.scrbl
@@ -64,7 +64,16 @@ down, then @var{f} is called immediately, and the result is
 @function[(void scheme_custodian_check_available
            [Scheme_Custodian* m]
            [const-char* name]
-           [const-char* resname]
+           [const-char* resname])]{
+
+Checks whether @var{m} is already shut down, and raises an error if
+  so.  If @var{m} is @cpp{NULL}, the current custodian is used. The
+  @var{name} argument is used for error reporting. The @var{resname}
+  argument will likely be used for checking pre-set limits in the
+  future; pre-set limits will have symbolic names, and the
+  @var{resname} string will be compared to the symbols.}
+
+@function[(void scheme_remove_managed
            [Scheme_Custodian_Reference* mref]
            [Scheme_Object* o])]{