From fa118d01832234294bae7423267f18fa59de213c Mon Sep 17 00:00:00 2001
From: Athanasius <github@miggy.org>
Date: Tue, 21 Dec 2021 09:37:08 +0000
Subject: [PATCH] schemas/codexentry: Clarify that what unset
 `status_body_name` means

---
 schemas/codexentry-README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/schemas/codexentry-README.md b/schemas/codexentry-README.md
index 1f3725e..58da99e 100644
--- a/schemas/codexentry-README.md
+++ b/schemas/codexentry-README.md
@@ -64,7 +64,7 @@ release, Update 7, plus one patch).
    away.
 5. If Status.json does **not** have `BodyName` then clear `status_body_name`.
 6. For a `CodexEntry` event:
-    1. Check that `status_body_name` is set. If it is not, exit.
+    1. Only if `status_body_name` is set:
         1. Set the EDDN `codexentry` schema message `BodyName` to this value.
         2. Check if it matches the `journal_body_name` value, and 
            ONLY if they match, set `BodyID` in the EDDN `codexentry`
@@ -121,4 +121,4 @@ So you might receive any of:
 3. Both `BodyName` and `BodyID` keys present, with values.  This SHOULD 
    indicate a codex entry object which is on a body surface.
 
-Adjust your local processing accordingly.
\ No newline at end of file
+Adjust your local processing accordingly.