diff options
| -rw-r--r-- | Base/usr/share/man/man2/mount.md | 2 | ||||
| -rw-r--r-- | Base/usr/share/man/man3/posix_spawnattr_init.md | 2 | ||||
| -rw-r--r-- | Base/usr/share/man/man5/Shell.md | 4 | ||||
| -rw-r--r-- | Base/usr/share/man/man7/Mitigations.md | 2 | ||||
| -rw-r--r-- | Base/usr/share/man/man7/Shell-vars.md | 2 | ||||
| -rw-r--r-- | Base/usr/share/man/man7/setuid_overview.md | 2 |
6 files changed, 7 insertions, 7 deletions
diff --git a/Base/usr/share/man/man2/mount.md b/Base/usr/share/man/man2/mount.md index 63904326e1..7c5b2c6854 100644 --- a/Base/usr/share/man/man2/mount.md +++ b/Base/usr/share/man/man2/mount.md @@ -73,7 +73,7 @@ to use the new mount flags after remounting a filesystem, a process can call Similarly, to change the mount flags used by the root directory, a process can call [`chroot_with_mount_flags`(2)](chroot.md), specifying a single slash (`/`) -as the path along with the desired flags. While is's possible to remount the +as the path along with the desired flags. While it is possible to remount the root filesystem using `MS_REMOUNT`, it would only have a noticeable effect if the kernel was to launch more userspace processes directly, the way it does launch the initial userspace process. diff --git a/Base/usr/share/man/man3/posix_spawnattr_init.md b/Base/usr/share/man/man3/posix_spawnattr_init.md index 1ab9cbf066..e64ea805bf 100644 --- a/Base/usr/share/man/man3/posix_spawnattr_init.md +++ b/Base/usr/share/man/man3/posix_spawnattr_init.md @@ -60,7 +60,7 @@ It is valid to alternatingly call `posix_spawnattr_init()` and `posix_spawnattr_ * `POSIX_SPAWN_SETSIGMASK`: If set, `posix_spawn()` will set the signal mask of the child process to the signal mask configured with `posix_spawnattr_setsigmask()`, as if `sigprocmask()` was called in the child process. -* `POSIX_SPAWN_SETSID`: If set, `posix_spawn()` will run the child process in a new session, as if `setsid()` was called in the child process. The behavior if bboth this an d`POSIX_SPAWN_SETPGROUP` is set is undefined. +* `POSIX_SPAWN_SETSID`: If set, `posix_spawn()` will run the child process in a new session, as if `setsid()` was called in the child process. The behavior if both this and `POSIX_SPAWN_SETPGROUP` is set is undefined. The `posix_spawnattr_get*` functions return what's been set with the corresponding setters. The default `flags` and `pgroup` are 0, the default `sigdefault` set is `sigemptyset()`, all other fields have an unspecified default value. diff --git a/Base/usr/share/man/man5/Shell.md b/Base/usr/share/man/man5/Shell.md index 278f197e46..5815a73321 100644 --- a/Base/usr/share/man/man5/Shell.md +++ b/Base/usr/share/man/man5/Shell.md @@ -195,7 +195,7 @@ Commands can be either calls to Shell builtins, or external programs. The commands can be composed into semantic elements, producing composite commands: ### Sequences -A sequence of commands, executed serially independent of each other: `Commanad ; Command ; Command ...` +A sequence of commands, executed serially independent of each other: `Command ; Command ; Command ...` It should be noted that a newline (`\\n`) can be substituted for the semicolon (`;`). @@ -263,7 +263,7 @@ The general syntax follows the form `for index index_name name in expr { sequenc It should be noted that the `index index_name` section is optional, but if supplied, will require an explicit iteration variable as well. In other words, `for index i in foo` is not valid syntax. -A for-loop evaluates the _sequence_ once per every element in the _expr_, seetting the local variable _name_ to the element being processed, and the local variable _enum name_ to the enumeration index (if set). +A for-loop evaluates the _sequence_ once per every element in the _expr_, setting the local variable _name_ to the element being processed, and the local variable _enum name_ to the enumeration index (if set). The Shell shall cancel the for loop if two consecutive commands are interrupted via SIGINT (\^C), and any other terminating signal aborts the loop entirely. diff --git a/Base/usr/share/man/man7/Mitigations.md b/Base/usr/share/man/man7/Mitigations.md index 966fe9a982..e4bb883abe 100644 --- a/Base/usr/share/man/man7/Mitigations.md +++ b/Base/usr/share/man/man7/Mitigations.md @@ -132,7 +132,7 @@ Kernel: KUBSAN! (Kernel Undefined Behavior SANitizer) :^) ### Kernel unmap-after-init -Umap-after-init allows the kernel to remove functions which contain potentially +Unmap-after-init allows the kernel to remove functions which contain potentially dangerous [ROP gadgets](https://en.wikipedia.org/wiki/Return-oriented_programming) from kernel memory after we've booted up and they are no longer needed. Notably the `write_cr4(..)` function used to control processor features like the SMEP/SMAP bits diff --git a/Base/usr/share/man/man7/Shell-vars.md b/Base/usr/share/man/man7/Shell-vars.md index 82e4153edf..2666621ec6 100644 --- a/Base/usr/share/man/man7/Shell-vars.md +++ b/Base/usr/share/man/man7/Shell-vars.md @@ -4,7 +4,7 @@ Shell Variables - Special local and environment variables used by the Shell ## Description -The Shell uses various variables to allow for customisations of certain behavioral or visual things. +The Shell uses various variables to allow for customizations of certain behavioral or visual things. Such variables can be changed or set by the user to tweak how the shell presents things. ## Behavioral diff --git a/Base/usr/share/man/man7/setuid_overview.md b/Base/usr/share/man/man7/setuid_overview.md index aa7829598a..9866780159 100644 --- a/Base/usr/share/man/man7/setuid_overview.md +++ b/Base/usr/share/man/man7/setuid_overview.md @@ -22,7 +22,7 @@ Since SUID binaries are able to bypass access checks, only carefully selected bi In some instances, it is useful for a SUID binary to either temporarily or permanently drop its permissions and set the effective user ID to the real user ID. -To make this possible, each process has *three* user (and group) IDs: The (real) user ID, the *effective* user ID, and the *saved* user ID. When a process executes a normal binary, all three IDs are set to the parent process's user ID. However, when a process executes a SUID binary, the process runs with the paren process's ID as its real ID, but it takes its effective ID and saved ID from the binary. (Analogously for the group ID for SGID binaries.) +To make this possible, each process has *three* user (and group) IDs: The (real) user ID, the *effective* user ID, and the *saved* user ID. When a process executes a normal binary, all three IDs are set to the parent process's user ID. However, when a process executes a SUID binary, the process runs with the parent process's ID as its real ID, but it takes its effective ID and saved ID from the binary. (Analogously for the group ID for SGID binaries.) The function [`setresuid`(2)](../man2/getresuid.md) can change the real, effective, and saved user ID of a process -- but for non-root processes it is only valid to set each new ID to the current value of real, effective, or saved user ID. Since SUID binaries start with the binary's owner as effective and saved user ID and with the current user's ID as real user ID, this allows switching the effective user ID between the SUID owner's ID and the current user's ID. |