From 4f63ee25bda2876e36d47d7a77747b2eeaaae202 Mon Sep 17 00:00:00 2001
From: liquidraver <504870+liquidraver@users.noreply.github.com>
Date: Fri, 16 Oct 2026 14:33:34 +0200
Subject: [PATCH] releasenotes update

---
 releasenotes/RELEASE_NOTES_1.18.0-zephcore.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/releasenotes/RELEASE_NOTES_1.18.0-zephcore.md b/releasenotes/RELEASE_NOTES_1.18.0-zephcore.md
index 61c4152..259c239 100644
--- a/releasenotes/RELEASE_NOTES_1.18.0-zephcore.md
+++ b/releasenotes/RELEASE_NOTES_1.18.0-zephcore.md
@@ -92,7 +92,7 @@ Thanks to **recrof** for the port.
 - **Acknowledgements on direct routes are relayed after a short random delay**, like other direct
   packets, and with `multi.acks 1` the two copies go out 300 ms apart. This means fewer lost
   acknowledgements.
-- **Floods with transport code 0 are treated as un-scoped.** Unlike upstream, ZephCore applies your
-  `flood.max.unscoped` and `region denyf *` settings to them.
+- **Floods with transport code 0 are un-scoped**, as in upstream 1.18.0. Unlike upstream, ZephCore
+  also applies your `flood.max.unscoped` and `region denyf *` settings to them. (because I don't really get it what is this transport code for, yet)
 - **Room server:** `set repeat on` now answers `ERR - repeat now deprecated`. A room server never
-  forwarded packets anyway.
+  forwarded packets by default anyway.