summaryrefslogtreecommitdiff
path: root/src/content/blog/2021/02/17/fallible.adoc
diff options
context:
space:
mode:
authorEuAndreh <eu@euandre.org>2025-04-01 06:09:08 -0300
committerEuAndreh <eu@euandre.org>2025-04-02 08:05:48 -0300
commitd5795ea791bd49a8ef30f1c00c811f3f4975770e (patch)
treeee8781f5231c0d66802322e5857e1690f7b2dacb /src/content/blog/2021/02/17/fallible.adoc
parentsrc/content/style.css: Add adjustment for asciidoc (diff)
downloadeuandre.org-d5795ea791bd49a8ef30f1c00c811f3f4975770e.tar.gz
euandre.org-d5795ea791bd49a8ef30f1c00c811f3f4975770e.tar.xz
src/content/: Tweak asciidoc leftovers
Diffstat (limited to 'src/content/blog/2021/02/17/fallible.adoc')
-rw-r--r--src/content/blog/2021/02/17/fallible.adoc2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/content/blog/2021/02/17/fallible.adoc b/src/content/blog/2021/02/17/fallible.adoc
index 533e107..e8dc8f6 100644
--- a/src/content/blog/2021/02/17/fallible.adoc
+++ b/src/content/blog/2021/02/17/fallible.adoc
@@ -133,7 +133,7 @@ my own code, but was still left with manually verifying the correctness and
robustness of it.
How could I add assertions around my code that would help me make sure the
-`free(s1);` exists, before getting an error report? How do other people and
+`free(s1);` exists, before getting an error report? How do other people and
projects solve this?
From what I could see, either people a) hope for the best, b) write safe code