aboutsummaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorTest_User <hax@andrewyu.org>2024-11-30 14:04:06 -0500
committerTest_User <hax@andrewyu.org>2024-11-30 14:04:06 -0500
commiteed6baaea3e506a74db5ea4a1ece8fe56d72955f (patch)
tree6cabcea0c04704a6981bbf0420f7004a4001f660 /README.md
parentFix a typo, remove a wrong assertion, and write up a start for `nofail` (diff)
downloade2-spec-eed6baaea3e506a74db5ea4a1ece8fe56d72955f.tar.gz
e2-spec-eed6baaea3e506a74db5ea4a1ece8fe56d72955f.tar.zst
e2-spec-eed6baaea3e506a74db5ea4a1ece8fe56d72955f.zip
Fix a typo
Diffstat (limited to 'README.md')
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index 7211906..a849649 100644
--- a/README.md
+++ b/README.md
@@ -85,5 +85,5 @@ If such a case were to present itself, the compiler must make the caller fail
instead. This is recursive, and thus you cannot create a loop of `nofail` functions.
You may use `canfail` to be explicit about the reverse in function definitions,
or to override a function when calling it. In the latter case, if the function
-does not define a `onfail` section, you must wrap it in a `try {...} onfail {...}`
+does not define an `onfail` section, you must wrap it in a `try {...} onfail {...}`
block.