Ticket #377: some_docs_fixes.patch

docs/multidispatch.pod

@@ -8 +8 @@
 =head1 CAVEATS
 
 XXX - Part or all of this document is outdated.  Especially the "the MMD system
-doesn't handle inheritance" bit.  Please refer to PDD03 at this moment while we
+doesn't handle inheritance" bit.  Please refer to PDD27 at this moment while we
 rewrite or merge this document.  We apologize for the inconvenience.
 
 =head1 SYNOPSIS

docs/vtables.pod

@@ -161 +161 @@
 
 The master list of VTABLE interfaces can be found in F<src/vtable.tbl> in
 the root directory of the Parrot source, with documentation in
-F<docs/pdds/pdd02_vtables.pod>. A few of these are very important, for
+F<docs/pdds/pdd17_pmc.pod>. A few of these are very important, for
 instance:
 
 =over 3

docs/debug.pod

@@ -58 +58 @@
 garbage collector.
 
 Within the C<--gc-debug> mode, there is another tool to help narrow down the
-problem. You can edit F<src/gc/api.c> and C<#define> the C<GC_VERBOSE> flag to
+problem. You can edit F<include/parrot/gc_api.h> and C<#define> the C<GC_VERBOSE> flag to
 1.  After recompiling C<parrot>, the garbage collector will perform additional
 checks. After the garbage collector has traced all objects to find which ones
 are still alive, it will scan through all of the dead objects to see if any of

include/parrot/settings.h

@@ -27 +27 @@
 
 /* Helpful internal macro for testing whether we are currently
  * debugging garbage collection and memory management. See also the
- * definition of GC_VERBOSE in src/gc/api.c. */
+ * definition of GC_VERBOSE in include/parrot/gc_api.h. */
 #if DISABLE_GC_DEBUG
 #  define GC_DEBUG(interp) 0
 #else