ia64/xen-unstable

changeset 17382:a2903704c17a

docs: Fix typos.
Signed-off-by: Atsushi SAKAI <sakaia@jp.fujitsu.com>
author Keir Fraser <keir.fraser@citrix.com>
date Thu Apr 03 11:34:21 2008 +0100 (2008-04-03)
parents 522f64fbb8bf
children da35b52c4fd7
files docs/misc/VMX_changes.txt docs/misc/hg-cheatsheet.txt docs/misc/vtpm.txt docs/misc/xenstore.txt docs/src/interface.tex docs/src/user.tex docs/xen-api/presentation.tex docs/xen-api/todo.tex docs/xen-api/wire-protocol.tex docs/xen-api/xenapi-datamodel.tex
line diff
     1.1 --- a/docs/misc/VMX_changes.txt	Thu Apr 03 11:33:10 2008 +0100
     1.2 +++ b/docs/misc/VMX_changes.txt	Thu Apr 03 11:34:21 2008 +0100
     1.3 @@ -79,7 +79,7 @@ Changes to the existing code:
     1.4  
     1.5      * include/asm-x86/processor.h: struct arch_vmx_struct arch_vmx has
     1.6        been added to the thread_struct data structure. The arch_vmx has
     1.7 -      the addtional VMX-related CPU context.
     1.8 +      the additional VMX-related CPU context.
     1.9  
    1.10      * arch/x86/io_apic.c: reverse mapping between vector and irq has
    1.11        been added. We will revisit this code when considering MSI
     2.1 --- a/docs/misc/hg-cheatsheet.txt	Thu Apr 03 11:33:10 2008 +0100
     2.2 +++ b/docs/misc/hg-cheatsheet.txt	Thu Apr 03 11:34:21 2008 +0100
     2.3 @@ -12,7 +12,7 @@ control.  This note aims to provide a qu
     2.4  running with the new tools as quickly as possible, and is written from
     2.5  the perspective of someone who has been using BK.
     2.6  
     2.7 -For a more detailed exposition, see the mecurial tutorial:
     2.8 +For a more detailed exposition, see the mercurial tutorial:
     2.9   http://www.serpentine.com/mercurial/index.cgi?Tutorial
    2.10  
    2.11  The Hg manpage is available at:
    2.12 @@ -69,7 +69,7 @@ descendent in one repository -- somethin
    2.13  actually pretty neat. For example, it would in principle enable you to
    2.14  have both the 2.0-testing and unstable trees in a single
    2.15  repository. We shyed away from doing this as we thought the risk of
    2.16 -commiting to the wrong head was too great.
    2.17 +committing to the wrong head was too great.
    2.18  
    2.19  One slightly confusing aspect of Hg is that many of the commands have
    2.20  aliases, and hence when looking things up in the man page its not
    2.21 @@ -81,7 +81,7 @@ more sense, at least to RCS refugees lik
    2.22  Getting Xen
    2.23  -----------
    2.24  
    2.25 -The URL for the mainline Xen mercurial respository is:
    2.26 +The URL for the mainline Xen mercurial repository is:
    2.27  
    2.28     http://xenbits.xensource.com/xen-unstable.hg
    2.29     (similarly for xen-2.0 and xen-2.0-testing)
    2.30 @@ -273,9 +273,9 @@ Pushing changesets to a parent repositor
    2.31  
    2.32  Pushes changes up to a parent. You can't push if you pulled the
    2.33  repository off the web interface. In fact, you can currently only push
    2.34 -to an ssh target -- filesystem drectory targets don't work, but this
    2.35 +to an ssh target -- filesystem directory targets don't work, but this
    2.36  will be fixed soon.
    2.37 -For now it is possible to set up assymetric pull/push paths. Pulls can
    2.38 +For now it is possible to set up asymmetric pull/push paths. Pulls can
    2.39  be done via web interface while pushes via ssh. Example of .hg/hgrc config
    2.40  file:
    2.41    | [paths]
    2.42 @@ -332,7 +332,7 @@ by other checked-out versions. This can 
    2.43  system. Hg will probably get fixed soon, but in the meantime you can
    2.44  cleanup with "find -depth -type d -print | xargs -r rmdir".
    2.45  
    2.46 -You can return to the tip by ommiting an explicit changeset id.
    2.47 +You can return to the tip by omitting an explicit changeset id.
    2.48     
    2.49  The manifest command lets you see the contents of the repository for 
    2.50  the current changeset.
    2.51 @@ -347,7 +347,7 @@ This will print a bunch of records of th
    2.52     | 7fc869aae2945a9f4626fad96552db3103e61cb9 644 README
    2.53     | ...
    2.54  
    2.55 -This lists the hash of each file, its 1-bit 'executable' atribute
    2.56 +This lists the hash of each file, its 1-bit 'executable' attribute
    2.57  (either file permission mode 644 or 755), and the file name.  So, to
    2.58  determine the files that change across two changesets, you would dump
    2.59  the respective manifests to files, and use diff.
     3.1 --- a/docs/misc/vtpm.txt	Thu Apr 03 11:33:10 2008 +0100
     3.2 +++ b/docs/misc/vtpm.txt	Thu Apr 03 11:34:21 2008 +0100
     3.3 @@ -143,7 +143,7 @@ PCR-07: 00 00 00 00 00 00 00 00 00 00 00
     3.4  PCR-08: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
     3.5  [...]
     3.6  
     3.7 -At this point the user domain has been sucessfully connected to its
     3.8 +At this point the user domain has been successfully connected to its
     3.9  virtual TPM instance.
    3.10  
    3.11  For further information please read the documentation in 
     4.1 --- a/docs/misc/xenstore.txt	Thu Apr 03 11:33:10 2008 +0100
     4.2 +++ b/docs/misc/xenstore.txt	Thu Apr 03 11:34:21 2008 +0100
     4.3 @@ -129,7 +129,7 @@ The following are the actual type values
     4.4  reply payloads as applicable:
     4.5  
     4.6  
     4.7 ----------- Database read, write and permissions operatons ----------
     4.8 +---------- Database read, write and permissions operations ----------
     4.9  
    4.10  READ			<path>|			<value|>
    4.11  WRITE			<path>|<value|>
    4.12 @@ -206,7 +206,7 @@ WATCH_EVENT					<epath>|<token>|
    4.13  	as described above.  req_id and tx_id are both 0.
    4.14  
    4.15  	<epath> is the event's path, ie the actual path that was
    4.16 -	modifed; however if the event was the recursive removal of an
    4.17 +	modified; however if the event was the recursive removal of an
    4.18  	parent of <wpath>, <epath> is just
    4.19  	<wpath> (rather than the actual path which was removed).  So
    4.20  	<epath> is a child of <wpath>, regardless.
     5.1 --- a/docs/src/interface.tex	Thu Apr 03 11:33:10 2008 +0100
     5.2 +++ b/docs/src/interface.tex	Thu Apr 03 11:34:21 2008 +0100
     5.3 @@ -470,7 +470,7 @@ typedef struct shared_info {
     5.4       * are delivered by this mechanism:
     5.5       *  1. Bi-directional inter- and intra-domain connections. Domains must
     5.6       *     arrange out-of-band to set up a connection (usually by allocating
     5.7 -     *     an unbound 'listener' port and avertising that via a storage service
     5.8 +     *     an unbound 'listener' port and advertising that via a storage service
     5.9       *     such as xenstore).
    5.10       *  2. Physical interrupts. A domain with suitable hardware-access
    5.11       *     privileges can bind an event-channel port to a physical interrupt
    5.12 @@ -915,7 +915,7 @@ These activities include:
    5.13    (e.g. performance-related statistics, etc).
    5.14  \end{itemize}
    5.15  
    5.16 -The store is arranged as a hierachical collection of key-value pairs.
    5.17 +The store is arranged as a hierarchical collection of key-value pairs.
    5.18  Each domain has a directory hierarchy containing data related to its
    5.19  configuration.  Domains are permitted to register for notifications
    5.20  about changes in subtrees of the store, and to apply changes to the
    5.21 @@ -1114,9 +1114,9 @@ This path contains:
    5.22            \end{description}
    5.23          \end{description}
    5.24  	
    5.25 -      \item[device-misc/] miscellanous information for devices 
    5.26 +      \item[device-misc/] miscellaneous information for devices 
    5.27  	\begin{description}
    5.28 -	\item[vif/] miscellanous information for vif devices
    5.29 +	\item[vif/] miscellaneous information for vif devices
    5.30  	  \begin{description}
    5.31  	  \item[nextDeviceID] the next device id to use 
    5.32  	  \end{description}
    5.33 @@ -1511,7 +1511,7 @@ Otherwise an error message is automatica
    5.34  The virtual TPM implementation listens for TPM request on /dev/vtpm. Since
    5.35  it must be able to apply the TPM request packet to the virtual TPM instance
    5.36  associated with the virtual machine, a 4-byte virtual TPM instance
    5.37 -identifier is prepended to each packet by the backend driver (in network
    5.38 +identifier is pretended to each packet by the backend driver (in network
    5.39  byte order) for internal routing of the request.
    5.40  
    5.41  \subsection{Virtual TPM ring interface}
     6.1 --- a/docs/src/user.tex	Thu Apr 03 11:33:10 2008 +0100
     6.2 +++ b/docs/src/user.tex	Thu Apr 03 11:34:21 2008 +0100
     6.3 @@ -3394,7 +3394,7 @@ or \verb|A-Bank.MarketAnalysis| workload
     6.4  Alternatively, a system that has two hard-drives does not need a VIO
     6.5  domain but can directly assign one hardware storage device to each of
     6.6  the workloads if the platform offers an IO-MMU, cf
     6.7 -Section~\ref{s:ddsecurity}.  Sharing hardware through virtualizated devices
     6.8 +Section~\ref{s:ddsecurity}.  Sharing hardware through virtualized devices
     6.9  is a trade-off between the amount of trusted code (size of the trusted
    6.10  computing base) and the amount of acceptable over-provisioning. This
    6.11  holds both for peripherals and for system platforms.
    6.12 @@ -4652,7 +4652,7 @@ answering the questions as follows:
    6.13  
    6.14  \begin{enumerate}
    6.15  \item When the program asks for \textbf{model},
    6.16 -scroll down and selese \textbf{SummaSketch (MM Compatible)}.
    6.17 +scroll down and select \textbf{SummaSketch (MM Compatible)}.
    6.18  
    6.19  \item When the program asks for \textbf{COM Port} specify \textbf{com2}.
    6.20  
     7.1 --- a/docs/xen-api/presentation.tex	Thu Apr 03 11:33:10 2008 +0100
     7.2 +++ b/docs/xen-api/presentation.tex	Thu Apr 03 11:34:21 2008 +0100
     7.3 @@ -69,7 +69,7 @@ VM object to be updated automatically.
     7.4  The API reference explicitly lists the fields that are
     7.5  bound together in this way. It also contains a diagram that shows
     7.6  relationships between classes. In this diagram an edge signifies the
     7.7 -existance of a pair of fields that are bound together, using standard
     7.8 +existence of a pair of fields that are bound together, using standard
     7.9  crows-foot notation to signify the type of relationship (e.g.\
    7.10  one-many, many-many).
    7.11  
     8.1 --- a/docs/xen-api/todo.tex	Thu Apr 03 11:33:10 2008 +0100
     8.2 +++ b/docs/xen-api/todo.tex	Thu Apr 03 11:34:21 2008 +0100
     8.3 @@ -32,7 +32,7 @@ code, potential error description, but o
     8.4  
     8.5  \item Clarify session behaviour wrt timeouts and disconnects.
     8.6  
     8.7 -\item Clarify behaviour of progress field on asyncrhonous request polling when
     8.8 +\item Clarify behaviour of progress field on asynchronous request polling when
     8.9  that request fails.
    8.10  
    8.11  \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)
     9.1 --- a/docs/xen-api/wire-protocol.tex	Thu Apr 03 11:33:10 2008 +0100
     9.2 +++ b/docs/xen-api/wire-protocol.tex	Thu Apr 03 11:34:21 2008 +0100
     9.3 @@ -185,7 +185,7 @@ you must login and initiate a session. F
     9.4  Where {\tt uname} and {\tt password} refer to your username and password
     9.5  respectively, as defined by the Xen administrator.
     9.6  The {\tt session\_id} returned by {\tt session.login\_with\_password} is passed
     9.7 -to subequent RPC calls as an authentication token.
     9.8 +to subsequent RPC calls as an authentication token.
     9.9  
    9.10  A session can be terminated with the {\tt session.logout} function:
    9.11  \begin{verbatim}
    9.12 @@ -210,7 +210,7 @@ Async.VM.clone(...)}, that is non-blocki
    9.13  
    9.14  Instead of returning its result directly, an asynchronous RPC call
    9.15  returns a {\tt task-id}; this identifier is subsequently used
    9.16 -to track the status of a running asynchronous RPC. Note that an asychronous
    9.17 +to track the status of a running asynchronous RPC. Note that an asynchronous
    9.18  call may fail immediately, before a {\tt task-id} has even been created---to
    9.19  represent this eventuality, the returned {\tt task-id}
    9.20  is wrapped in an XML-RPC struct with a {\tt Status}, {\tt ErrorDescription} and
    9.21 @@ -248,7 +248,7 @@ Create a python object referencing the r
    9.22  \end{verbatim}
    9.23  
    9.24  Acquire a session token by logging in with a username and password
    9.25 -(error-handling ommitted for brevity; the session token is pointed to by the
    9.26 +(error-handling omitted for brevity; the session token is pointed to by the
    9.27  key {\tt 'Value'} in the returned dictionary)
    9.28  
    9.29  \begin{verbatim}
    10.1 --- a/docs/xen-api/xenapi-datamodel.tex	Thu Apr 03 11:33:10 2008 +0100
    10.2 +++ b/docs/xen-api/xenapi-datamodel.tex	Thu Apr 03 11:34:21 2008 +0100
    10.3 @@ -75,7 +75,7 @@ host.host\_CPUs & host\_cpu.host & many-
    10.4  \hline
    10.5  \end{tabular}\end{center}
    10.6  
    10.7 -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
    10.8 +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
    10.9                     relationships:
   10.10  
   10.11  \begin{center}\resizebox{0.8\textwidth}{!}{
   10.12 @@ -444,7 +444,7 @@ returned.  Also returned is a developer-
   10.13  
   10.14  \subsubsection{VLAN\_TAG\_INVALID}
   10.15  
   10.16 -You tried to create a VLAN, but the tag you gave was invalid -- it mmust be
   10.17 +You tried to create a VLAN, but the tag you gave was invalid -- it must be
   10.18  between 0 and 4095.  The parameter echoes the VLAN tag you gave.
   10.19  
   10.20  \vspace{0.3cm}
   10.21 @@ -1390,7 +1390,7 @@ Quals & Field & Type & Description \\
   10.22  $\mathit{RW}$ &  {\tt memory/static\_max} & int & Statically-set (i.e. absolute) maximum (bytes) \\
   10.23  $\mathit{RW}$ &  {\tt memory/dynamic\_max} & int & Dynamic maximum (bytes) \\
   10.24  $\mathit{RW}$ &  {\tt memory/dynamic\_min} & int & Dynamic minimum (bytes) \\
   10.25 -$\mathit{RW}$ &  {\tt memory/static\_min} & int & Statically-set (i.e. absolute) mininum (bytes) \\
   10.26 +$\mathit{RW}$ &  {\tt memory/static\_min} & int & Statically-set (i.e. absolute) minimum (bytes) \\
   10.27  $\mathit{RW}$ &  {\tt VCPUs/params} & (string $\rightarrow$ string) Map & configuration parameters for the selected VCPU policy \\
   10.28  $\mathit{RW}$ &  {\tt VCPUs/max} & int & Max number of VCPUs \\
   10.29  $\mathit{RW}$ &  {\tt VCPUs/at\_startup} & int & Boot number of VCPUs \\