Index: ossp-pkg/ex/ex.pod
RCS File: /v/ossp/cvs/ossp-pkg/ex/ex.pod,v
rcsdiff -q -kk '-r1.24' '-r1.25' -u '/v/ossp/cvs/ossp-pkg/ex/ex.pod,v' 2>/dev/null
--- ex.pod	2002/04/02 06:36:38	1.24
+++ ex.pod	2002/04/02 17:54:09	1.25
@@ -441,7 +441,7 @@
 clause, it is also evaluated before the B<ex_catch> clause. So,
 resources being cleaned up must no longer be used in the B<ex_catch>
 block. The example above would have trouble referencing the character
-strings in the printf(3) statement because these have been free()d
+strings in the printf(3) statement because these have been free(3)'d
 before.
 
 =item B<05: variable uninitialization>
@@ -449,7 +449,7 @@
 If resources are passed away and out of the scope of the
 B<ex_try>/B<ex_clean>/B<ex_catch> construct and the variables were
 initialized for using a "free if unset" approach then they must be
-uninitialized after being passed away. The example above would free()
+uninitialized after being passed away. The example above would free(3)
 C<cp1> in the B<ex_clean> clause if mallocex() throws an exception if
 allocating a C<TOOBIG> buffer. The C<globalcontext-&gt;first> pointer
 hence becomes invalid.