about summary refs log tree commit diff stats
diff options
context:
space:
mode:
authorKartik Agaram <vc@akkartik.com>2018-07-24 21:02:52 -0700
committerKartik Agaram <vc@akkartik.com>2018-07-24 21:02:52 -0700
commitdd0ad0c72b0ba022d0c0c08f15fb115d03a9f5bc (patch)
tree45be65b5d712a01f02f8ac88eaed4e60749bc1ea
parent1b35d4cd8bc9dce84fde4d0145d3058bca370350 (diff)
downloadmu-dd0ad0c72b0ba022d0c0c08f15fb115d03a9f5bc.tar.gz
4398
-rw-r--r--subx/011parse.cc2
1 files changed, 1 insertions, 1 deletions
diff --git a/subx/011parse.cc b/subx/011parse.cc
index 189f369d..3874e72f 100644
--- a/subx/011parse.cc
+++ b/subx/011parse.cc
@@ -5,7 +5,7 @@ put(Help, "syntax",
   "SubX programs consist of segments, each segment in turn consisting of lines.\n"
   "Line-endings are significant; each line should contain a single instruction, macro or directive.\n"
   "Comments start with the '#' character. It should be at the start of a word (start of line, or following a space).\n"
-  "Each segment starts with a header line: a '--' delimiter followed by the starting address for the segment.\n"
+  "Each segment starts with a header line: a '==' delimiter followed by the starting address for the segment.\n"
   "The starting address for a segment has some finicky requirements. But just start with a round number, and `subx` will try to guide you to a valid configuration.\n"
   "A good rule of thumb is to try to start the first segment at the default address of 0x08048000, and to start each subsequent segment at least 0x1000 (most common page size) bytes after the last.\n"
   "If a segment occupies than 0x1000 bytes you'll need to push subsequent segments further down.\n"