9front - general discussion about 9front
 help / color / mirror / Atom feed
From: igor@9lab.org
To: 9front@9front.org
Cc: igor@9lab.org
Subject: [9front] nusbrc(8) patch
Date: Fri, 18 Jun 2021 23:20:42 +0200	[thread overview]
Message-ID: <D3F26BB2F8A6B11124F54DC855A0827E@9lab.org> (raw)

Spotted two small typos while reading nusbrc(8):

term% git/diff /sys/man/8/nusbrc 
--- //.git/fs/object/b3215c807556cdaaa0f949f1fb3f97c484ffd1da/tree//sys/man/8/nusbrc
+++ /sys/man/8/nusbrc
@@ -31,5 +31,5 @@
 identified by the devices unique name assigned by usbd.
 When the environment variable
 .I nousbhname
-is defined, devies are named by ther dynamically assigned
+is defined, devices are named by their dynamically assigned
 usb device address instead. This emulates the old behaviour.


             reply	other threads:[~2021-06-19  5:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-18 21:20 igor [this message]
2021-06-19 10:45 ` Alex Musolino
2021-06-19 16:19   ` ori
2021-06-20  2:02     ` Alex Musolino
2021-06-19 12:04 ` kvik

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=D3F26BB2F8A6B11124F54DC855A0827E@9lab.org \
    --to=igor@9lab.org \
    --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).