Skip to content

Commit c702c0d

Browse files
authored
Import textual fixes from fd-nls [closes #174] (#175)
Part of patch ~~~ commit 01c4ad0a496797e74fccee2e5ae61244f8e4e641 Author: Sebastian Rasmussen <sebras@gmail.com> Date: Thu Apr 10 00:21:02 2025 +0200 Fix typos in the original English files for many projects. ~~~
1 parent c78b0a9 commit c702c0d

File tree

2 files changed

+7
-7
lines changed

2 files changed

+7
-7
lines changed

strings/DEFAULT.err

+1-1
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@
3636
#
3737
# The individual words are defined by ABORT, IGNORE, RETRY, FAIL. They
3838
# should indicate which user response keys is associated with them;
39-
# suggested is to use the first letter and enclose it in parenthesises.
39+
# suggested is to use the first letter and enclose it in parentheses.
4040
# The delimiter ", " can be defined with DELIMITER and is the same
4141
# for all slots.
4242
# The "? " sequence is defined by QUESTION.

strings/DEFAULT.lng

+6-6
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@
1515
# outputs. This file is the input to the fixstrs program, and it
1616
# outputs strings.h and strings.dat. The .DAT file is appended to
1717
# the command.exe file, and then renamed to command.com. The .H
18-
# file contains all the info for the program to retreive the
18+
# file contains all the info for the program to retrieve the
1919
# messages.
2020
#
2121
# The format of this file is simple. Blank lines and lines starting
@@ -35,7 +35,7 @@
3535
#
3636
# All lines after the label are the message until a line with a
3737
# single "." or "," in the first column. The difference is the
38-
# period (".") signifies that there will be a final carrage return when
38+
# period (".") signifies that there will be a final carriage return when
3939
# the message is displayed, but a comma does not.
4040
#
4141
# The body may contain backslash escape sequences as known from C; there
@@ -55,7 +55,7 @@
5555

5656
# Defining prompts
5757
# Some prompts may cause an user interaction. Those ones should be in sync
58-
# with the issued text. To define how to interprete a pressed key, they
58+
# with the issued text. To define how to interpret a pressed key, they
5959
# are mapped into metakeys like that: [ignore first hash sign]
6060

6161
## Return value: a -> Yes; else -> No
@@ -67,9 +67,9 @@
6767

6868
# All strings, which label start with "PROMPT_", are parsed as prompts.
6969
# The first two lines of the body are special; the first one enumerates all
70-
# valid keys, the second one assigns arbitary metakeys. Metakeys may
70+
# valid keys, the second one assigns arbitrary metakeys. Metakeys may
7171
# range from 'a' through 'z'; spaces are ignored; everything else cause
72-
# an error. The comment preceeding the prompt definition associates the
72+
# an error. The comment preceding the prompt definition associates the
7373
# metakeys with their meaning.
7474
# The remaining lines of the body contain the text to be displayed.
7575
#
@@ -80,7 +80,7 @@
8080
# 'N', 'n', Enter and ^Break are mapped to metakey 'b' (aka No).
8181
# The spaces between the 'b's in the second line had been inserted to
8282
# align them with the corresponding keys of the first line, hence in order
83-
# to enhance readibility of the association between the pressed keys and their
83+
# to enhance readability of the association between the pressed keys and their
8484
# mapping into a metakey.
8585
#
8686
# The first line (pressed keys) has to enumerate the ASCII value as returned

0 commit comments

Comments
 (0)