From: Aurelien Jarno <aurelien@aurel32.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] Fix some typo in the documentation
Date: Mon, 11 Dec 2006 01:19:37 +0100 [thread overview]
Message-ID: <20061211001937.GA4060@bode.aurel32.net> (raw)
The patch below fixes a few typos in the documentation.
Aurelien
Index: qemu-doc.texi
===================================================================
RCS file: /sources/qemu/qemu/qemu-doc.texi,v
retrieving revision 1.112
diff -u -d -p -r1.112 qemu-doc.texi
--- qemu-doc.texi 22 Oct 2006 00:18:54 -0000 1.112
+++ qemu-doc.texi 11 Dec 2006 00:18:00 -0000
@@ -443,7 +443,7 @@ or @file{C:\WINNT\SYSTEM32\DRIVERS\ETC\L
Then @file{dir} can be accessed in @file{\\smbserver\qemu}.
Note that a SAMBA server must be installed on the host OS in
-@file{/usr/sbin/smbd}. QEMU was tested succesfully with smbd version
+@file{/usr/sbin/smbd}. QEMU was tested successfully with smbd version
2.2.7a from the Red Hat 9 and version 3.0.10-1.fc3 from Fedora Core 3.
@item -redir [tcp|udp]:host-port:[guest-host]:guest-port
@@ -678,7 +678,7 @@ During emulation, if you are using the @
@item Ctrl-a h
Print this help
@item Ctrl-a x
-Exit emulatior
+Exit emulator
@item Ctrl-a s
Save disk data back to file (if -snapshot)
@item Ctrl-a b
@@ -1810,7 +1810,7 @@ to install QEMU in @file{/usr/local}.
@subsection Tested tool versions
-In order to compile QEMU succesfully, it is very important that you
+In order to compile QEMU successfully, it is very important that you
have the right tools. The most important one is gcc. I cannot guaranty
that QEMU works if you do not use a tested gcc version. Look at
'configure' and 'Makefile' if you want to make a different gcc
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' aurel32@debian.org | aurelien@aurel32.net
`- people.debian.org/~aurel32 | www.aurel32.net
reply other threads:[~2006-12-11 0:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20061211001937.GA4060@bode.aurel32.net \
--to=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.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).