From 48f0d952faad9bf386c454bf32f6b98cf658f15b Mon Sep 17 00:00:00 2001 From: Keir Fraser Date: Thu, 3 Apr 2008 11:34:21 +0100 Subject: docs: Fix typos. Signed-off-by: Atsushi SAKAI --- 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 +++--- 4 files changed, 8 insertions(+), 8 deletions(-) (limited to 'docs/xen-api') diff --git a/docs/xen-api/presentation.tex b/docs/xen-api/presentation.tex index a1f33dc99f..17fe3c598a 100644 --- a/docs/xen-api/presentation.tex +++ b/docs/xen-api/presentation.tex @@ -69,7 +69,7 @@ VM object to be updated automatically. 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 --git a/docs/xen-api/todo.tex b/docs/xen-api/todo.tex index b66dec0aba..615a5e57da 100644 --- a/docs/xen-api/todo.tex +++ b/docs/xen-api/todo.tex @@ -32,7 +32,7 @@ code, potential error description, but otherwise no value. \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 --git a/docs/xen-api/wire-protocol.tex b/docs/xen-api/wire-protocol.tex index 2a75c65dcb..6c0dc29771 100644 --- a/docs/xen-api/wire-protocol.tex +++ b/docs/xen-api/wire-protocol.tex @@ -185,7 +185,7 @@ you must login and initiate a session. For example: 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-blocking. 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 remote server: \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 --git a/docs/xen-api/xenapi-datamodel.tex b/docs/xen-api/xenapi-datamodel.tex index c7645710e9..04a0266550 100644 --- a/docs/xen-api/xenapi-datamodel.tex +++ b/docs/xen-api/xenapi-datamodel.tex @@ -75,7 +75,7 @@ host.host\_CPUs & host\_cpu.host & many-to-one\\ \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-only diagnostic reason. \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 @@ $\mathit{RO}_\mathit{run}$ & {\tt resident\_on} & host ref & the host the VM is $\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 \\ -- cgit v1.2.3