Francois Gouget : testbot: Some spelling fixes and wording tweaks.

[Alexandre Julliard]

Module: tools
Branch: master
Commit: 0c79e60d6777279b311d8adc34cca0afd2aa6c87
URL:    http://source.winehq.org/git/tools.git/?a=commit;h=0c79e60d6777279b311d8adc3...

Author: Francois Gouget <fgouget(a)codeweavers.com>
Date:   Thu Oct  3 12:16:48 2013 +0200

testbot: Some spelling fixes and wording tweaks.

---

 testbot/bin/Engine.pl           |    4 ++--
 testbot/lib/WineTestBot/Jobs.pm |    2 +-
 testbot/lib/WineTestBot/VMs.pm  |    2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/testbot/bin/Engine.pl b/testbot/bin/Engine.pl
index 2438298..03575f6 100755
--- a/testbot/bin/Engine.pl
+++ b/testbot/bin/Engine.pl
@@ -73,7 +73,7 @@ It has to contend with three main scenarios:
 - The Engine being restarted. Any task started just before that is still
   running should still have its process and powered on VM and should be left
   alone so it can complete normally. If a task died unexpectedly while the
-  Engine was done it's ok to requeue it.
+  Engine was down it's ok to requeue it.
 - The Engine startup after a reboot. All task processes will be dead and need
   to be requeued. But the VMs are likely to be hosted on a separate machine so
   it is quite possible that they will still be running. Hopefully any running
@@ -82,7 +82,7 @@ It has to contend with three main scenarios:
 - A shutdown of the Engine and its tasks / VMs. In this case it's used to
   kill the running tasks and requeue them, and/or shut down the VMs.
 
-In all cases we only trust that a VM status field is still valid:
+In all cases we only trust that a VM status field is still valid if:
 - It is 'running' and used by a task that is still running.
 - It is 'reverting' or 'sleeping', is powered on and the revert process is
   still running.
diff --git a/testbot/lib/WineTestBot/Jobs.pm b/testbot/lib/WineTestBot/Jobs.pm
index 35514a7..48e74f9 100644
--- a/testbot/lib/WineTestBot/Jobs.pm
+++ b/testbot/lib/WineTestBot/Jobs.pm
@@ -399,7 +399,7 @@ VM Statuses.
 The number of VMs running on the host must be kept under $MaxRunningVMs. The
 rational behind this limit is that the host may not be able to run more VMs
 simultaneously, typically due to memory or CPU constraints. Also note that
-this limit must be respected even if there are more than one hypervisor running
+this limit must be respected even if there is more than one hypervisor running
 on the host.
 
 =item *
diff --git a/testbot/lib/WineTestBot/VMs.pm b/testbot/lib/WineTestBot/VMs.pm
index 37d1c4f..8069c90 100644
--- a/testbot/lib/WineTestBot/VMs.pm
+++ b/testbot/lib/WineTestBot/VMs.pm
@@ -535,7 +535,7 @@ sub RunRevert
 
   # Note that if the child process completes quickly (typically due to some
   # error), it may set ChildPid to undef before we get here. So we may end up
-  # with non-reverting VM for which ChildPid is set. That's ok because
+  # with non-reverting VMs for which ChildPid is set. That's ok because
   # ChildPid should be ignored anyway if Status is not 'reverting' or
   # 'sleeping'.
   $self->ChildPid($Pid);