Fix typos

Change-Id: I9a5940027423ff0791fa7da0b79b617412ce6b86
Reviewed-on: https://gerrit.libreoffice.org/21209
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Ashod Nakashian <ashnakash@gmail.com>

3 files changed, 14 insertions, 14 deletions

diff --git a/testtools/qa/cli/readme.txt b/testtools/qa/cli/readme.txt
index d0a55beae98b..88ad4bd30b12 100644
--- a/testtools/qa/cli/readme.txt
+++ b/testtools/qa/cli/readme.txt
@@ -1,26 +1,26 @@
 This test is for Windows only!
 
-The cli test uses .NET assemblies: 
-cli_types.dll, 
-cli_basetypes.dll, 
-cli_ure.dll, 
+The cli test uses .NET assemblies:
+cli_types.dll,
+cli_basetypes.dll,
+cli_ure.dll,
 cli_cppuhelper.dll.
 
 
-When an office is properly installed then these assemblies can be found in the 
-global assebly cache (GAC), for example in c:\windows\assembly.
+When an office is properly installed then these assemblies can be found in the
+global assembly cache (GAC), for example in c:\windows\assembly.
 
-When the test is run then the assemblies are used from the GAC. That is 
+When the test is run then the assemblies are used from the GAC. That is
 one has to make sure that one has the respective office installed.
 
-The test can also be run without an installed office. Then the assemblies are used 
+The test can also be run without an installed office. Then the assemblies are used
 which reside next to the executable. The testtools project copies the assemblies from
 the build environment into the wntmscixx\bin folder.
 
-However, if for some reason an assembly remains in the GAC than it is used no matter 
+However, if for some reason an assembly remains in the GAC than it is used no matter
 what.
 
 
-The qa test simply executes the cli_bridgetest_inprocess.exe. All console output is decarded.
-When the test fails one should directly run that executable. Then one may see the cause 
+The qa test simply executes the cli_bridgetest_inprocess.exe. All console output is descarded.
+When the test fails one should directly run that executable. Then one may see the cause
 of the failure in the console.
diff --git a/testtools/source/bridgetest/cli/cli_cs_bridgetest.cs b/testtools/source/bridgetest/cli/cli_cs_bridgetest.cs
index ed4f483efbbc..9d629e062c49 100644
--- a/testtools/source/bridgetest/cli/cli_cs_bridgetest.cs
+++ b/testtools/source/bridgetest/cli/cli_cs_bridgetest.cs
@@ -966,7 +966,7 @@ static bool raiseException(XBridgeTest xLBT )
 
     private void perform_test( XBridgeTest xLBT )
     {
-        bool bRet= true;;
+        bool bRet= true;
        bRet = check( performTest( xLBT ), "standard test" ) && bRet;
        bRet = check( raiseException( xLBT ) , "exception test" )&& bRet;
        bRet = check( raiseOnewayException( xLBT ), "oneway exception test" ) && bRet;
diff --git a/testtools/source/cliversioning/readme.txt b/testtools/source/cliversioning/readme.txt
index 81a0a1747860..c2878c3836f5 100644
--- a/testtools/source/cliversioning/readme.txt
+++ b/testtools/source/cliversioning/readme.txt
@@ -25,7 +25,7 @@ GAC and if the policy files are correct. The office must be installed with compl
 system integration. That is, one does not use setup /a for starting the
 installation.
 
-In OOo 3.0 there was a breanking change so that the test created for previous
+In OOo 3.0 there was a breaking change so that the test created for previous
 version do not work anymore. To use these old tests one needs to install a
 version of OOo less than v 3.0. Then one needs to check out the cli_ure module
 for that version. The tests are contained in cli_ure/qa/versioning.
@@ -86,7 +86,7 @@ because it puts out more information.
 Creating a new version_xxx.dll
 ==============================
 When a version of our assemblies changes then one should provide a new version dll which test exactly the assemblies with the changed version. This is easily done:
-1. set the build environment in which the new versions are effectiv.
+1. set the build environment in which the new versions are effective.
 2  call: dmake name=version_xxx.dll
 3. copy the new version dll from the output tree into qa/versioning/version_libs
 4. commit the new version.dll using the -kb switch (only when creating the new file : cvs new -kb version_3_1_0.dll)