Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Fixed typos #2840

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 13, 2025
+6 −6
Merged

Fixed typos #2840

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions Contributing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ have in mind is not how we'd expect it to be - talking to us
before you start might save you a lot of work in those cases.

(''Note:'' The word "must" indicates a requirement. The word
"should" indicates a recomendation.)
"should" indicates a recommendation.)

*this is work in progress and is constantly updated - if in
doubt, please ask*
Expand Down Expand Up @@ -54,7 +54,7 @@ This is an ongoing controversial topic - everyone knows
that. However, the following is how we do it :)

* TAB characters must be expanded to spaces.
* 4 spaces per indention level (rather than 8) are
* 4 spaces per indentation level (rather than 8) are
preferred, especially if there are many different levels.
* No extra spaces at the end of lines.
* All text files must end with new-line characters. Don't
Expand Down Expand Up @@ -262,9 +262,9 @@ conform with the C standard. That means:
.assert RETURN_VALUE = 0
tax

; Sometimes jumping to 'return 0' could save a byte:
; Sometimes jumping to 'return0' could save a byte:
.assert RETURN_VALUE = 0
jmp return 0
jmp return0
~~~

* Functions, that are intended for a platform's system
Expand Down Expand Up @@ -300,7 +300,7 @@ conform with the C standard. That means:
is on emulators or eg flash cartridges, the process of
converting them to something that can be used with these
should be documented in the user manual.
* Generally every function should live in a seperate source
* Generally every function should live in a separate source
file - unless the functions are so closely related that
splitting makes no sense.
* Source files should not contain commented out code - if
Expand Down Expand Up @@ -342,7 +342,7 @@ to the github actions - those may rely on bash and/or linux tools.
## Compiler

* We need a way that makes it possible to feed arbitrary
assembler code into the optimzer, so we can have proper
assembler code into the optimizer, so we can have proper
tests for it.

### Floating point support
Expand Down