From 973fbc267b0cbe538f3dcd2b066d183048f72f0b Mon Sep 17 00:00:00 2001
From: Sander Bos <32989873+MyNameIsTrez@users.noreply.github.com>
Date: Mon, 17 Feb 2025 00:37:30 +0100
Subject: [PATCH] Update 2024-02-29-creating-the-perfect-modding-language.md

---
 _posts/2024-02-29-creating-the-perfect-modding-language.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_posts/2024-02-29-creating-the-perfect-modding-language.md b/_posts/2024-02-29-creating-the-perfect-modding-language.md
index a8980c6..0a449a5 100644
--- a/_posts/2024-02-29-creating-the-perfect-modding-language.md
+++ b/_posts/2024-02-29-creating-the-perfect-modding-language.md
@@ -86,7 +86,7 @@ In this video, look at the console at the bottom of the game for these grug runt
 
 <video src="https://github.com/user-attachments/assets/3e9ae8ff-8e34-4d9f-90e6-f56ef909bc1a" width="100%" autoplay controls loop muted></video>
 
-The remaining possible runtime errors are for integer overflow/underflow with addition/subtraction/negation/multiplication/division.
+The remaining possible runtime errors are for integer overflow/underflow with the addition, subtraction, negation, multiplication, division and remainder operators.
 
 If you're curious *how* grug catches runtime errors, [I wrote a post]({{ site.baseurl }} {% link _posts/2024-11-01-how-grug-used-to-catch-runtime-errors.md %}) about the old implementation that used signal handlers.