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>

9 files changed, 16 insertions, 16 deletions

diff --git a/docs/misc/distro_mapping.txt b/docs/misc/distro_mapping.txt
index 7f41b96474..f56e2814a7 100644
--- a/docs/misc/distro_mapping.txt
+++ b/docs/misc/distro_mapping.txt
@@ -22,6 +22,6 @@ one must grep for the above elements and add appropriate checks.
 
 For example if a new distro uses /etc/bork as its config dir, it's not
 sufficient to set CONFIG_LEAF_DIR=bork; one must also add tests for the
-existance of the bork dir in every context where config files are read.
+existence of the bork dir in every context where config files are read.
 
 
diff --git a/docs/misc/kexec_and_kdump.txt b/docs/misc/kexec_and_kdump.txt
index 06592196db..9ec3fcc784 100644
--- a/docs/misc/kexec_and_kdump.txt
+++ b/docs/misc/kexec_and_kdump.txt
@@ -3,8 +3,8 @@
 Kexec and Kdump for Xen
 =======================
 
-This is a breif guide to using Kexec and Kdump in conjunction with Xen.
-This functionaly works at the level of the hypervisor and dom0 kernel.
+This is a brief guide to using Kexec and Kdump in conjunction with Xen.
+This functionally works at the level of the hypervisor and dom0 kernel.
 And will thus affect all guests running on a machine.
 
 At this stage it does not work in conjunction with domU kernels.
@@ -33,7 +33,7 @@ Linux -> Xen   | first kernel       | second hypervisor &
 ---------------+--------------------+--------------------
 Linux -> Linux | first kernel       | second kernel
 
-If you are kexecing to Xen then you will also need to preapare the second
+If you are kexecing to Xen then you will also need to prepare the second
 hypervisor and dom0 kernel that will run after kexec. These may be the same
 as the first hypervisor and dom0 kernel that are used before kexec if you
 are kexecing from Xen to Xen.
@@ -176,7 +176,7 @@ running kernel.
 On x86 systems the crash kernel may be either
 - A uncompressed vmlinux image if the kernel is not relocatable
 - A compressed bzImage or vmlinuz image if the kernel is relocatable
-- Relocatability is crontroled by the CONFIG_RELOCATABLE kernel
+- Relocatability is controlled by the CONFIG_RELOCATABLE kernel
   compile configuration parameter. This option may not be available
   depending on the kernel version
 On ia64
diff --git a/docs/misc/tscmode.txt b/docs/misc/tscmode.txt
index 4f4d8f6132..e8c84e8004 100644
--- a/docs/misc/tscmode.txt
+++ b/docs/misc/tscmode.txt
@@ -121,7 +121,7 @@ may not remain) synchronized as "TSC-unsafe".
 
 As a result of TSC's sordid history, two classes of applications use
 TSC: old applications designed for single processors, and the most recent
-enteprise applications which require high-frequency high-precision
+enterprise applications which require high-frequency high-precision
 timestamping.
 
 We will refer to apps that might break if running on a TSC-unsafe
@@ -151,13 +151,13 @@ instructions to trap.  This trap can be detected by Xen, which can
 then transparently "emulate" the results of the rdtsc instruction and
 return control to the code following the rdtsc instruction.
 
-To provide a "safe" TSC, i.e. to ensure both TSC monontonicity and a
+To provide a "safe" TSC, i.e. to ensure both TSC monotonicity and a
 fixed rate, Xen provides rdtsc emulation whenever necessary or when
 explicitly specified by a per-VM configuration option.  TSC emulation is
 relatively slow -- roughly 15-20 times slower than the rdtsc instruction
 when executed natively.  However, except when an OS or application uses
 the rdtsc instruction at a high frequency (e.g. more than about 10,000 times
-per second per processor), this performance degradation is not noticable
+per second per processor), this performance degradation is not noticeable
 (i.e. <0.3%).  And, TSC emulation is nearly always faster than
 OS-provided alternatives (e.g. Linux's gettimeofday).  For environments
 where it is certain that all apps are TSC-resilient (e.g.
@@ -196,7 +196,7 @@ all apps running in this virtual machine.  This means that all
 apps must either be TSC-resilient or pvrdtscp-modified.  Second,
 highest performance is only obtained on TSC-safe machines that
 support the rdtscp instruction; when running on older machines,
-rdtscp is emulated and thus slower.  For more information on PVRTSCP,
+rdtscp is emulated and thus slower.  For more information on PVRDTSCP,
 see below.
 
 Finally, tsc_mode==1 always enables TSC emulation, regardless of
@@ -243,7 +243,7 @@ saved, restore this domain will fail.
 There is another cpuid-related complication: The x86 cpuid instruction is
 non-privileged.  HVM domains are configured to always trap this instruction
 to Xen, where Xen can "filter" the result.  In a PV OS, all cpuid instructions
-have been replaced by a parvirtualized equivalent of the cpuid instruction
+have been replaced by a paravirtualized equivalent of the cpuid instruction
 ("pvcpuid") and also trap to Xen.  But apps in a PV guest that use a
 cpuid instruction execute it directly, without a trap to Xen.  As a result,
 an app may directly examine the physical TSC Invariant cpuid bit and make
diff --git a/docs/misc/vtpm.txt b/docs/misc/vtpm.txt
index 9e34db5a4e..ad37fe8566 100644
--- a/docs/misc/vtpm.txt
+++ b/docs/misc/vtpm.txt
@@ -78,7 +78,7 @@ ramdisk = "/xen/initrd_domU/U1_ramdisk.img"
 memory = 32
 name = "TPMUserDomain0"
 vtpm = ['instance=1,backend=0']
-root = "/dev/ram0 cosole=tty ro"
+root = "/dev/ram0 console=tty ro"
 vif = ['backend=0']
 
 In the above configuration file the line 'vtpm = ...' provides
diff --git a/docs/misc/xen-command-line.markdown b/docs/misc/xen-command-line.markdown
index 7ceaa3b555..4c3be4a645 100644
--- a/docs/misc/xen-command-line.markdown
+++ b/docs/misc/xen-command-line.markdown
@@ -89,7 +89,7 @@ common, and only has an effect if your system is blacklisted.
 
 The `acpi=noirq` option causes Xen to not parse the ACPI MADT table
 looking for IO-APIC entries.  This is also not common, and any system
-which requries this option to function should be blacklisted.
+which requires this option to function should be blacklisted.
 Additionally, this will not prevent Xen from finding IO-APIC entries
 from the MP tables.
 
diff --git a/docs/misc/xenstore.txt b/docs/misc/xenstore.txt
index fa9de01ef0..c9f4a05317 100644
--- a/docs/misc/xenstore.txt
+++ b/docs/misc/xenstore.txt
@@ -202,7 +202,7 @@ WATCH			<wpath>|<token>|?
 	readable, some notifications may have been lost).
 
 WATCH_EVENT					<epath>|<token>|
-	Unsolicited `reply' generated for matching modfication events
+	Unsolicited `reply' generated for matching modification events
 	as described above.  req_id and tx_id are both 0.
 
 	<epath> is the event's path, ie the actual path that was
diff --git a/docs/misc/xl-disk-configuration.txt b/docs/misc/xl-disk-configuration.txt
index 91e0cc7284..3bf20bf968 100644
--- a/docs/misc/xl-disk-configuration.txt
+++ b/docs/misc/xl-disk-configuration.txt
@@ -72,7 +72,7 @@ Special syntax:
    syntax in the configuration file, it consumes the whole rest of the
    <diskspec>.  Therefore in that case it must come last.  This is
    permissible even if an empty value for the target was already
-   specifed as a positional parameter.  This is the only way to
+   specified as a positional parameter.  This is the only way to
    specify a target string containing metacharacters such as commas
    and (in some cases) colons, which would otherwise be
    misinterpreted.
diff --git a/docs/misc/xl-network-configuration.markdown b/docs/misc/xl-network-configuration.markdown
index b36d6c89c9..650926cb03 100644
--- a/docs/misc/xl-network-configuration.markdown
+++ b/docs/misc/xl-network-configuration.markdown
@@ -89,7 +89,7 @@ are:
 
   * `rtl8139` (default) -- Realtek RTL8139
   * `e1000` -- Intel E1000 
-  * in principal any device supported by your device model
+  * in principle any device supported by your device model
 
 ### vifname
 
diff --git a/docs/misc/xsm-flask.txt b/docs/misc/xsm-flask.txt
index e2e415d578..6b0d327ee5 100644
--- a/docs/misc/xsm-flask.txt
+++ b/docs/misc/xsm-flask.txt
@@ -226,7 +226,7 @@ Additional notes on XSM:FLASK
 	To boot the platform into enforcing mode, which means that the policy is
 	loaded and enforced, append 'flask_enforcing=1' on the grub line.
 	
-	This parameter may also be changed through the flask hyercall.
+	This parameter may also be changed through the flask hypercall.
 	
 	b) flask_enabled