docs: --privileged docs completeness, consistency

As discussed in https://github.com/containers/libpod/issues/4840

Signed-off-by: Mark Stosberg <mark@rideamigos.com>

1 files changed, 3 insertions, 1 deletions

diff --git a/docs/source/markdown/podman-create.1.md b/docs/source/markdown/podman-create.1.md
index 2bbe4f70a..fdc2edf39 100644
--- a/docs/source/markdown/podman-create.1.md
+++ b/docs/source/markdown/podman-create.1.md
@@ -586,7 +586,7 @@ To make a pod with more granular options, use the `podman pod create` command be
 Give extended privileges to this container. The default is *false*.
 
 By default, Podman containers are
-“unprivileged” (=false) and cannot, for example, modify parts of the kernel.
+“unprivileged” (=false) and cannot, for example, modify parts of the operating system.
 This is because by default a container is not allowed to access any devices.
 A “privileged” container is given access to all devices.
 
@@ -595,6 +595,8 @@ to all devices on the host, turns off graphdriver mount options, as well as
 turning off most of the security measures protecting the host from the
 container.
 
+Rootless containers cannot have more privileges than the account that launched them.
+
 **--publish**, **-p**=*port*
 
 Publish a container's port, or range of ports, to the host