doc: Clean up some recently added PL/pgSQL documentation

- Capitalize titles consistently.
- Fix some grammar.
- Group "Obtaining Information About an Error" under "Trapping Errors",
  but make "Obtaining the Call Stack Context Information" its own
  section, since it's not about errors.

diff --git a/doc/src/sgml/plpgsql.sgml b/doc/src/sgml/plpgsql.sgml
index e3b03f7004ad85dde7d29466285926acda95d22e..91fadb0f14d8802dbff7dabbb5b455b1ad22fc0c 100644 (file)
--- a/doc/src/sgml/plpgsql.sgml
+++ b/doc/src/sgml/plpgsql.sgml
@@ -2641,18 +2641,9 @@ SELECT merge_db(1, 'dennis');
      expected.
     
     
-  
-
-   
-    Getting Diagnostics Information
-
-    
-     diagnostics
-     in PL/pgSQL
-    
 
    
-    Obtaining <span class="marked">information about an e</span>rror
+    Obtaining <span class="marked">Information About an E</span>rror
 
     
      Exception handlers frequently need to identify the specific error that
@@ -2686,7 +2677,7 @@ GET STACKED DIAGNOSTICS variable { = | := } 
     
 
      
-      Error <span class="marked">diagnostics v</span>alues
+      Error <span class="marked">Diagnostics V</span>alues
       
        
         
@@ -2704,17 +2695,17 @@ GET STACKED DIAGNOSTICS variable { = | := } 
         
          COLUMN_NAME
          text
-         the name of column related to exception
+         the name of the column related to exception
         
         
          CONSTRAINT_NAME
          text
-         the name of constraint related to exception
+         the name of the constraint related to exception
         
         
          PG_DATATYPE_NAME
          text
-         the name of data type related to exception
+         the name of the data type related to exception
         
         
          MESSAGE_TEXT
@@ -2724,12 +2715,12 @@ GET STACKED DIAGNOSTICS variable { = | := } 
         
          TABLE_NAME
          text
-         the name of table related to exception
+         the name of the table related to exception
         
         
          SCHEMA_NAME
          text
-         the name of schema related to exception
+         the name of the schema related to exception
         
         
          PG_EXCEPTION_DETAIL
@@ -2773,17 +2764,16 @@ END;
 
     
    
+  
 
-  
-   Obtaining the call stack context information
-
-   
+  
+   Obtaining the Call Stack Context Information
 
 
 GET  CURRENT  DIAGNOSTICS variable { = | := } PG_CONTEXT  , ... ;
 
 
-
+   
     Calling GET DIAGNOSTICS with status
     item PG_CONTEXT will return a text string with line(s) of
     text describing the call stack.  The first row refers to the
@@ -2820,7 +2810,6 @@ PL/pgSQL function outer_func() line 3 at RETURN
 
 
    
-  
   
   
 
@@ -3567,7 +3556,7 @@ RAISE unique_violation USING MESSAGE = 'Duplicate user ID: ' || user_id;
   
 
   
-   Triggers on <span class="marked">data c</span>hanges
+   Triggers on <span class="marked">Data C</span>hanges
 
    
     PL/pgSQL can be used to define trigger
@@ -4119,7 +4108,7 @@ SELECT * FROM sales_summary_bytime;
 
 
   
-   Triggers on <span class="marked">e</span>vents
+   Triggers on <span class="marked">E</span>vents
 
    
     PL/pgSQL can be used to define event
@@ -4712,7 +4701,7 @@ a_output := a_output || $$ if v_$$ || referrer_keys.kind || $$ like '$$
 
   
   
-   Additional <span class="marked">compile-time c</span>hecks
+   Additional <span class="marked">Compile-time C</span>hecks
 
    
     To aid the user in finding instances of simple but common problems before