From 630abd84e41ff82f8bf8eec62fb41c9a8bbb2e5f Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Wed, 2 Nov 2016 03:57:08 +0100 Subject: [PATCH] keyrings.7: wfix Signed-off-by: Michael Kerrisk --- man7/keyrings.7 | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/man7/keyrings.7 b/man7/keyrings.7 index 8ce2e6dc0..84db5524b 100644 --- a/man7/keyrings.7 +++ b/man7/keyrings.7 @@ -78,7 +78,8 @@ when it was requested. A key's payload can be read and updated if the key type supports it and if suitable permission is granted to the caller. .IP "\fBAccess rights\fR" -Each key has an owning user ID, an owning group, and a security label - much as +Much as files do, +each key has an owning user ID, an owning group ID, and a security label. files do. They also have a set of permissions, though there are more than for a normal UNIX file, @@ -125,7 +126,7 @@ It may be read and updated by user-space applications This is similar to \fBuser\fR but it may hold data up to 1MB in size. The data may be stored in the swap space rather than in kernel memory if the size exceeds the overhead of doing so -(a tmpfs file is used - which requires filesystem structures +(a tmpfs file is used, which requires filesystem structures to be allocated in the kernel). .IP "\fBlogon\fR" This is similar to \fBuser\fR but the contents may not be read by @@ -182,8 +183,8 @@ The kernel makes available a number of anchor keyrings. Note that some of these keyrings will be created only when first accessed. .IP "\fBProcess keyrings\fR" Process credentials themselves reference keyrings with specific semantics. -These keyrings are pinned as long as the set of credentials exists - which is -usually as long as the process does. +These keyrings are pinned as long as the set of credentials exists, +which is usually as long as the process exists. .IP There are three keyrings with different inheritance/sharing rules: The