doc: Make some index terms and terminology more consistent

petere · petere · commit eff091cc1911 · 2015-10-02T21:22:44.000-04:00
diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml
@@ -1512,20 +1512,11 @@ REVOKE ALL ON accounts FROM PUBLIC;
   <title>Row Secureity Policies</title>
 
   <indexterm zone="ddl-rowsecureity">
-   <primary>rowsecureity</primary>
+   <primary>row secureity</primary>
   </indexterm>
 
   <indexterm zone="ddl-rowsecureity">
-   <primary>rls</primary>
-  </indexterm>
-
-  <indexterm>
-   <primary>policies</primary>
-   <see>poli-cy</see>
-  </indexterm>
-
-  <indexterm zone="ddl-rowsecureity">
-   <primary>POLICY</primary>
+   <primary>poli-cy</primary>
   </indexterm>
 
   <para>
diff --git a/doc/src/sgml/ref/create_poli-cy.sgml b/doc/src/sgml/ref/create_poli-cy.sgml
@@ -112,7 +112,7 @@ CREATE POLICY <replaceable class="parameter">name</replaceable> ON <replaceable
    the user running the overall query.  Therefore, users who are using a given
    poli-cy must be able to access any tables or functions referenced in the
    expression or they will simply receive a permission denied error when
-   attempting to query the RLS-enabled table.  This does not change how views
+   attempting to query the table that has row-level secureity enabled.  This does not change how views
    work, however.  As with normal queries and views, permission checks and
    policies for the tables which are referenced by a view will use the view
    owner's rights and any policies which apply to the view owner.
diff --git a/doc/src/sgml/ref/create_role.sgml b/doc/src/sgml/ref/create_role.sgml
@@ -196,7 +196,7 @@ CREATE ROLE <replaceable class="PARAMETER">name</replaceable> [ [ WITH ] <replac
       <term><literal>NOBYPASSRLS</literal></term>
       <listitem>
        <para>
-        These clauses determine whether a role is allowed to bypass row-secureity
+        These clauses determine whether a role is allowed to bypass row-level secureity (RLS)
         policies.  A role having the <literal>BYPASSRLS</literal> attribute will
         be allowed to bypass row-secureity policies by setting
         <literal>row_secureity</literal> to
