Skip to content

[FIX] Grammar and Consistency#95

Closed
Sir-NoChill wants to merge 5 commits into
masterfrom
spec/grammar-and-consistency
Closed

[FIX] Grammar and Consistency#95
Sir-NoChill wants to merge 5 commits into
masterfrom
spec/grammar-and-consistency

Conversation

@Sir-NoChill

Copy link
Copy Markdown
Collaborator

Some small fixes while I go through the spec. These are pulled out of my other PR.

Correct ~20 single-word spelling/grammar errors across the spec and impl prose
(e.g. writting->writing, preceeding->preceding, undecideable->undecidable,
accomodate->accommodate, propogation->propagation, be reference->by reference).
Also align two terminology slips with the surrounding text: refer to
stream_state as a procedure (it is declared as one) and to the struct type as
Another (its declared name). No semantic changes.
Correct mistakes in example snippets that would mislead readers: the tuple type
in errors.rst (integerm integer -> integer, integer), an undefined identifier in
string.rst (carry -> carray), a run-on comment (Run-timeerror -> Runtime error),
and an erroneously escaped block-comment terminator in matrix.rst (\*/ -> */).
Demote two headings that were marked at the wrong level: the Variable
Declarations subsection in globals.rst was underlined as a top-level title
(same as the page heading), and Syntax Errors in errors.rst used a deeper
underline than its sibling category Compile-time Errors. Both are now
second-level headings, matching the surrounding structure.
Use the canonical bracket-chained form everywhere for 2D types and indexing,
matching the rest of the matrix documentation: integer[3,3] -> integer[3][3]
(expressions), real[3,3] -> real[3][3] (functions), and the M[1, 2] index
comment -> M[1][2] (matrix). The comma form was used in only these three places
and is inconsistent with the [*][*] / M[i][j] notation defined elsewhere.
Resolve three dangling references. The ssec:errors_sizeErrors label is never
defined anywhere in the spec, so remove the two sentences that point to it (in
array.rst and errors.rst); the surrounding text already states that SizeError
may be raised at compile time or run time. Fill in the empty reference in
type_promotion.rst to point at the type-casting section (sec:typeCasting),
which defines the conversion semantics being referred to.
@Sir-NoChill Sir-NoChill requested review from novo52 and rcunrau June 22, 2026 17:25
@Sir-NoChill Sir-NoChill changed the title [Fix] Grammar and Consistency [FIX] Grammar and Consistency Jun 22, 2026
@Sir-NoChill

Copy link
Copy Markdown
Collaborator Author

Note that there are some duplicates from @novo52 in the 2026 changes, I'll cherry pick that commit and put it on here so that we can get things moving.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant