aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorB. Watson <urchlay@slackware.uk>2024-12-24 16:09:29 -0500
committerB. Watson <urchlay@slackware.uk>2024-12-24 16:09:29 -0500
commit92e123ac0419a3388cda0001fb01efa9c2ccc1cf (patch)
tree789e480ba2ed219b2f00fbb4be19b0b148d3a99a
parent5c130e94e4366d38c6553e008973057a3ef9c8e5 (diff)
downloaduxd-92e123ac0419a3388cda0001fb01efa9c2ccc1cf.tar.gz
tweak man page
-rw-r--r--uxd.16
-rw-r--r--uxd.rst4
2 files changed, 5 insertions, 5 deletions
diff --git a/uxd.1 b/uxd.1
index d4917fd..86d186c 100644
--- a/uxd.1
+++ b/uxd.1
@@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
..
-.TH "UXD" 1 "2024-12-23" "0.3.0" "Urchlay's Utilities"
+.TH "UXD" 1 "2024-12-24" "0.3.0" "Urchlay's Utilities"
.SH NAME
uxd \- UTF-8 hex dumper
.SH SYNOPSIS
@@ -352,10 +352,10 @@ it, it will be a dash (so there\(aqll be two dashes: \fBc3\-\-b1\fP).
.sp
Since the output lines are always 16 hex bytes, multibyte characters
can span two lines. When this happens, the character itself will be
-printed on the first line, along with the first byte(s) on hex. The
+printed on the first line, along with the first byte(s) in hex. The
last hex byte will be followed by a dash, and the next line of hex
dump will have the remaining bytes (in the same color as the first
-bytes and character). This sounds complicated, but it\(aqs easy to
+byte(s) and character). This sounds complicated, but it\(aqs easy to
understand once you see it a few times.
.SH EXAMPLE
.sp
diff --git a/uxd.rst b/uxd.rst
index 0c95d31..65302c8 100644
--- a/uxd.rst
+++ b/uxd.rst
@@ -258,10 +258,10 @@ it, it will be a dash (so there'll be two dashes: **c3--b1**).
Since the output lines are always 16 hex bytes, multibyte characters
can span two lines. When this happens, the character itself will be
-printed on the first line, along with the first byte(s) on hex. The
+printed on the first line, along with the first byte(s) in hex. The
last hex byte will be followed by a dash, and the next line of hex
dump will have the remaining bytes (in the same color as the first
-bytes and character). This sounds complicated, but it's easy to
+byte(s) and character). This sounds complicated, but it's easy to
understand once you see it a few times.
EXAMPLE