docs: Fix typos.

Signed-off-by: Atsushi SAKAI <sakaia@jp.fujitsu.com>

2 files changed, 12 insertions, 12 deletions

diff --git a/docs/src/interface.tex b/docs/src/interface.tex
index a77d4e81c2..f1b8430709 100644
--- a/docs/src/interface.tex
+++ b/docs/src/interface.tex
@@ -1052,7 +1052,7 @@ This path contains:
       \end{description}
     \end{description}
 
-  \item[vtpm/] a directory containin vtpm backends
+  \item[vtpm/] a directory containing vtpm backends
     \begin{description}
     \item[$<$domid$>$/] a directory containing vtpm's for domid
       \begin{description}
@@ -1287,7 +1287,7 @@ ring.
 \subsection{Network ring interface}
 
 The network device uses two shared memory rings for communication: one
-for transmit, one for receieve.
+for transmit, one for receive.
 
 Transmit requests are described by the following structure:
 
@@ -1466,7 +1466,7 @@ The fields are as follows:
   interface
 \item[id] this value is echoed in the response message for this IO;
   the guest may use it to identify the original request
-\item[sector\_number] start sector on the virtal device for this
+\item[sector\_number] start sector on the virtual device for this
   request
 \item[frame\_and\_sects] This array contains structures encoding
   scatter-gather IO to be performed:
@@ -1483,7 +1483,7 @@ The fields are as follows:
 
 Virtual TPM (VTPM) support provides TPM functionality to each virtual
 machine that requests this functionality in its configuration file.
-The interface enables domains to access therr own private TPM like it
+The interface enables domains to access their own private TPM like it
 was a hardware TPM built into the machine.
 
 The virtual TPM interface is implemented as a split driver,
@@ -1504,11 +1504,11 @@ the backend can map the pages into its memory space using the grant
 table mechanism.
 
 The backend driver has been implemented to only accept well-formed
-TPM requests. To meet this requirement, the length inidicator in the
+TPM requests. To meet this requirement, the length indicator in the
 TPM request must correctly indicate the length of the request.
 Otherwise an error message is automatically sent back by the device driver.
 
-The virtual TPM implementation listenes for TPM request on /dev/vtpm. Since
+The virtual TPM implementation listens for TPM request on /dev/vtpm. Since
 it must be able to apply the TPM request packet to the virtual TPM instance
 associated with the virtual machine, a 4-byte virtual TPM instance
 identifier is prepended to each packet by the backend driver (in network
@@ -1536,7 +1536,7 @@ typedef struct {
 The fields are as follows:
 
 \begin{description}
-\item[addr] The machine address of the page asscoiated with the TPM
+\item[addr] The machine address of the page associated with the TPM
             request/response; a request/response may span multiple
             pages
 \item[ref]  The grant table reference associated with the address.
@@ -1982,7 +1982,7 @@ the value of {\bf op}).  The available operations are:
   stored.
 \item[XENMEM\_current\_reservation] Returns current memory reservation
   of the specified domain.
-\item[XENMEM\_maximum\_reservation] Returns maximum memory resrevation
+\item[XENMEM\_maximum\_reservation] Returns maximum memory reservation
   of the specified domain.
 \end{description}
 
diff --git a/docs/src/user.tex b/docs/src/user.tex
index 2ccbf8b87c..f4e23b8482 100644
--- a/docs/src/user.tex
+++ b/docs/src/user.tex
@@ -1683,7 +1683,7 @@ to:
     section remains to detail a configuration that was used by older Xen
     versions.}}
 
-Raw image file-backed VBDs amy also be attached to VMs using the 
+Raw image file-backed VBDs may also be attached to VMs using the 
 Linux loopback driver.  The only required change to the raw file 
 instructions above are to specify the configuration entry as:
 \begin{quote}
@@ -1694,7 +1694,7 @@ instructions above are to specify the configuration entry as:
   I/O-intensive domains.}  This approach is known to experience
 substantial slowdowns under heavy I/O workloads, due to the I/O
 handling by the loopback block device used to support file-backed VBDs
-in dom0.  Loopbach support remains for old Xen installations, and users
+in dom0.  Loopback support remains for old Xen installations, and users
 are strongly encouraged to use the blktap-based file support (using 
 ``{\tt{tap:aio}}'' as described above).
 
@@ -4203,7 +4203,7 @@ on the vnet UDP port:
 # tcpdump udp port 1798
 \end{verbatim}
 
-If multicast is not being forwaded between machines you can configure
+If multicast is not being forwarded between machines you can configure
 multicast forwarding using vn. Suppose we have machines hostA on 10.10.0.100
 and hostB on 10.11.0.100 and that multicast is not forwarded between them.
 We use vn to configure each machine to forward to the other:
@@ -4256,7 +4256,7 @@ as it will forward multicasts received from other machines on the subnet.
   VMMs} to provide the illusion of contiguous physical memory, in
   Xen this is used during {\bf live migration}.
 
-\item[Virtual Block Device] Persistant storage available to a virtual
+\item[Virtual Block Device] Persistent storage available to a virtual
   machine, providing the abstraction of an actual block storage device.
   {\bf VBD}s may be actual block devices, filesystem images, or
   remote/network storage.