ia64/xen-unstable

changeset 10060:cb70d4f8d718

Fix spelling errors in man pages.
Signed-off-by: Charles Coffing <ccoffing@novell.com>
author kaf24@firebug.cl.cam.ac.uk
date Mon May 15 07:51:07 2006 +0100 (2006-05-15)
parents d20a2a971103
children dc213d745642
files docs/man/xend-config.sxp.pod.5 docs/man/xm.pod.1 docs/man/xmdomain.cfg.pod.5
line diff
     1.1 --- a/docs/man/xend-config.sxp.pod.5	Mon May 15 07:46:57 2006 +0100
     1.2 +++ b/docs/man/xend-config.sxp.pod.5	Mon May 15 07:51:07 2006 +0100
     1.3 @@ -107,7 +107,7 @@ If the value is 0, all available CPUs wi
     1.4  =item I<enable-dump>
     1.5  
     1.6  A boolean value that tells xend whether or not core dumps of guest
     1.7 -domains should be saved when a crash occurrs.  Defaults to I<no>.
     1.8 +domains should be saved when a crash occurs.  Defaults to I<no>.
     1.9  
    1.10  =item I<external-migration-tool>
    1.11  
     2.1 --- a/docs/man/xm.pod.1	Mon May 15 07:46:57 2006 +0100
     2.2 +++ b/docs/man/xm.pod.1	Mon May 15 07:51:07 2006 +0100
     2.3 @@ -27,12 +27,12 @@ each of those sub commands.
     2.4  
     2.5  =head1 NOTES
     2.6  
     2.7 -All B<xm> opperations rely upon the Xen control daemon, aka B<xend>.
     2.8 +All B<xm> operations rely upon the Xen control daemon, aka B<xend>.
     2.9  For any xm commands to run xend must also be running.  For this reason
    2.10  you should start xend as a service when your system first boots using
    2.11  xen.
    2.12  
    2.13 -Most B<xm> commands require root privledges to run due to the
    2.14 +Most B<xm> commands require root privileges to run due to the
    2.15  communications channels used to talk to the hypervisor.  Running as
    2.16  non root will return an error.
    2.17  
    2.18 @@ -169,7 +169,7 @@ The domain is currently running on a CPU
    2.19  
    2.20  =item B<b - blocked>
    2.21  
    2.22 -The domain is blocked, and not running or runable.  This can be caused
    2.23 +The domain is blocked, and not running or runnable.  This can be caused
    2.24  because the domain is waiting on IO (a traditional wait state) or has
    2.25  gone to sleep because there was nothing else for it to do.
    2.26  
    2.27 @@ -260,7 +260,7 @@ careful when using this command on runni
    2.28  
    2.29  Migrate a domain to another Host machine. B<Xend> must be running on
    2.30  other host machine, it must be running the same version of xen, it
    2.31 -must have the migration tcp port open and accepting connections from
    2.32 +must have the migration TCP port open and accepting connections from
    2.33  the source host, and there must be sufficient resources for the domain
    2.34  to run (memory, disk, etc).
    2.35  
    2.36 @@ -337,7 +337,7 @@ severed upon restore, as TCP timeouts ma
    2.37  =item B<shutdown> I<[options]> I<domain-id>
    2.38  
    2.39  Gracefully shuts down a domain.  This coordinates with the domain OS
    2.40 -to perform graceful shutdown, so there is no guaruntee that it will
    2.41 +to perform graceful shutdown, so there is no guarantee that it will
    2.42  succeed, and may take a variable length of time depending on what
    2.43  services must be shutdown in the domain.  The command returns
    2.44  immediately after signally the domain unless that I<-w> flag is used.
    2.45 @@ -573,11 +573,11 @@ B<PARAMETERS>
    2.46  
    2.47  =item I<period>
    2.48  
    2.49 -The normal EDF scheduling usage in nanosecs
    2.50 +The normal EDF scheduling usage in nanoseconds
    2.51  
    2.52  =item I<slice>
    2.53  
    2.54 -The normal EDF scheduling usage in nanosecs
    2.55 +The normal EDF scheduling usage in nanoseconds
    2.56  
    2.57  FIXME: these are lame, should explain more.
    2.58  
    2.59 @@ -726,7 +726,7 @@ circumstances this should actually work.
    2.60  
    2.61  =item I<mac=macaddr>
    2.62  
    2.63 -The MAC address that the domain will see on its ethernet device.  If
    2.64 +The MAC address that the domain will see on its Ethernet device.  If
    2.65  the device is not specified it will be randomly generated with the
    2.66  00:16:3e vendor id prefix.
    2.67  
    2.68 @@ -768,7 +768,7 @@ formatted as a list or as an S-Expressio
    2.69  
    2.70  The Virtual Network interfaces for Xen.
    2.71  
    2.72 -FIXME: This needs a lot more explaination, or it needs to be ripped
    2.73 +FIXME: This needs a lot more explanation, or it needs to be ripped
    2.74  out entirely.
    2.75  
    2.76  =over 4
     3.1 --- a/docs/man/xmdomain.cfg.pod.5	Mon May 15 07:46:57 2006 +0100
     3.2 +++ b/docs/man/xmdomain.cfg.pod.5	Mon May 15 07:51:07 2006 +0100
     3.3 @@ -80,7 +80,7 @@ An array of block device stanzas, in the
     3.4  
     3.5      disk = [ "stanza1", "stanza2", ... ]
     3.6  
     3.7 -Each stanza has 3 terms, seperated by commas,
     3.8 +Each stanza has 3 terms, separated by commas,
     3.9  "backend-dev,frontend-dev,mode".
    3.10  
    3.11  =over 4
    3.12 @@ -112,7 +112,7 @@ I<r> (read-only), I<w> (read/write).
    3.13  
    3.14  =item B<vif>
    3.15  
    3.16 -An arrray of virtual interface stanzas in the form:
    3.17 +An array of virtual interface stanzas in the form:
    3.18  
    3.19      vif = [ "stanza1", "stanza2", ... ]
    3.20