diff options
| author | Nico Weber <thakis@chromium.org> | 2021-09-30 19:55:37 -0400 |
|---|---|---|
| committer | Linus Groh <mail@linusgroh.de> | 2021-10-01 01:06:40 +0100 |
| commit | cd7ec294db8f0eb0f1d828c6c56331f32aa79015 (patch) | |
| tree | ac9f3766ca23a05ab8831a9e8718f702b4c27415 | |
| parent | 5a951d62580820def21bfe21d7f95768cfa09ccd (diff) | |
| download | serenity-cd7ec294db8f0eb0f1d828c6c56331f32aa79015.zip | |
Documentation: Fix grammar-o in ProcFSIndexing.md
| -rw-r--r-- | Documentation/Kernel/ProcFSIndexing.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/Kernel/ProcFSIndexing.md b/Documentation/Kernel/ProcFSIndexing.md index 8a2cf73a09..482de3ed79 100644 --- a/Documentation/Kernel/ProcFSIndexing.md +++ b/Documentation/Kernel/ProcFSIndexing.md @@ -25,8 +25,8 @@ effects of the disadvantages of each design. Since it was decided that heap allocations for ProcFS are *mostly* bad, the new design layout tries to achieve most of the principle of "Don't allocate anything -until actually needed". For that to happen, `InodeIndex` (u64 value) is splitted -to 3 Segments: +until actually needed". For that to happen, `InodeIndex` (u64 value) is split +into 3 Segments: - The primary segment: value 0 is reserved for all non-PID inodes in the procfs. All values from 1 to 0xFFFFFFF are valid PID indices, which represents all PIDs from 0 to 0xFFFFFFE |