docs: various typos

Signed-off-by: Tim Deegan <tim@xen.org>
Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
Committed-by: Ian Jackson <ian.jackson.citrix.com>

4 files changed, 18 insertions, 18 deletions

diff --git a/docs/man/xl.cfg.pod.5 b/docs/man/xl.cfg.pod.5
index 5254358200..314a03e339 100644
--- a/docs/man/xl.cfg.pod.5
+++ b/docs/man/xl.cfg.pod.5
@@ -202,7 +202,7 @@ configuration
         
 =item B<rename-restart>
 
-rename the domain which terminated, and thenimmediately create a new
+rename the domain which terminated, and then immediately create a new
 domain with the same configuration as the original
 
 =item B<preserve>
@@ -357,7 +357,7 @@ guest B<DDDD> and B<BB> are C<0000:00>. XXX how does this really work?
 
 =item B<KEY=VALUE>
 
-Posible B<KEY>s are:
+Possible B<KEY>s are:
 
 =over 4
 
@@ -387,7 +387,7 @@ enable this option only for trusted VMs under administrator control.
 =item B<pci_permissive=BOOLEAN>
 
 (PV only) Changes the default value of 'permissive' for all PCI
-devices for this VM.  This can still be overriden on a per-device
+devices for this VM.  This can still be overridden on a per-device
 basis. This option should be enabled with caution: it gives the guest
 much more control over the device, which may have security or
 stability implications.  It is recommended to enable this option only
@@ -436,7 +436,7 @@ specific what meaning this has).
 =item B<e820_host=BOOLEAN>
 
 Selects whether to expose the host e820 (memory map) to the guest via
-the virtual e820. When this option is false the guest psuedo-physical
+the virtual e820. When this option is false the guest pseudo-physical
 address space consists of a single contiguous RAM region. When this
 option is specified the virtual e820 instead reflects the host e820
 and contains the same PCI holes. The total amount of RAM represented
@@ -446,10 +446,10 @@ it is layed out.
 Exposing the host e820 to the guest gives the guest kernel the
 opportunity to set aside the required part of its pseudo-physical
 address space in order to provide address space to map passedthrough
-PCI devices. It is guest Operaring System dependant whether this
+PCI devices. It is guest Operating System dependant whether this
 option is required, specifically it is required when using a mainline
 Linux ("pvops") kernel. This option defaults to true if any PCI
-passthrough devices are configued and false otherwise. If you do not
+passthrough devices are configured and false otherwise. If you do not
 configure any passthrough devices at domain creation time but expect
 to hotplug devices later then you should set this option. Conversely
 if your particular guest kernel does not require this behaviour then
@@ -580,7 +580,7 @@ has no effect on a guest with multiple virtual CPUS as they must
 always include these tables. This option is enabled by default and you
 should usually omit it but it may be necessary to disable these
 firmware tables when using certain older guest Operating
-Systems. These tables have been superceded by newer constructs within
+Systems. These tables have been superseded by newer constructs within
 the ACPI tables. (X86 only)
 
 =item B<nx=BOOLEAN>
@@ -763,7 +763,7 @@ Simple DirectMedia Layer). The default is not to enable this mode.
 =item B<opengl=BOOLEAN>
 
 Enable OpenGL acceleration of the SDL display. Only effects machines
-using B<device_model_version="qemu-xen-traditonal"> and only if the
+using B<device_model_version="qemu-xen-traditional"> and only if the
 device-model was compiled with OpenGL support. Disabled by default.
 
 =item B<nographic=BOOLEAN>
@@ -903,7 +903,7 @@ device-model will become the default in a future version of Xen.
 =back
 
 It is recommended to accept the default value for new guests.  If
-you have existing guests then, depeending on the nature of the guest
+you have existing guests then, depending on the nature of the guest
 Operating System, you may wish to force them to use the device
 model which they were installed with.
 
@@ -926,19 +926,19 @@ Assign an XSM security label to the device-model stubdomain.
 
 =item B<device_model_args=[ "ARG", "ARG", ...]>
 
-Pass additional arbitrary options on the devide-model command
+Pass additional arbitrary options on the device-model command
 line. Each element in the list is passed as an option to the
 device-model.
 
 =item B<device_model_args_pv=[ "ARG", "ARG", ...]>
 
-Pass additional arbitrary options on the devide-model command line for
+Pass additional arbitrary options on the device-model command line for
 a PV device model only. Each element in the list is passed as an
 option to the device-model.
 
 =item B<device_model_args_hvm=[ "ARG", "ARG", ...]>
 
-Pass additional arbitrary options on the devide-model command line for
+Pass additional arbitrary options on the device-model command line for
 an HVM device model only. Each element in the list is passed as an
 option to the device-model.
 
diff --git a/docs/man/xl.pod.1 b/docs/man/xl.pod.1
index 16f78e3651..c1ec1dacd8 100644
--- a/docs/man/xl.pod.1
+++ b/docs/man/xl.pod.1
@@ -50,7 +50,7 @@ setup the bridge.
 =item B<autoballoon>
 
 If you specify the amount of memory dom0 has, passing B<dom0_mem> to
-Xen, it is highly reccomended to disable B<autoballoon>. Edit
+Xen, it is highly recommended to disable B<autoballoon>. Edit
 B</etc/xen/xl.conf> and set it to 0.
 
 =item run xl as B<root>
@@ -808,7 +808,7 @@ the ratelimit (see below).
 
 Ratelimit attempts to limit the number of schedules per second.  It
 sets a minimum amount of time (in microseconds) a VM must run before
-we will allow a higher-prioirty VM to pre-empt it.  The default value
+we will allow a higher-priority VM to pre-empt it.  The default value
 is 1000 microseconds (1ms).  Valid range is 100 to 500000 (500ms).
 The ratelimit length must be lower than the timeslice length.
 
@@ -1233,7 +1233,7 @@ We need better documentation for:
 
 =item B<tmem>
 
-Trascendent Memory.
+Transcendent Memory.
 
 =back
 
diff --git a/docs/man/xm.pod.1 b/docs/man/xm.pod.1
index f9d2a0a983..69e1f519b3 100644
--- a/docs/man/xm.pod.1
+++ b/docs/man/xm.pod.1
@@ -117,7 +117,7 @@ on the command line are replaced by the values set in the script.
 
 =item B<-F=FILE>, B<--config=FILE>
 
-Use the given SXP formated configuration script.
+Use the given SXP formatted configuration script.
 SXP is the underlying configuration format used by Xen.
 SXP configuration scripts can be hand-written or generated
 from Python configuration scripts, using the -n
@@ -430,7 +430,7 @@ on the command line are replaced by the values set in the script.
 
 =item B<-F=FILE>, B<--config=FILE>
 
-Use the given SXP formated configuration script.
+Use the given SXP formatted configuration script.
 SXP is the underlying configuration format used by Xen.
 SXP configuration scripts can be hand-written or generated
 from Python configuration scripts, using the -n
diff --git a/docs/man/xmdomain.cfg.pod.5 b/docs/man/xmdomain.cfg.pod.5
index f4a8b79f13..99fca68e4e 100644
--- a/docs/man/xmdomain.cfg.pod.5
+++ b/docs/man/xmdomain.cfg.pod.5
@@ -53,7 +53,7 @@ xen kernel.
 The amount of RAM, in megabytes, to allocate to the domain when it
 starts.  Allocating insufficient memory for a domain may produce
 extremely bizarre behavior.  If there isn't enough free memory left on
-the machine to fulfill this request, the domain will fail to start.
+the machine to fulfil this request, the domain will fail to start.
 
 Xen does not support overcommit of memory, so the total memory of all
 guests (+ 64 MB needed for Xen) must be less than or equal to the