diff --git a/doc/src/FAQ/FAQ_DEV.html b/doc/src/FAQ/FAQ_DEV.html
index 179f6168438eba62dd68bd71e77323614d7169ed..94306bdbe45834901a22a765cbeff2fb2342a5db 100644
--- a/doc/src/FAQ/FAQ_DEV.html
+++ b/doc/src/FAQ/FAQ_DEV.html
@@ -76,6 +76,7 @@
     make_mkid       make mkid ID files
     mkldexport      create AIX exports file
     pgindent        indents C source files
+    pgjindent       indents Java source files
     pginclude       scripts for adding/removing include files
     unused_oids     in pgsql/src/include/catalog
 </PRE>
@@ -112,7 +113,7 @@
     Others prefer <I>glimpse.</I> 
 
     <P><I>make_diff</I> has tools to create patch diff files that can
-    be applied to the distribution.  This produces context diffs, which
+    be applied to the distribution. This produces context diffs, which
     is our preferred format.</P>
 
     <P>Our standard format is to indent each code level with one tab,
@@ -163,10 +164,14 @@
     consistent. Comment blocks that need specific line breaks should be
     formatted as <I>block comments,</I> where the comment starts as
     <CODE>/*------</CODE>. These comments will not be reformatted in
-    any way. <I>pginclude</I> contains scripts used to add needed
-    #include's to include files, and removed unneeded #include's. When
-    adding system types, you will need to assign oids to them. There is
-    also a script called <I>unused_oids</I> in
+    any way.</P>
+
+    <P><I>pginclude</I> contains scripts used to add needed
+    <CODE>#include</CODE>'s to include files, and removed unneeded
+    <CODE>#include</CODE>'s.</P>
+
+    <P>When adding system types, you will need to assign oids to them.
+    There is also a script called <I>unused_oids</I> in
     <I>pgsql/src/include/catalog</I> that shows the unused oids.</P>
 
     <H3><A name="2">2</A>) What books are good for developers?</H3>
diff --git a/src/tools/find_baddefs b/src/tools/find_badmacros
similarity index 100%
rename from src/tools/find_baddefs
rename to src/tools/find_badmacros