Minor typo corrections in PAC macros comments

confdb/aclocal_fc.m4

@@ -35,9 +35,9 @@ dnl       it may also be the name of a command for something other than
 dnl       the Fortran compiler (e.g., fc=file system check!)
 dnl gfortran - The GNU Fortran compiler (not the same as g95) 
 dnl gfc - An alias for gfortran recommended in cygwin installations
-dnl D*/
 dnl NOTE: this macro suffers from a basically intractable "expanded before it
 dnl was required" problem when libtool is also used
+dnl D*/
 AC_DEFUN([PAC_PROG_FC],[
 PAC_PUSH_FLAG([FCFLAGS])
 AC_PROG_FC([m4_default([$1],[PAC_FC_SEARCH_LIST])])
@@ -359,7 +359,7 @@ if test "X$pac_cv_fc_module_incflag" = "X" ; then
         # compiled.  
         # Intel compilers use a wierd system: -cl,filename.pcl .  If no file is
         # specified, work.pcl and work.pc are created.  However, if you specify
-        # a file, it must contain a the name of a file ending in .pc .  Ugh!
+        # a file, it must contain the name of a file ending in .pc .  Ugh!
         pac_cv_fc_module_incflag="unknown"
     fi
 fi

confdb/aclocal_mpi.m4

@@ -34,7 +34,7 @@ if test "X$pac_lib_mpi_is_building" != "Xyes" ; then
      fi
   fi
   # Look for MPILIB first if it is defined
-  AC_SEARCH_LIBS(MPI_Init,$MPILIB mpi mpich mpich)
+  AC_SEARCH_LIBS(MPI_Init,$MPILIB mpi mpich)
   if test "$ac_cv_search_MPI_Init" = "no" ; then
     ifelse($2,,
     AC_MSG_ERROR([Could not find MPI library]),[$2])
@@ -157,7 +157,7 @@ if test "$ac_mpi_type" = "unknown" -a "$pac_lib_mpi_is_building" = "yes" ; then
 fi
 ])
 dnl
-dnl Because of autoconf insists on moving code to the beginning of 
+dnl Because autoconf insists on moving code to the beginning of
 dnl certain definitions, it is *not possible* to define a single command
 dnl that selects compilation scripts and also check for other options.
 dnl Thus, this needs to be divided into