From 155c77cecbb552348ac1d1268d1335368a192949 Mon Sep 17 00:00:00 2001
From: simon <simon@journeyman.cc>
Date: Wed, 5 Mar 2025 09:56:50 +0000
Subject: [PATCH] Update vector space

---
 vector-space.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/vector-space.md b/vector-space.md
index e87a591..1dcbb22 100644
--- a/vector-space.md
+++ b/vector-space.md
@@ -43,7 +43,7 @@ So the header now looks like this:
     | tag | vecp-pointer | size | mark | payload...          /
     +-----+--------------+------+------+--------------------+
 
-#### Alternative mark-bit strategy
+#### Alternative mark-bit strategy
 
 A thought which has recently occurred to me is that the mark bit could be the case bit of the least significant byte of the tag. So that if the tag read 'IMAG' (a raster image), for example, when marked it would read 'IMAg'. This saves having a separately allocated mark in the header, but retains debugging clarity.