aboutsummaryrefslogtreecommitdiff
path: root/qemu-doc.texi
diff options
context:
space:
mode:
authorbellard <bellard@c046a42c-6fe2-441c-8c8c-71466251a162>2006-08-07 21:34:34 +0000
committerbellard <bellard@c046a42c-6fe2-441c-8c8c-71466251a162>2006-08-07 21:34:34 +0000
commit19d36792c02e09941d9f3ef19b9461306cc54d76 (patch)
tree22c2783568ea095e42acc3a9e3c6fcedf492f6ad /qemu-doc.texi
parent90765429aab64478e4dd9de3bbb21e5eafb5ead5 (diff)
update
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@2100 c046a42c-6fe2-441c-8c8c-71466251a162
Diffstat (limited to 'qemu-doc.texi')
-rw-r--r--qemu-doc.texi6
1 files changed, 3 insertions, 3 deletions
diff --git a/qemu-doc.texi b/qemu-doc.texi
index 9f0b4f68b4..8ff329a723 100644
--- a/qemu-doc.texi
+++ b/qemu-doc.texi
@@ -949,7 +949,7 @@ format. Normally this device is the first virtual hard drive.
Use the monitor command @code{savevm} to create a new VM snapshot or
replace an existing one. A human readable name can be assigned to each
-snapshots in addition to its numerical ID.
+snapshot in addition to its numerical ID.
Use @code{loadvm} to restore a VM snapshot and @code{delvm} to remove
a VM snapshot. @code{info snapshots} lists the available snapshots
@@ -972,8 +972,8 @@ and writable block device. The disk image snapshots are stored in
every disk image. The size of a snapshot in a disk image is difficult
to evaluate and is not shown by @code{info snapshots} because the
associated disk sectors are shared among all the snapshots to save
-disk space (otherwise each snapshot would have to copy the full disk
-images).
+disk space (otherwise each snapshot would need a full copy of all the
+disk images).
When using the (unrelated) @code{-snapshot} option
(@ref{disk_images_snapshot_mode}), you can always make VM snapshots,