Update revoke.sgml

2019.12.15更新内容。
将英文原文中</>补充相应tag

Author: chegong18

postgresql/doc/src/sgml/ref/revoke.sgml

@@ -254,13 +254,13 @@ ____________________________________________________________________________-->
    Note that any particular role will have the sum
    of privileges granted directly to it, privileges granted to any role it
    is presently a member of, and privileges granted to
-   <literal>PUBLIC</literal>.  Thus, for example, revoking <literal>SELECT</> privilege
+   <literal>PUBLIC</literal>.  Thus, for example, revoking <literal>SELECT</literal> privilege
    from <literal>PUBLIC</literal> does not necessarily mean that all roles
-   have lost <literal>SELECT</> privilege on the object: those who have it granted
+   have lost <literal>SELECT</literal> privilege on the object: those who have it granted
    directly or via another role will still have it.  Similarly, revoking
-   <literal>SELECT</> from a user might not prevent that user from using
-   <literal>SELECT</> if <literal>PUBLIC</literal> or another membership
-   role still has <literal>SELECT</> rights.
+   <literal>SELECT</literal> from a user might not prevent that user from using
+   <literal>SELECT</literal> if <literal>PUBLIC</literal> or another membership
+   role still has <literal>SELECT</literal> rights.
   </para>
 ____________________________________________________________________________-->
   <para>
@@ -328,10 +328,10 @@ ____________________________________________________________________________-->
 
 <!--==========================orignal english content==========================
   <para>
-   When revoking membership in a role, <literal>GRANT OPTION</> is instead
-   called <literal>ADMIN OPTION</>, but the behavior is similar.
+   When revoking membership in a role, <literal>GRANT OPTION</literal> is instead
+   called <literal>ADMIN OPTION</literal>, but the behavior is similar.
    Note also that this form of the command does not
-   allow the noise word <literal>GROUP</>.
+   allow the noise word <literal>GROUP</literal>.
   </para>
 ____________________________________________________________________________-->
   <para>
@@ -352,7 +352,7 @@ ____________________________________________________________________________-->
    Use <xref linkend="app-psql">'s <command>\dp</command> command to
    display the privileges granted on existing tables and columns.  See <xref
    linkend="sql-grant"> for information about the
-   format.  For non-table objects there are other <command>\d</> commands
+   format.  For non-table objects there are other <command>\d</command> commands
    that can display their privileges.
   </para>
 ____________________________________________________________________________-->
@@ -388,12 +388,12 @@ ____________________________________________________________________________-->
 
 <!--==========================orignal english content==========================
    <para>
-    When a non-owner of an object attempts to <command>REVOKE</> privileges
+    When a non-owner of an object attempts to <command>REVOKE</command> privileges
     on the object, the command will fail outright if the user has no
     privileges whatsoever on the object.  As long as some privilege is
     available, the command will proceed, but it will revoke only those
     privileges for which the user has grant options.  The <command>REVOKE ALL
-    PRIVILEGES</> forms will issue a warning message if no grant options are
+    PRIVILEGES</command> forms will issue a warning message if no grant options are
     held, while the other forms will issue a warning if grant options for
     any of the privileges specifically named in the command are not held.
     (In principle these statements apply to the object owner as well, but
@@ -413,7 +413,7 @@ ____________________________________________________________________________-->
 
 <!--==========================orignal english content==========================
    <para>
-    If a superuser chooses to issue a <command>GRANT</> or <command>REVOKE</>
+    If a superuser chooses to issue a <command>GRANT</command> or <command>REVOKE</command>
     command, the command is performed as though it were issued by the
     owner of the affected object.  Since all privileges ultimately come
     from the object owner (possibly indirectly via chains of grant options),
@@ -431,18 +431,18 @@ ____________________________________________________________________________-->
 
 <!--==========================orignal english content==========================
    <para>
-    <command>REVOKE</> can also be done by a role
+    <command>REVOKE</command> can also be done by a role
     that is not the owner of the affected object, but is a member of the role
     that owns the object, or is a member of a role that holds privileges
     <literal>WITH GRANT OPTION</literal> on the object.  In this case the
     command is performed as though it were issued by the containing role that
     actually owns the object or holds the privileges
     <literal>WITH GRANT OPTION</literal>.  For example, if table
-    <literal>t1</> is owned by role <literal>g1</>, of which role
-    <literal>u1</> is a member, then <literal>u1</> can revoke privileges
-    on <literal>t1</> that are recorded as being granted by <literal>g1</>.
-    This would include grants made by <literal>u1</> as well as by other
-    members of role <literal>g1</>.
+    <literal>t1</literal> is owned by role <literal>g1</literal>, of which role
+    <literal>u1</literal> is a member, then <literal>u1</literal> can revoke privileges
+    on <literal>t1</literal> that are recorded as being granted by <literal>g1</literal>.
+    This would include grants made by <literal>u1</literal> as well as by other
+    members of role <literal>g1</literal>.
    </para>
 ____________________________________________________________________________-->
    <para>
@@ -459,11 +459,11 @@ ____________________________________________________________________________-->
 
 <!--==========================orignal english content==========================
    <para>
-    If the role executing <command>REVOKE</> holds privileges
+    If the role executing <command>REVOKE</command> holds privileges
     indirectly via more than one role membership path, it is unspecified
     which containing role will be used to perform the command.  In such cases
-    it is best practice to use <command>SET ROLE</> to become the specific
-    role you want to do the <command>REVOKE</> as.  Failure to do so might
+    it is best practice to use <command>SET ROLE</command> to become the specific
+    role you want to do the <command>REVOKE</command> as.  Failure to do so might
     lead to revoking privileges other than the ones you intended, or not
     revoking anything at all.
    </para>
@@ -512,7 +512,7 @@ REVOKE ALL PRIVILEGES ON kinds FROM manuel;
 </programlisting>
 
    Note that this actually means <quote>revoke all privileges that I
-   granted</>.
+   granted</quote>.
   </para>
 ____________________________________________________________________________-->
   <para>
@@ -528,7 +528,7 @@ REVOKE ALL PRIVILEGES ON kinds FROM manuel;
 
 <!--==========================orignal english content==========================
   <para>
-   Revoke membership in role <literal>admins</> from user <literal>joe</>:
+   Revoke membership in role <literal>admins</literal> from user <literal>joe</literal>:
 
 <programlisting>
 REVOKE admins FROM joe;
@@ -553,7 +553,7 @@ ____________________________________________________________________________-->
     The compatibility notes of the <xref linkend="sql-grant"> command
     apply analogously to <command>REVOKE</command>.
     The keyword <literal>RESTRICT</literal> or <literal>CASCADE</literal>
-    is required according to the standard, but <productname>PostgreSQL</>
+    is required according to the standard, but <productname>PostgreSQL</productname>
     assumes <literal>RESTRICT</literal> by default.
    </para>
 ____________________________________________________________________________-->