Skip to content

fix typo: regaurdless -> regardless #20

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

Open
roemvaar wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix typo: regaurdless -> regardless #20

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
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -109,7 +109,7 @@ A few examples are provided that leverage the unique hardware aspects of the x86

## Grammar

The following grammar is accepted and compiled by sectorc:
The following grammar is accepted and compiled by SectorC:

```
program = (var_decl | func_decl)+
Expand All @@ -135,7 +135,7 @@ op = "+" | "-" | "&" | "|" | "^" | "<<" | ">>"

In addition, both `// comment` and `/* multi-line comment */` styles are supported.

(NOTE: This grammar is 704 bytes in ascii, 38% larger than it's implementation!)
(NOTE: This grammar is 704 bytes in ASCII, 38% larger than it's implementation!)

## How?

Expand All @@ -147,7 +147,7 @@ In 2020, cesarblum wrote a Forth that fits in a bootsector: ([sectorforth](https

In 2021, jart et. al. wrote a Lisp that fits in the bootsector: ([sectorlisp](https://github.com/jart/sectorlisp))

Naturally, C always needs to come and crash (literally) every low-level systems party regaurdless of whether it was even invited.
Naturally, C always needs to come and crash (literally) every low-level systems party, regardless of whether it was even invited.

## Running

Expand Down