[libvirt] [libvirt-tck 1/3] Correct typos in documents

* docs/intro.pod * docs/writing-tests.pod --- docs/intro.pod | 10 +++++----- docs/writing-tests.pod | 8 ++++---- 2 files changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/intro.pod b/docs/intro.pod index 5943f3b..3684d51 100644 --- a/docs/intro.pod +++ b/docs/intro.pod @@ -16,7 +16,7 @@ =head1 libvirt TCK: Technology Compatability Kit The libvirt TCK provides a framework for performing testing -of the integration bqetween libvirt drivers, the underlying virt +of the integration between libvirt drivers, the underlying virt hypervisor technology, related operating system services and system configuration. The idea (and name) is motivated by the Java TCK @@ -51,7 +51,7 @@ to determine the level of compatability of their platform, and evaluate whether it will meet their needs, and get awareness of any regressions that may have occurred since a previous test run -In relation to other libvirt testing, the split of responsibiity +In relation to other libvirt testing, the split of responsibility will be =over 4 @@ -131,7 +131,7 @@ These are all currently available within Fedora 11, and later These modules are all well tested, actively maintained parts of Perl / CPAN, so easily available for every other operating system -in existance. +in existence. =head2 Overview of framework structure @@ -238,7 +238,7 @@ update the 'ID' field in the virDomainPtr =item * -After destroying a active domain, the remote driver did not +After destroying an active domain, the remote driver did not update the 'ID' field in the virDomainPtr =item * @@ -340,7 +340,7 @@ vs a virtual root filesystem for containers =item More helper XML helper modules -Add helpers for building network, storage and inteface XML +Add helpers for building network, storage and interface XML configs =item Broader host configuration diff --git a/docs/writing-tests.pod b/docs/writing-tests.pod index 5380f5d..3bc70b0 100644 --- a/docs/writing-tests.pod +++ b/docs/writing-tests.pod @@ -38,7 +38,7 @@ of checks that will be run in the test case. This enables the test harness to determine if a test case crashed / exited earlier than expected without running all checks. Each line starts with a word 'ok' or 'not ok' to indicate state of the check, followed -by the check number (assigned incremnetally), and a description +by the check number (assigned incrementally), and a description of the check performed. Diagnostic comments can be output using a leading '#' to assist in debugging / interpreting the results. @@ -148,7 +148,7 @@ Going line by line, this first imports the 'Sys::Virt::TCK' package and its functions. Then it creates an instance of the 'Sys::Virt::TCK' object. Then it runs the 'setup' method to obtain a libvirt connection, catching any error that may be thrown. The fourth line -willl abort the entire test if an error occurred during setup. The +will abort the entire test if an error occurred during setup. The final line registers a 'END' block which will perform cleanup when Perl exits. @@ -190,7 +190,7 @@ domain. "created a running domain", "test"); This creates a new running guest from '$xml', and checks that it -succeeeded and returns a domain object with an expected name of +succeeded and returns a domain object with an expected name of 'test'. If an exception was thrown during guest creation this will be reported as an error. If the guest has the incorrect name, that will also be reported as an error. @@ -428,6 +428,6 @@ If something went wrong, it might look like # Looks like you failed 1 test of 2 run. # Looks like your test died just after 2. -Notice that since the tst script declared upfront that it intended +Notice that since the test script declared upfront that it intended to run 5 checks, Perl was able to detect that it aborted earlier than expected. -- 1.7.1