[3.9] Fix typos in the Tools directory (GH-28769) (GH-28800)

Like #28744 but for the Tools directory.

Automerge-Triggered-By: GH:pablogsal
(cherry picked from commit 682aecfdeba481c876bfc9f3796c635bd5b5df50)
This commit is contained in:
Christian Clauss 2021-10-07 17:31:24 +02:00 committed by GitHub
parent 78efc9aff2
commit da56601783
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
5 changed files with 5 additions and 5 deletions

View File

@ -685,7 +685,7 @@ class CParserGenerator(ParserGenerator, GrammarVisitor):
self.print(
f'D(fprintf(stderr, "%*c+ {rulename}[%d-%d]: %s succeeded!\\n", p->level, \' \', _mark, p->mark, "{node_str}"));'
)
# Prepare to emmit the rule action and do so
# Prepare to emit the rule action and do so
if node.action and "EXTRA" in node.action:
self._set_up_token_end_metadata_extraction()
if self.skip_actions:

View File

@ -59,7 +59,7 @@ class FirstSetCalculator(GrammarVisitor):
result -= to_remove
# If the set of new terminals can start with the empty string,
# it means that the item is completelly nullable and we should
# it means that the item is completely nullable and we should
# also considering at least the next item in case the current
# one fails to parse.

View File

@ -72,7 +72,7 @@ def main() -> None:
package_json = load_json(package_name)
try:
print(f"Dowloading and compressing package {package_name} ... ", end="")
print(f"Downloading and compressing package {package_name} ... ", end="")
download_package_code(package_name, package_json)
print("Done")
except (IndexError, KeyError):

View File

@ -9,7 +9,7 @@ format of the file is. If it can't figure out the file format, or it has
trouble reading the file, None is returned. You can pass get_colordb() an
optional filetype argument.
Supporte file types are:
Supported file types are:
X_RGB_TXT -- X Consortium rgb.txt format files. Three columns of numbers
from 0 .. 255 separated by whitespace. Arbitrary trailing

View File

@ -15,7 +15,7 @@ From the keyboard of flee@cs.psu.edu (Felix Lee):
:And Perl is definitely awkward with data types. I haven't yet found a
:pleasant way of shoving non-trivial data types into Perl's grammar.
Yes, it's pretty aweful at that, alright. Sometimes I write perl programs
Yes, it's pretty awful at that, alright. Sometimes I write perl programs
that need them, and sometimes it just takes a little creativity. But
sometimes it's not worth it. I actually wrote a C program the other day
(gasp) because I didn't want to deal with a game matrix with six links per node.