diff options
| author | Michael Paquier | 2020-01-10 00:37:44 +0000 |
|---|---|---|
| committer | Michael Paquier | 2020-01-10 00:37:44 +0000 |
| commit | 27676e22d330e6a6f30b1e1dd6ed6e3d3413f200 (patch) | |
| tree | 4722f03ac0bc3bcb27f00831b67324ff61c8d361 | |
| parent | b83ba2e6e7060fd8c37bd57e660b2ad64a1a9cd6 (diff) | |
doc: Fix naming of SELinux
Reported-by: Tham Nguyen
Discussion: https://postgr.es/m/[email protected]
Backpatch-through: 9.4
| -rw-r--r-- | doc/src/sgml/dummy-seclabel.sgml | 2 | ||||
| -rw-r--r-- | doc/src/sgml/ref/security_label.sgml | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/sgml/dummy-seclabel.sgml b/doc/src/sgml/dummy-seclabel.sgml index d064705f2a..f735cb5315 100644 --- 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 6e2bd25240..e17bc8cd46 100644 --- 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> |