Merge pull request #16411 from ddstreet/bridge_without_carrier_fails

[thirdparty/systemd.git] / docs / USER_NAMES.md

diff --git a/docs/USER_NAMES.md b/docs/USER_NAMES.md
index a56984b044a7439783d78bd7e27eb72235309949..ec07b19f306b44b17332fac374e7ba022742d5c8 100644 (file)
--- a/docs/USER_NAMES.md
+++ b/docs/USER_NAMES.md
@@ -68,9 +68,9 @@ Distilled from the above, below are the rules systemd enforces on user/group
 names. An additional, common rule between both modes listed below is that empty
 strings are not valid user/group names.
 
-Philosophically, the strict mode described below enforces a white-list of what's
-allowed and prohibits everything else, while the relaxed mode described below
-implements a blacklist of what's not allowed and permits everything else.
+Philosophically, the strict mode described below enforces an allow list of
+what's allowed and prohibits everything else, while the relaxed mode described
+below implements a deny list of what's not allowed and permits everything else.
 
 ### Strict mode
 
@@ -157,7 +157,7 @@ it creates ambiguity in traditional `chown` syntax (which is still accepted
 today) that uses it to separate user and group names in the command's
 parameter: without consulting the user/group databases it is not possible to
 determine if a `chown` invocation would change just the owning user or both the
-owning user and group. It also allows embeddeding `@` (which is confusing to
+owning user and group. It also allows embedding `@` (which is confusing to
 MTAs).
 
 ## Common Core