Reference pgAdmin as a typical client-side tool, rather than the

no-longer-maintained PgAccess.  Per Erik Rijkers.

diff --git a/doc/src/sgml/plpgsql.sgml b/doc/src/sgml/plpgsql.sgml
index 32f668aabe5577f5412b0b7d1ca13fd5fd289509..29357e4ca9b1c17bb88ce30fd794b464915943b2 100644 (file)
--- a/doc/src/sgml/plpgsql.sgml
+++ b/doc/src/sgml/plpgsql.sgml
@@ -1,4 +1,4 @@
-
+
 
  
   <application>PL/pgSQL</application> - <acronym>SQL</acronym> Procedural Language
@@ -3474,7 +3474,7 @@ $$ LANGUAGE plpgsql;
     Another good way to develop in PL/pgSQL is with a
     GUI database access tool that facilitates development in a
     procedural language. One example of such as a tool is
-    PgAccess, although others exist. These tools often
+    pgAdmin, although others exist. These tools often
     provide convenient features such as escaping single quotes and
     making it easier to recreate and debug functions.
    

diff --git a/doc/src/sgml/start.sgml b/doc/src/sgml/start.sgml
index c97b953c5a1090f7c0ca27638982d74969413efd..1ae900852faefbe89e28b80c937aeb6053489a8f 100644 (file)
--- a/doc/src/sgml/start.sgml
+++ b/doc/src/sgml/start.sgml
@@ -1,4 +1,4 @@
-
+
 
  
   Getting Started
@@ -298,7 +298,7 @@ createdb: database creation failed: ERROR:  permission denied to create database
      
       
        Using an existing graphical frontend tool like
-       PgAccess or an office suite with
+       pgAdmin or an office suite with
        ODBC support to create and manipulate a
        database.  These possibilities are not covered in this
        tutorial.