commit f4b8b799484efe1f88a8844f02579b9353c04fbc
parent 00d7809c4721f982e5dfabd3b12fd24399042c30
Author: Arcade Wise <l3gacy.b3ta@disroot.org>
Date: Sun, 2 Oct 2022 14:51:25 -0400
Spelling fixes
Signed-off-by: Arcade Wise <l3gacy.b3ta@disroot.org>
Diffstat:
5 files changed, 10 insertions(+), 11 deletions(-)
diff --git a/fs/doc/dict.txt b/fs/doc/dict.txt
@@ -45,8 +45,7 @@ indicating a special attribute:
## Symbols
Across words, different symbols are used in different contexts,
-but we try to be consistent in their use. Here's their defini-
-tions:
+but we try to be consistent in their use. Here's their definitions:
! - Store
@ - Fetch
diff --git a/fs/doc/file.txt b/fs/doc/file.txt
@@ -172,5 +172,5 @@ that this ID scheme could only address 64GB volumes.
This would mean that the File API would be broken on a subset of filesystems.
Does it mean that Dusk couldn't read them? No, only that file/dir enumeration
-would have to go through FS-specific tools. I think that this incovenience is
+would have to go through FS-specific tools. I think that this inconvenience is
worth it if it means an overall simpler API.
diff --git a/fs/doc/usage.txt b/fs/doc/usage.txt
@@ -151,7 +151,7 @@ levels (they always need to stay balanced, of course), but it can happen. For
example, in early "exit" paths, we often have to include a few "rdrop" before
the "exit" call. This messes up the "R counter". You can manually adjust it
through the [rcnt] variable. For example, if you want your next ">r" to push to
-V1, you would preceed it with:
+V1, you would precede it with:
[ 0 [rcnt] ! ]
@@ -175,7 +175,7 @@ But there's more! "to" semantics are built upon those words, so we'd need to add
a "c" and "w" variant to all "to" words too? That's heavy.
To make things lighter, Dusk has "8b" and "16b" modulator words. A memory word,
-when preceeded by one of these modulator word, will execute its 8-bit or 16-bit
+when preceded by one of these modulator word, will execute its 8-bit or 16-bit
variant. These words are immediate and work during compilation too.
Better yet: the choice of variant is applied at compile time, which means that
@@ -270,7 +270,7 @@ You will often want to bind data to structs. You can do so with "structbind":
someword . \ prints 2
When a structbind is compiled, it is so with a level of indirection that allows
-it to be rebinded. So, you can rebind structbinds and this is done with the word
+it to be rebound. So, you can rebind structbinds and this is done with the word
"rebind" (we can't use "to" because it applies to the bind's field):
data2 ' MyData1 rebind
@@ -333,11 +333,11 @@ structures in them. These structures simply plug themselves in "key" and
"emit".
From that point on, the system interpret loop feeds itself from "stdin". "emit"
-and "stdout" becomes synonymous, the latter being prefered. "emit" becomes the
+and "stdout" becomes synonymous, the latter being preferred. "emit" becomes the
"console only" output word and "stdout" is the "generally console, but
redirectable output" word.
The basic Dusk console, the sys/rdln subsystem, inserts itself between "key" and
-"stdin". It feeds itself from key and provides line editing capabilitites. When
-a whole line is ready to be interpeted, it is fed to stdin.
+"stdin". It feeds itself from key and provides line editing capabilities. When
+a whole line is ready to be interpreted, it is fed to stdin.
diff --git a/fs/doc/value.txt b/fs/doc/value.txt
@@ -4,7 +4,7 @@ There are several words that are used to define other words, such as
":" and "code", but the three that will be explained here are
"create", "value", and "alias".
-create is mostly straitforward, it defines a word that pushes an
+create is mostly straightforward, it defines a word that pushes an
address to the stack. The address that it pushes is the same as the
one returned by "here" after the word is defined. To use this to
store a cell-sized value (4 bytes), you would to something like this:
diff --git a/fs/doc/x86.txt b/fs/doc/x86.txt
@@ -39,7 +39,7 @@ PS lives at the end of x86 conventional memory, that is $80000.
RS lives at $7c00. The idea is that it lives below the $10000 line so that we
don't have to save/restore ESP when doing the int13h call in real mode. If we
-have it live over this line, the 64K wrapup makes int13h push to unexpected
+have it live over this line, the 64K wrap-up makes int13h push to unexpected
places in memory.
The bootloader is loaded at $7c00, and it then loads the kernel along with its
