about summary refs log tree commit diff
path: root/served/things/memoryleak
diff options
context:
space:
mode:
authorgennyble <gen@nyble.dev>2024-04-18 03:20:24 -0500
committergennyble <gen@nyble.dev>2024-04-18 03:20:24 -0500
commit94e22d26b12aae9176be05eaee2bc28f3e3286a4 (patch)
tree41c58d04641b1132a1f3c8c0ab0e5b7b8e386b01 /served/things/memoryleak
parent661a12f60710520c2d3e5e23de92a9b88d036a9d (diff)
download∞-94e22d26b12aae9176be05eaee2bc28f3e3286a4.tar.gz
∞-94e22d26b12aae9176be05eaee2bc28f3e3286a4.zip
Correct wording in memoryleak
Diffstat (limited to 'served/things/memoryleak')
-rw-r--r--served/things/memoryleak/memoryleak.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/served/things/memoryleak/memoryleak.html b/served/things/memoryleak/memoryleak.html
index 98a3d9c..d54c01c 100644
--- a/served/things/memoryleak/memoryleak.html
+++ b/served/things/memoryleak/memoryleak.html
@@ -20,7 +20,7 @@ random file, and then go back to sleep. It posted about it at
 
 	<p style="margin: 0">
 		It's face is a RAM module that I broke in half. I processed the raw photo
-		through my perpetually-in-process image processing project.
+		through my perpetually-in-progress image processing project.
 		I am very happy with how it came out! The split-and-<i>just</i>-peaking-open
 		memory chip is my favourite bit of it.</p>
 </section>