doc: Fix naming of SELinux

Reported-by: Tham Nguyen
Discussion: https://postgr.es/m/157851402876.29175.12977878383183540468@wrigleys.postgresql.org
Backpatch-through: 9.4

diff --git a/doc/src/sgml/dummy-seclabel.sgml b/doc/src/sgml/dummy-seclabel.sgml
index d064705f2aeb661bb883f16897c7251774a43bec..f735cb5315f9a6b6843293aad1e303465321ead4 100644 (file)
--- a/doc/src/sgml/dummy-seclabel.sgml
+++ b/doc/src/sgml/dummy-seclabel.sgml
@@ -26,7 +26,7 @@
   <para>
    Security label providers intended to be used in production will typically be
    dependent on a platform-specific feature such as
-   <productname>SE-Linux</productname>.  This module is platform-independent,
+   <productname>SELinux</productname>.  This module is platform-independent,
    and therefore better-suited to regression testing.
   </para>
  </sect2>

diff --git a/doc/src/sgml/ref/security_label.sgml b/doc/src/sgml/ref/security_label.sgml
index 6e2bd25240b728d8aa8a1b21382f2a802c287451..e17bc8cd462e014e195a63998ebd7845d40d8fa2 100644 (file)
--- a/doc/src/sgml/ref/security_label.sgml
+++ b/doc/src/sgml/ref/security_label.sgml
@@ -76,7 +76,7 @@ SECURITY LABEL [ FOR <replaceable class="PARAMETER">provider</replaceable> ] ON
    label provider must interpret security labels; it merely provides a
    mechanism for storing them.  In practice, this facility is intended to allow
    integration with label-based mandatory access control (MAC) systems such as
-   <productname>SE-Linux</>.  Such systems make all access control decisions
+   <productname>SELinux</>.  Such systems make all access control decisions
    based on object labels, rather than traditional discretionary access control
    (DAC) concepts such as users and groups.
   </para>