9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Stuart Morrow <morrow.stuart@gmail.com>
To: 9front@9front.org
Subject: [9front] Re: small patches
Date: Mon, 19 Jul 2021 00:00:36 +0100	[thread overview]
Message-ID: <CABB-WO8nUog5pWh7SAEZN5DEOoxmy5qMEmLzfqkfiyGW722oGA@mail.gmail.com> (raw)
In-Reply-To: <CABB-WO-mdeCuH=Xy0v+sC4VZv7yya5=UusaT7AqXXAJofCPPZg@mail.gmail.com>

Better rio(4) diff than before.

"Stable device unique name" sounds like a violation of that rule about
the order in adjectives in English, although "device unique name"
appears elsewhere and so may be a technical term not to be rearranged.

Or perhaps I'm looking at a missing hyphen (stable device-unique name)
rather than wrong order. The order the words are already in would be
correct in this case.

inb4 device isn't an adjective

--- /mnt/git/object/be36c092ac061a04065720e98e5849130487be7f/tree/sys/man/4/rio
+++ sys/man/4/rio
@@ -225,7 +225,7 @@
 .B wctl
 accepts messages to change the size or placement of the associated window,
 and to create new windows.
-The messages are in a command-line like format, with a command name,
+The messages are in a command-line-like format, with a command name,
 possibly followed by options introduced by a minus sign.
 The options must be separated by blanks, for example
 .B -dx 100
@@ -276,14 +276,14 @@
 .B new
 commands accept
 .B -minx
-.IR n ,
+.RI [±] n ,
 .B -miny
-.IR n ,
+.RI [±] n ,
 .B -maxx
-.IR n ,
+.RI [±] n ,
 and
-.BR -maxy
-.I n
+.B -maxy
+.RI [±] n
 options to set the position of the corresponding edge of the window.
 They also accept an option
 .B -r
--- /mnt/git/object/be36c092ac061a04065720e98e5849130487be7f/tree/sys/man/4/nusb
+++ sys/man/4/nusb
@@ -88,7 +88,7 @@
 .B usbevent
 (usually seen as
 .BR /dev/usbevent )
-which, when read, returns a 6 column, space separated line of
+which, when read, returns a 6-column, space-separated line of
 text, one for each event. The columns are:
 .B attach
 or
@@ -99,7 +99,7 @@
 .I did
 .I csp
 and
-.I hname .
+.IR hname .
 The
 .I addr
 is the decimal device address assigned.
@@ -113,7 +113,7 @@
 .I Usbd
 assigns a stable device unique name based on the
 device descriptor for
-.I hname .
+.IR hname .
 This information is read by
 .IR nusbrc (8)
 and the
@@ -160,7 +160,7 @@
 .SS Ethernet
 .I Ether
 handles USB ethernet devices. The file system provided is
-compatible to
+compatible with
 .IR ether (3)
 and added to the share
 .B usbnet
@@ -234,7 +234,7 @@
 configures and manages a USB audio device.
 It implements a file system, (normally seen under
 .BI /dev )
-compatible to
+compatible with
 .IR audio (3).
 .SH SOURCE
 .B /sys/src/cmd/nusb

  reply	other threads:[~2021-07-19  8:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-13 17:41 [9front] " Stuart Morrow
2021-07-18 23:00 ` Stuart Morrow [this message]
2021-07-19  8:50   ` [9front] " Kurt H Maier
2021-07-19 12:06     ` Stuart Morrow
2021-07-19 19:40   ` Amavect
2021-07-19 19:52     ` ori
2021-07-21 21:19   ` Stuart Morrow
2021-07-21 21:20     ` Stuart Morrow

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CABB-WO8nUog5pWh7SAEZN5DEOoxmy5qMEmLzfqkfiyGW722oGA@mail.gmail.com \
    --to=morrow.stuart@gmail.com \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).