diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index 5c6a8b3b3db..831f878e463 100644
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -28501,7 +28501,7 @@ acl      | {postgres=arwdDxtm/postgres,foo=r/postgres}
 
    <para>
     The functions shown in <xref linkend="functions-multixact"/>
-    provide information about about current Multixact usage.
+    provide information about multixacts in the system.
    </para>
 
    <table id="functions-multixact">
diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml
index a21b42a6bd3..94f75f3da8f 100644
--- a/doc/src/sgml/maintenance.sgml
+++ b/doc/src/sgml/maintenance.sgml
@@ -779,7 +779,7 @@ HINT:  Execute a database-wide VACUUM in that database.
      careful aging management, storage cleanup, and wraparound handling.
      There is a separate storage area which holds the list of members in
      each multixact, which also uses a 32-bit counter and which must also
-     be managed. The system function <function>pg_get_multixact_members</function>
+     be managed. The system function <function>pg_get_multixact_members()</function>
      described in <xref linkend="functions-info-multixact"/> can be used to
      examine the transaction IDs associated with a multixact ID.
     </para>