From: Hongren Zheng <i@zenithal.me>
To: Stefan Weil <sw@weilnetz.de>
Cc: qemu-devel@nongnu.org, libvir-list@redhat.com,
"Canokeys . org" <contact@canokeys.org>,
qemu-trivial@nongnu.org
Subject: Re: [PATCH for-7.1?] Fix some typos in documentation (most of them found by codespell)
Date: Fri, 12 Aug 2022 16:37:41 +0800 [thread overview]
Message-ID: <YvYRVfwBDttg/Qj7@Sun> (raw)
In-Reply-To: <20220812075642.1200578-1-sw@weilnetz.de>
On Fri, Aug 12, 2022 at 09:56:42AM +0200, Stefan Weil wrote:
> diff --git a/docs/system/devices/canokey.rst b/docs/system/devices/canokey.rst
> index c2c58ae3e7..cfa6186e48 100644
> --- a/docs/system/devices/canokey.rst
> +++ b/docs/system/devices/canokey.rst
> @@ -28,9 +28,9 @@ With the same software configuration as a hardware key,
> the guest OS can use all the functionalities of a secure key as if
> there was actually an hardware key plugged in.
>
> -CanoKey QEMU provides much convenience for debuging:
> +CanoKey QEMU provides much convenience for debugging:
>
> -* libcanokey-qemu supports debuging output thus developers can
> +* libcanokey-qemu supports debugging output thus developers can
> inspect what happens inside a secure key
> * CanoKey QEMU supports trace event thus event
> * QEMU USB stack supports pcap thus USB packet between the guest
> @@ -102,8 +102,8 @@ and find CanoKey QEMU there:
>
> You may setup the key as guided in [6]_. The console for the key is at [7]_.
>
> -Debuging
> -========
> +Debugging
> +=========
>
> CanoKey QEMU consists of two parts, ``libcanokey-qemu.so`` and ``canokey.c``,
> the latter of which resides in QEMU. The former provides core functionality
Reviewed-by: Hongren (Zenithal) Zheng <i@zenithal.me>
next prev parent reply other threads:[~2022-08-12 8:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 7:56 [PATCH for-7.1?] Fix some typos in documentation (most of them found by codespell) Stefan Weil via
2022-08-12 8:37 ` Hongren Zheng [this message]
2022-08-12 10:15 ` Peter Maydell
2022-08-12 10:21 ` Peter Maydell
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=YvYRVfwBDttg/Qj7@Sun \
--to=i@zenithal.me \
--cc=contact@canokeys.org \
--cc=libvir-list@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=sw@weilnetz.de \
/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).