public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: George Jones <gjones.dev@gmail.com>
To: linux-doc@vger.kernel.org
Cc: George Jones <gjones.dev@gmail.com>
Subject: [PATCH] doc: clarify wording for FlashPoint system ordering
Date: Wed,  1 Apr 2026 15:12:08 +0100	[thread overview]
Message-ID: <20260401141212.23955-2-gjones.dev@gmail.com> (raw)
In-Reply-To: <20260401141212.23955-1-gjones.dev@gmail.com>

Signed-off-by: George Jones <gjones.dev@gmail.com>
---
 Documentation/scsi/FlashPoint.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/scsi/FlashPoint.rst b/Documentation/scsi/FlashPoint.rst
index ef3c07e94ad6..292143a45e58 100644
--- a/Documentation/scsi/FlashPoint.rst
+++ b/Documentation/scsi/FlashPoint.rst
@@ -97,7 +97,7 @@ Contact:
 
   After this problem was identified, BusLogic contacted its major OEM
   customers to make sure the BT-946C/956C MultiMaster cards would still be
-  made available, and that Linux users who mistakenly ordered systems with
+  made available, and that Linux users who accidently ordered systems with
   the FlashPoint would be able to upgrade to the BT-946C.  While this helped
   many purchasers of new systems, it was only a partial solution to the
   overall problem of FlashPoint support for Linux users.  It did nothing to
-- 
2.43.0


  reply	other threads:[~2026-04-01 14:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-01 14:12 [PATCH] doc: clarify sisfb notes and fix minor wording issues George Jones
2026-04-01 14:12 ` George Jones [this message]
2026-04-01 14:12 ` [PATCH] doc: clarify wording for ntrig sensor disconnect behavior George Jones
2026-04-01 14:12 ` [PATCH] doc: fix typo in coding-style documentation (reformat) George Jones
2026-04-01 14:12 ` [PATCH] doc: fix typo in serial-console documentation George Jones

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=20260401141212.23955-2-gjones.dev@gmail.com \
    --to=gjones.dev@gmail.com \
    --cc=linux-doc@vger.kernel.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