doc: Improve hyphenation consistency

7 files changed, 19 insertions, 19 deletions

diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml
index 1345791e963..492ed348b3a 100644
--- a/doc/src/sgml/catalogs.sgml
+++ b/doc/src/sgml/catalogs.sgml
@@ -1556,7 +1556,7 @@
        <structfield>rolbypassrls</structfield> <type>bool</type>
       </para>
       <para>
-       Role bypasses every row level security policy, see
+       Role bypasses every row-level security policy, see
        <xref linkend="ddl-rowsecurity"/> for more information.
       </para></entry>
      </row>
@@ -2130,7 +2130,7 @@ SCRAM-SHA-256$<replaceable>&lt;iteration count&gt;</replaceable>:<replaceable>&l
        <structfield>relrowsecurity</structfield> <type>bool</type>
       </para>
       <para>
-       True if table has row level security enabled; see
+       True if table has row-level security enabled; see
        <link linkend="catalog-pg-policy"><structname>pg_policy</structname></link> catalog
       </para></entry>
      </row>
@@ -2140,7 +2140,7 @@ SCRAM-SHA-256$<replaceable>&lt;iteration count&gt;</replaceable>:<replaceable>&l
        <structfield>relforcerowsecurity</structfield> <type>bool</type>
       </para>
       <para>
-       True if row level security (when enabled) will also apply to table owner; see
+       True if row-level security (when enabled) will also apply to table owner; see
        <link linkend="catalog-pg-policy"><structname>pg_policy</structname></link> catalog
       </para></entry>
      </row>
@@ -5531,7 +5531,7 @@ SCRAM-SHA-256$<replaceable>&lt;iteration count&gt;</replaceable>:<replaceable>&l
   </indexterm>
 
   <para>
-   The catalog <structname>pg_policy</structname> stores row level
+   The catalog <structname>pg_policy</structname> stores row-level
    security policies for tables.  A policy includes the kind of
    command that it applies to (possibly all commands), the roles that it
    applies to, the expression to be added as a security-barrier
@@ -11765,7 +11765,7 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx
        <structfield>rolbypassrls</structfield> <type>bool</type>
       </para>
       <para>
-       Role bypasses every row level security policy, see
+       Role bypasses every row-level security policy, see
        <xref linkend="ddl-rowsecurity"/> for more information.
       </para></entry>
      </row>
@@ -12554,7 +12554,7 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx
        <structfield>usebypassrls</structfield> <type>bool</type>
       </para>
       <para>
-       User bypasses every row level security policy, see
+       User bypasses every row-level security policy, see
        <xref linkend="ddl-rowsecurity"/> for more information.
       </para></entry>
      </row>
@@ -13667,7 +13667,7 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx
        <structfield>usebypassrls</structfield> <type>bool</type>
       </para>
       <para>
-       User bypasses every row level security policy, see
+       User bypasses every row-level security policy, see
        <xref linkend="ddl-rowsecurity"/> for more information.
       </para></entry>
      </row>
diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml
index 30e41709634..7d587b226cb 100644
--- a/doc/src/sgml/ddl.sgml
+++ b/doc/src/sgml/ddl.sgml
@@ -2382,7 +2382,7 @@ INSERT INTO passwd VALUES
 INSERT INTO passwd VALUES
   ('alice','xxx',2,1,'Alice','098-765-4321',null,'/home/alice','/bin/zsh');
 
--- Be sure to enable row level security on the table
+-- Be sure to enable row-level security on the table
 ALTER TABLE passwd ENABLE ROW LEVEL SECURITY;
 
 -- Create policies
diff --git a/doc/src/sgml/ref/alter_policy.sgml b/doc/src/sgml/ref/alter_policy.sgml
index 1c38324b599..fbc262ba20d 100644
--- a/doc/src/sgml/ref/alter_policy.sgml
+++ b/doc/src/sgml/ref/alter_policy.sgml
@@ -16,7 +16,7 @@ PostgreSQL documentation
 
  <refnamediv>
   <refname>ALTER POLICY</refname>
-  <refpurpose>change the definition of a row level security policy</refpurpose>
+  <refpurpose>change the definition of a row-level security policy</refpurpose>
  </refnamediv>
 
  <refsynopsisdiv>
diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml
index 07e37a6dc81..39927be41ed 100644
--- a/doc/src/sgml/ref/alter_table.sgml
+++ b/doc/src/sgml/ref/alter_table.sgml
@@ -611,7 +611,7 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM
       These forms control the application of row security policies belonging
       to the table.  If enabled and no policies exist for the table, then a
       default-deny policy is applied.  Note that policies can exist for a table
-      even if row level security is disabled.  In this case, the policies will
+      even if row-level security is disabled.  In this case, the policies will
       <emphasis>not</emphasis> be applied and the policies will be ignored.
       See also
       <link linkend="sql-createpolicy"><command>CREATE POLICY</command></link>.
@@ -624,9 +624,9 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM
     <listitem>
      <para>
       These forms control the application of row security policies belonging
-      to the table when the user is the table owner.  If enabled, row level
+      to the table when the user is the table owner.  If enabled, row-level
       security policies will be applied when the user is the table owner.  If
-      disabled (the default) then row level security will not be applied when
+      disabled (the default) then row-level security will not be applied when
       the user is the table owner.
       See also
       <link linkend="sql-createpolicy"><command>CREATE POLICY</command></link>.
diff --git a/doc/src/sgml/ref/create_policy.sgml b/doc/src/sgml/ref/create_policy.sgml
index b4f90561018..9f532068e64 100644
--- a/doc/src/sgml/ref/create_policy.sgml
+++ b/doc/src/sgml/ref/create_policy.sgml
@@ -16,7 +16,7 @@ PostgreSQL documentation
 
  <refnamediv>
   <refname>CREATE POLICY</refname>
-  <refpurpose>define a new row level security policy for a table</refpurpose>
+  <refpurpose>define a new row-level security policy for a table</refpurpose>
  </refnamediv>
 
  <refsynopsisdiv>
@@ -188,7 +188,7 @@ CREATE POLICY <replaceable class="parameter">name</replaceable> ON <replaceable
       Any <acronym>SQL</acronym> conditional expression (returning
       <type>boolean</type>).  The conditional expression cannot contain
       any aggregate or window functions.  This expression will be added
-      to queries that refer to the table if row level security is enabled.
+      to queries that refer to the table if row-level security is enabled.
       Rows for which the expression returns true will be visible.  Any
       rows for which the expression returns false or null will not be
       visible to the user (in a <command>SELECT</command>), and will not be
@@ -207,7 +207,7 @@ CREATE POLICY <replaceable class="parameter">name</replaceable> ON <replaceable
       <type>boolean</type>).  The conditional expression cannot contain
       any aggregate or window functions.  This expression will be used in
       <command>INSERT</command> and <command>UPDATE</command> queries against
-      the table if row level security is enabled.  Only rows for which the
+      the table if row-level security is enabled.  Only rows for which the
       expression evaluates to true will be allowed.  An error will be thrown
       if the expression evaluates to false or null for any of the records
       inserted or any of the records that result from the update.  Note that
diff --git a/doc/src/sgml/ref/drop_policy.sgml b/doc/src/sgml/ref/drop_policy.sgml
index 9297ade1133..d7d3771faea 100644
--- a/doc/src/sgml/ref/drop_policy.sgml
+++ b/doc/src/sgml/ref/drop_policy.sgml
@@ -16,7 +16,7 @@ PostgreSQL documentation
 
  <refnamediv>
   <refname>DROP POLICY</refname>
-  <refpurpose>remove a row level security policy from a table</refpurpose>
+  <refpurpose>remove a row-level security policy from a table</refpurpose>
  </refnamediv>
 
  <refsynopsisdiv>
@@ -31,9 +31,9 @@ DROP POLICY [ IF EXISTS ] <replaceable class="parameter">name</replaceable> ON <
   <para>
    <command>DROP POLICY</command> removes the specified policy from the table.
    Note that if the last policy is removed for a table and the table still has
-   row level security enabled via <command>ALTER TABLE</command>, then the
+   row-level security enabled via <command>ALTER TABLE</command>, then the
    default-deny policy will be used.  <literal>ALTER TABLE ... DISABLE ROW
-   LEVEL SECURITY</literal> can be used to disable row level security for a
+   LEVEL SECURITY</literal> can be used to disable row-level security for a
    table, whether policies for the table exist or not.
   </para>
  </refsect1>
diff --git a/doc/src/sgml/rules.sgml b/doc/src/sgml/rules.sgml
index 2ae6925b418..5024e4ff704 100644
--- a/doc/src/sgml/rules.sgml
+++ b/doc/src/sgml/rules.sgml
@@ -2123,7 +2123,7 @@ SELECT * FROM phone_number WHERE tricky(person, phone);
 </para>
 
 <para>
-    When it is necessary for a view to provide row level security, the
+    When it is necessary for a view to provide row-level security, the
     <literal>security_barrier</literal> attribute should be applied to
     the view.  This prevents maliciously-chosen functions and operators from
     being passed values from rows until after the view has done its work.  For