From 1fd8fc8b4e3e325b389c67deede3d2c8e696f1c8 Mon Sep 17 00:00:00 2001
From: Wolfgang Müller
Date: Wed, 2 Oct 2024 19:42:18 +0200
Subject: content: Clarify relocation sections in post 23

---
 content/23/index.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

(limited to 'content/23')

diff --git a/content/23/index.md b/content/23/index.md
index 9699334..442f383 100644
--- a/content/23/index.md
+++ b/content/23/index.md
@@ -76,12 +76,12 @@ Already pretty out of my depth considering the fact that I couldn't fathom how
 `fd(1)` got musl to segfault on `memcpy`, I now also found that a piece of the
 puzzle required me to understand specific linker flags. *Oof.*
 
-Unsure what to do next I decided on a whim to compare the working and the broken
-binary with `readelf(1)`. The most obvious difference was that the working
-binary had its `.rela.dyn`
+Unsure what to do next I decided on a whim to compare the working and the
+broken binary with `readelf(1)`. The most obvious difference was that the
+working binary had its `.rela.dyn`
 [relocation](https://en.wikipedia.org/wiki/Relocation_(computing)) section
-populated with entries whilst the broken one's didn't seem filled out. At a
-loss, I stopped and went to do something else.
+populated with entries whilst the broken one was missing `.rela.dyn` but had
+`.relr.dyn` instead. At a loss, I stopped and went to do something else.
 
 The story would probably have ended here had I not mentioned this conundrum to
 [my partner](https://ahti.space/~nortti/) later in the day. We decided to have
-- 
cgit v1.2.3-2-gb3c3