From 7d231d60a6b969ffd7198ac90ff77f23f74d4281 Mon Sep 17 00:00:00 2001
From: Kugel Fuhr <98353208+kugelfuhr@users.noreply.github.com>
Date: Sun, 22 Jun 2025 12:15:33 +0200
Subject: [PATCH] Minor corrections after looking at the diff.

---
 src/da65/handler.c | 4 +---
 src/da65/labels.c  | 2 +-
 2 files changed, 2 insertions(+), 4 deletions(-)

diff --git a/src/da65/handler.c b/src/da65/handler.c
index 836dc2884..db55b4058 100644
--- a/src/da65/handler.c
+++ b/src/da65/handler.c
@@ -125,10 +125,8 @@ static const char* GetAddrArg (unsigned Flags, uint32_t Addr)
         static char Buf [32];
         if (Addr < 0x100) {
             xsprintf (Buf, sizeof (Buf), "$%02" PRIX32, Addr);
-        } else if (Addr < 0x10000) {
-            xsprintf (Buf, sizeof (Buf), "$%04" PRIX32, Addr);
         } else {
-            xsprintf (Buf, sizeof (Buf), "$%06" PRIX32, Addr);
+            xsprintf (Buf, sizeof (Buf), "$%04" PRIX32, Addr);
         }
         return Buf;
     }
diff --git a/src/da65/labels.c b/src/da65/labels.c
index 3a4cdd2d7..6f6bce3ed 100644
--- a/src/da65/labels.c
+++ b/src/da65/labels.c
@@ -507,7 +507,7 @@ void DefOutOfRangeLabels (void)
     ** sorted by address for better readability. This is not directly
     ** possible when using a hash table, so an intermediate data structure
     ** is required. It is not possible to collect out-of-range labels while
-    ** generating them, since they may come from an info file and where added
+    ** generating them, since they may come from an info file and are added
     ** while no input file was read. Which means it cannot be determined at
     ** that point if they're out-of-range or not.
     */