diff options
-rw-r--r-- | man2/mount_setattr.2 | 2 | ||||
-rw-r--r-- | man2/openat2.2 | 2 | ||||
-rw-r--r-- | man7/landlock.7 | 2 |
3 files changed, 3 insertions, 3 deletions
diff --git a/man2/mount_setattr.2 b/man2/mount_setattr.2 index 24801a4bd..8df02641a 100644 --- a/man2/mount_setattr.2 +++ b/man2/mount_setattr.2 @@ -862,7 +862,7 @@ may change in the future user-space applications should zero-fill .I struct mount_attr to ensure that recompiling the program with new headers will not result in -spurious errors at runtime. +spurious errors at run time. The simplest way is to use a designated initializer: .PP .in +4n diff --git a/man2/openat2.2 b/man2/openat2.2 index e90211fad..182851089 100644 --- a/man2/openat2.2 +++ b/man2/openat2.2 @@ -545,7 +545,7 @@ may change in the future (with new fields being added when system headers are updated), user-space applications should zero-fill .I struct open_how to ensure that recompiling the program with new headers will not result in -spurious errors at runtime. +spurious errors at run time. The simplest way is to use a designated initializer: .PP diff --git a/man7/landlock.7 b/man7/landlock.7 index b6c9d3821..df7b87e80 100644 --- a/man7/landlock.7 +++ b/man7/landlock.7 @@ -251,7 +251,7 @@ will stay enforced on all this thread's descendants. This allows creating standalone and modular security policies per application, which will automatically be composed between themselves -according to their runtime parent policies. +according to their run-time parent policies. .\" .SS Ptrace restrictions A sandboxed process has less privileges than a non-sandboxed process and |