30.07.2023 21:03, Stefan Weil via wrote:
Signed-off-by: Stefan Weil <s...@weilnetz.de>
---

This patch was triggered by a spelling check for the generated
QEMU documentation using codespell. It does not try to fix all
typos which still exist in the QEMU code, but has a focus on
those required to fix the documentation. Nevertheless some code
comments with the same typos were fixed, too.

I think the patch is trivial, so maybe it can still be included
in the upcoming release, but that's not strictly necessary.

Stefan

  docs/about/deprecated.rst    | 2 +-
  docs/devel/qom.rst           | 2 +-
  docs/system/devices/nvme.rst | 2 +-
  hw/core/loader.c             | 4 ++--
  include/exec/memory.h        | 2 +-
  ui/vnc-enc-tight.c           | 2 +-
  6 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/docs/about/deprecated.rst b/docs/about/deprecated.rst
index 1c35f55666..92a2bafd2b 100644
--- a/docs/about/deprecated.rst
+++ b/docs/about/deprecated.rst
@@ -369,7 +369,7 @@ mapping permissions et al by using its 'mapped' security 
model option.
  Nowadays it would make sense to reimplement the ``proxy`` backend by using
  QEMU's ``vhost`` feature, which would eliminate the high latency costs under
  which the 9p ``proxy`` backend currently suffers. However as of to date nobody
-has indicated plans for such kind of reimplemention unfortunately.
+has indicated plans for such kind of reimplementation unfortunately.

FWIW, all these changes has been included in my "tree-wide spelling" series.
This particular change:
 https://lists.nongnu.org/archive/html/qemu-devel/2023-07/msg03011.html

/mjt

Reply via email to