Fix inconsistent markups in catalogs.sgml

Some fields related to pg_opclass and pg_opfamily were using incorrect
markups, listing them as structname instead of structfield.

Author: Fabien Coelho
Discussion: https://postgr.es/m/alpine.DEB.2.22.394.2006210903560.859381@pseudo

diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml
index 700271fd40e1403251473970cec9596a87f66a8c..5a66115df1ee979fd630aa38923fa1af7ee175a7 100644 (file)
--- a/doc/src/sgml/catalogs.sgml
+++ b/doc/src/sgml/catalogs.sgml
@@ -897,7 +897,7 @@
 
   
    An entry's amopmethod must match the
-   name>opfmethod> of its containing operator family (including
+   field>opfmethod> of its containing operator family (including
    amopmethod here is an intentional denormalization of the
    catalog structure for performance reasons).  Also,
    amoplefttype and amoprighttype must match
@@ -5064,10 +5064,10 @@ SCRAM-SHA-256$<iteration count>:&l
 
   
    An operator class's opcmethod must match the
-   name>opfmethod> of its containing operator family.
+   field>opfmethod> of its containing operator family.
    Also, there must be no more than one pg_opclass
-   row having name>opcdefault> true for any given combination of
-   name>opcmethod and opcintype>.
+   row having field>opcdefault> true for any given combination of
+   field>opcmethod and opcintype>.