# HG changeset patch
# User Keir Fraser <keir.fraser@xxxxxxxxxx>
# Date 1207218861 -3600
# Node ID a2903704c17af6f44070ded1a50e29455b403e00
# Parent 522f64fbb8bf44bc8820c6c86dacc904d41a53cf
docs: Fix typos.
Signed-off-by: Atsushi SAKAI <sakaia@xxxxxxxxxxxxxx>
---
docs/misc/VMX_changes.txt | 2 +-
docs/misc/hg-cheatsheet.txt | 14 +++++++-------
docs/misc/vtpm.txt | 2 +-
docs/misc/xenstore.txt | 3 ++-
docs/src/interface.tex | 10 +++++-----
docs/src/user.tex | 4 ++--
docs/xen-api/presentation.tex | 2 +-
docs/xen-api/todo.tex | 2 +-
docs/xen-api/wire-protocol.tex | 6 +++---
docs/xen-api/xenapi-datamodel.tex | 6 +++---
10 files changed, 26 insertions(+), 25 deletions(-)
diff -r 522f64fbb8bf -r a2903704c17a docs/misc/VMX_changes.txt
--- a/docs/misc/VMX_changes.txt Thu Apr 03 11:33:10 2008 +0100
+++ b/docs/misc/VMX_changes.txt Thu Apr 03 11:34:21 2008 +0100
@@ -79,7 +79,7 @@ Changes to the existing code:
* include/asm-x86/processor.h: struct arch_vmx_struct arch_vmx has
been added to the thread_struct data structure. The arch_vmx has
- the addtional VMX-related CPU context.
+ the additional VMX-related CPU context.
* arch/x86/io_apic.c: reverse mapping between vector and irq has
been added. We will revisit this code when considering MSI
diff -r 522f64fbb8bf -r a2903704c17a docs/misc/hg-cheatsheet.txt
--- a/docs/misc/hg-cheatsheet.txt Thu Apr 03 11:33:10 2008 +0100
+++ b/docs/misc/hg-cheatsheet.txt Thu Apr 03 11:34:21 2008 +0100
@@ -12,7 +12,7 @@ running with the new tools as quickly as
running with the new tools as quickly as possible, and is written from
the perspective of someone who has been using BK.
-For a more detailed exposition, see the mecurial tutorial:
+For a more detailed exposition, see the mercurial tutorial:
http://www.serpentine.com/mercurial/index.cgi?Tutorial
The Hg manpage is available at:
@@ -69,7 +69,7 @@ actually pretty neat. For example, it wo
actually pretty neat. For example, it would in principle enable you to
have both the 2.0-testing and unstable trees in a single
repository. We shyed away from doing this as we thought the risk of
-commiting to the wrong head was too great.
+committing to the wrong head was too great.
One slightly confusing aspect of Hg is that many of the commands have
aliases, and hence when looking things up in the man page its not
@@ -81,7 +81,7 @@ Getting Xen
Getting Xen
-----------
-The URL for the mainline Xen mercurial respository is:
+The URL for the mainline Xen mercurial repository is:
http://xenbits.xensource.com/xen-unstable.hg
(similarly for xen-2.0 and xen-2.0-testing)
@@ -273,9 +273,9 @@ Pushing changesets to a parent repositor
Pushes changes up to a parent. You can't push if you pulled the
repository off the web interface. In fact, you can currently only push
-to an ssh target -- filesystem drectory targets don't work, but this
+to an ssh target -- filesystem directory targets don't work, but this
will be fixed soon.
-For now it is possible to set up assymetric pull/push paths. Pulls can
+For now it is possible to set up asymmetric pull/push paths. Pulls can
be done via web interface while pushes via ssh. Example of .hg/hgrc config
file:
| [paths]
@@ -332,7 +332,7 @@ system. Hg will probably get fixed soon,
system. Hg will probably get fixed soon, but in the meantime you can
cleanup with "find -depth -type d -print | xargs -r rmdir".
-You can return to the tip by ommiting an explicit changeset id.
+You can return to the tip by omitting an explicit changeset id.
The manifest command lets you see the contents of the repository for
the current changeset.
@@ -347,7 +347,7 @@ This will print a bunch of records of th
| 7fc869aae2945a9f4626fad96552db3103e61cb9 644 README
| ...
-This lists the hash of each file, its 1-bit 'executable' atribute
+This lists the hash of each file, its 1-bit 'executable' attribute
(either file permission mode 644 or 755), and the file name. So, to
determine the files that change across two changesets, you would dump
the respective manifests to files, and use diff.
diff -r 522f64fbb8bf -r a2903704c17a docs/misc/vtpm.txt
--- a/docs/misc/vtpm.txt Thu Apr 03 11:33:10 2008 +0100
+++ b/docs/misc/vtpm.txt Thu Apr 03 11:34:21 2008 +0100
@@ -143,7 +143,7 @@ PCR-08: 00 00 00 00 00 00 00 00 00 00 00
PCR-08: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[...]
-At this point the user domain has been sucessfully connected to its
+At this point the user domain has been successfully connected to its
virtual TPM instance.
For further information please read the documentation in
diff -r 522f64fbb8bf -r a2903704c17a docs/misc/xenstore.txt
--- a/docs/misc/xenstore.txt Thu Apr 03 11:33:10 2008 +0100
+++ b/docs/misc/xenstore.txt Thu Apr 03 11:34:21 2008 +0100
@@ -129,7 +129,7 @@ reply payloads as applicable:
reply payloads as applicable:
----------- Database read, write and permissions operatons ----------
+---------- Database read, write and permissions operations ----------
READ <path>| <value|>
WRITE <path>|<value|>
@@ -206,7 +206,7 @@ WATCH_EVENT <epath>|<token>|
as described above. req_id and tx_id are both 0.
<epath> is the event's path, ie the actual path that was
- modifed; however if the event was the recursive removal of an
+ modified; however if the event was the recursive removal of an
parent of <wpath>, <epath> is just
<wpath> (rather than the actual path which was removed). So
<epath> is a child of <wpath>, regardless.
diff -r 522f64fbb8bf -r a2903704c17a docs/src/interface.tex
--- a/docs/src/interface.tex Thu Apr 03 11:33:10 2008 +0100
+++ b/docs/src/interface.tex Thu Apr 03 11:34:21 2008 +0100
@@ -470,7 +470,7 @@ typedef struct shared_info {
* are delivered by this mechanism:
* 1. Bi-directional inter- and intra-domain connections. Domains must
* arrange out-of-band to set up a connection (usually by allocating
- * an unbound 'listener' port and avertising that via a storage service
+ * an unbound 'listener' port and advertising that via a storage
service
* such as xenstore).
* 2. Physical interrupts. A domain with suitable hardware-access
* privileges can bind an event-channel port to a physical interrupt
@@ -915,7 +915,7 @@ These activities include:
(e.g. performance-related statistics, etc).
\end{itemize}
-The store is arranged as a hierachical collection of key-value pairs.
+The store is arranged as a hierarchical collection of key-value pairs.
Each domain has a directory hierarchy containing data related to its
configuration. Domains are permitted to register for notifications
about changes in subtrees of the store, and to apply changes to the
@@ -1114,9 +1114,9 @@ This path contains:
\end{description}
\end{description}
- \item[device-misc/] miscellanous information for devices
+ \item[device-misc/] miscellaneous information for devices
\begin{description}
- \item[vif/] miscellanous information for vif devices
+ \item[vif/] miscellaneous information for vif devices
\begin{description}
\item[nextDeviceID] the next device id to use
\end{description}
@@ -1511,7 +1511,7 @@ The virtual TPM implementation listens f
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
+identifier is pretended to each packet by the backend driver (in network
byte order) for internal routing of the request.
\subsection{Virtual TPM ring interface}
diff -r 522f64fbb8bf -r a2903704c17a docs/src/user.tex
--- a/docs/src/user.tex Thu Apr 03 11:33:10 2008 +0100
+++ b/docs/src/user.tex Thu Apr 03 11:34:21 2008 +0100
@@ -3394,7 +3394,7 @@ Alternatively, a system that has two har
Alternatively, a system that has two hard-drives does not need a VIO
domain but can directly assign one hardware storage device to each of
the workloads if the platform offers an IO-MMU, cf
-Section~\ref{s:ddsecurity}. Sharing hardware through virtualizated devices
+Section~\ref{s:ddsecurity}. Sharing hardware through virtualized devices
is a trade-off between the amount of trusted code (size of the trusted
computing base) and the amount of acceptable over-provisioning. This
holds both for peripherals and for system platforms.
@@ -4652,7 +4652,7 @@ answering the questions as follows:
\begin{enumerate}
\item When the program asks for \textbf{model},
-scroll down and selese \textbf{SummaSketch (MM Compatible)}.
+scroll down and select \textbf{SummaSketch (MM Compatible)}.
\item When the program asks for \textbf{COM Port} specify \textbf{com2}.
diff -r 522f64fbb8bf -r a2903704c17a docs/xen-api/presentation.tex
--- a/docs/xen-api/presentation.tex Thu Apr 03 11:33:10 2008 +0100
+++ b/docs/xen-api/presentation.tex Thu Apr 03 11:34:21 2008 +0100
@@ -69,7 +69,7 @@ The API reference explicitly lists the f
The API reference explicitly lists the fields that are
bound together in this way. It also contains a diagram that shows
relationships between classes. In this diagram an edge signifies the
-existance of a pair of fields that are bound together, using standard
+existence of a pair of fields that are bound together, using standard
crows-foot notation to signify the type of relationship (e.g.\
one-many, many-many).
diff -r 522f64fbb8bf -r a2903704c17a docs/xen-api/todo.tex
--- a/docs/xen-api/todo.tex Thu Apr 03 11:33:10 2008 +0100
+++ b/docs/xen-api/todo.tex Thu Apr 03 11:34:21 2008 +0100
@@ -32,7 +32,7 @@ code, potential error description, but o
\item Clarify session behaviour wrt timeouts and disconnects.
-\item Clarify behaviour of progress field on asyncrhonous request polling when
+\item Clarify behaviour of progress field on asynchronous request polling when
that request fails.
\item Clarify which calls have asynchronous counterparts by marking them as
such in the reference. (Individual getters and setters are too small and quick
to justify having async versions)
diff -r 522f64fbb8bf -r a2903704c17a docs/xen-api/wire-protocol.tex
--- a/docs/xen-api/wire-protocol.tex Thu Apr 03 11:33:10 2008 +0100
+++ b/docs/xen-api/wire-protocol.tex Thu Apr 03 11:34:21 2008 +0100
@@ -185,7 +185,7 @@ Where {\tt uname} and {\tt password} ref
Where {\tt uname} and {\tt password} refer to your username and password
respectively, as defined by the Xen administrator.
The {\tt session\_id} returned by {\tt session.login\_with\_password} is passed
-to subequent RPC calls as an authentication token.
+to subsequent RPC calls as an authentication token.
A session can be terminated with the {\tt session.logout} function:
\begin{verbatim}
@@ -210,7 +210,7 @@ Async.VM.clone(...)}, that is non-blocki
Instead of returning its result directly, an asynchronous RPC call
returns a {\tt task-id}; this identifier is subsequently used
-to track the status of a running asynchronous RPC. Note that an asychronous
+to track the status of a running asynchronous RPC. Note that an asynchronous
call may fail immediately, before a {\tt task-id} has even been created---to
represent this eventuality, the returned {\tt task-id}
is wrapped in an XML-RPC struct with a {\tt Status}, {\tt ErrorDescription} and
@@ -248,7 +248,7 @@ Create a python object referencing the r
\end{verbatim}
Acquire a session token by logging in with a username and password
-(error-handling ommitted for brevity; the session token is pointed to by the
+(error-handling omitted for brevity; the session token is pointed to by the
key {\tt 'Value'} in the returned dictionary)
\begin{verbatim}
diff -r 522f64fbb8bf -r a2903704c17a docs/xen-api/xenapi-datamodel.tex
--- a/docs/xen-api/xenapi-datamodel.tex Thu Apr 03 11:33:10 2008 +0100
+++ b/docs/xen-api/xenapi-datamodel.tex Thu Apr 03 11:34:21 2008 +0100
@@ -75,7 +75,7 @@ host.host\_CPUs & host\_cpu.host & many-
\hline
\end{tabular}\end{center}
-The following represents bound fields (as specified above) diagramatically,
using crows-foot notation to specify one-to-one, one-to-many or many-to-many
+The following represents bound fields (as specified above) diagrammatically,
using crows-foot notation to specify one-to-one, one-to-many or many-to-many
relationships:
\begin{center}\resizebox{0.8\textwidth}{!}{
@@ -444,7 +444,7 @@ returned. Also returned is a developer-
\subsubsection{VLAN\_TAG\_INVALID}
-You tried to create a VLAN, but the tag you gave was invalid -- it mmust be
+You tried to create a VLAN, but the tag you gave was invalid -- it must be
between 0 and 4095. The parameter echoes the VLAN tag you gave.
\vspace{0.3cm}
@@ -1390,7 +1390,7 @@ Quals & Field & Type & Description \\
$\mathit{RW}$ & {\tt memory/static\_max} & int & Statically-set (i.e.
absolute) maximum (bytes) \\
$\mathit{RW}$ & {\tt memory/dynamic\_max} & int & Dynamic maximum (bytes) \\
$\mathit{RW}$ & {\tt memory/dynamic\_min} & int & Dynamic minimum (bytes) \\
-$\mathit{RW}$ & {\tt memory/static\_min} & int & Statically-set (i.e.
absolute) mininum (bytes) \\
+$\mathit{RW}$ & {\tt memory/static\_min} & int & Statically-set (i.e.
absolute) minimum (bytes) \\
$\mathit{RW}$ & {\tt VCPUs/params} & (string $\rightarrow$ string) Map &
configuration parameters for the selected VCPU policy \\
$\mathit{RW}$ & {\tt VCPUs/max} & int & Max number of VCPUs \\
$\mathit{RW}$ & {\tt VCPUs/at\_startup} & int & Boot number of VCPUs \\
_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-changelog
|
Home