Index: docs/debug.pod
===================================================================
--- docs/debug.pod	(revision 18711)
+++ docs/debug.pod	(working copy)
@@ -47,7 +47,7 @@
 
 Infant mortality
 
-See F<docs/dev/infant.dev> for details of one frequent problem: infant
+See F<docs/dev/infant.pod> for details of one frequent problem: infant
 mortality. Infant mortality is when you create a Parrot object, but the garbage
 collector runs before you put it into a Parrot register or in something else
 that is itself within a Parrot register.
Index: docs/pdds/pdd00_pdd.pod
===================================================================
--- docs/pdds/pdd00_pdd.pod	(revision 18711)
+++ docs/pdds/pdd00_pdd.pod	(working copy)
@@ -21,7 +21,7 @@
 
 The key aspects of Parrot's design are its interface to the outside world --
 its feature set -- and its internal structure, both in code and in the broader
-project.  Thus, PDDs descirbe Parrot's:
+project.  Thus, PDDs describe Parrot's:
 
 =over 4
 
@@ -48,8 +48,8 @@
 
 PDDS B<should not> discuss the implementation details or trade-offs, unless
 they absolutely have to.  Such implementation documentation should go in the
-relevant F<*.dev> file.  On the other hand, PDDs B<should> document design
-trade-offs, i.e. the paths not chosen.
+relevant F<docs/dev/*.pod> file.  On the other hand, PDDs B<should> document
+design trade-offs, i.e. the paths not chosen.
 
 These guidelines may seem fuzzy.  The line between "design" and
 "implementation" is a murky one.  Still, please try to adhere to this design
Index: docs/pdds/pdd07_codingstd.pod
===================================================================
--- docs/pdds/pdd07_codingstd.pod	(revision 18711)
+++ docs/pdds/pdd07_codingstd.pod	(working copy)
@@ -807,7 +807,7 @@
 documentation containing information on the implementation decisions associated
 with the source file. (Note that this is in contrast to PDDs, which describe
 design decisions). In addition, more discussive documentation can be placed in
-F<*.dev> files in the F<docs/dev> directory. This is the place for mini-essays
+F<*.pod> files in the F<docs/dev> directory. This is the place for mini-essays
 on how to avoid overflows in unsigned arithmetic, or on the pros and cons of
 differing hash algorithms, and why the current one was chosen, and how it
 works.
@@ -898,7 +898,7 @@
 schmuck trying subsequently to replace it with something 'cleaner'.
 
     /* The loop is partially unrolled here as it makes it a lot faster.
-     * See the .dev file for the full details
+     * See the file in docs/dev for the full details
      */
 
 =item General comments
Index: docs/gettingstarted.pod
===================================================================
--- docs/gettingstarted.pod	(revision 18711)
+++ docs/gettingstarted.pod	(working copy)
@@ -120,11 +120,11 @@
 and cons of differing hash algorithms, and why the current one was chosen, and
 how it works.
 
-If you are coming to a particular source file for the first time, you should be
-able to read the F<.dev> file and gain an immediate overview of what the source
-file is for, the algorithms it implements, etc.
+If you are coming to a particular source file for the first time, you should
+be able to read the developer file and gain an immediate overview of what
+the source file is for, the algorithms it implements, etc.
 
-NB: We need more F<.dev> files too. Patches welcome!
+NB: We need more developer files too. Patches welcome!
 
 =item * Source file documentation