spell correction - JUnit

tck/docs/userguide/src/main/jbake/content/debug.adoc

@@ -35,13 +35,13 @@ filtered out to have passing results. If the root test suite folder
 contains tests with errors or failing results, you must troubleshoot and
 correct the cause to satisfactorily complete the test run.
 
-* Errors: Tests with errors could not be executed by the Junit
+* Errors: Tests with errors could not be executed by the JUnit
 framework. These errors usually occur because the test environment is not
 properly configured.
 * Failures: Tests that fail were executed but had failing results.
 
 
-For every test run, the Junit framework creates a set of report files
+For every test run, the JUnit framework creates a set of report files
 in the target directory.
 
 
@@ -57,7 +57,7 @@ configuration issue is the cause of the failures.
 ~~~~~~~~~~~~~~~~~~~~
 
 If you need more information to identify the cause of the error or
-failure, use the Junit reports generated after running the tests.
+failure, use the JUnit reports generated after running the tests.
 
 
 [[GBFYF]][[configuration-failures]]

tck/docs/userguide/src/main/jbake/content/faq.adoc

@@ -44,7 +44,7 @@ A.3 What would cause tests be added to the exclude list?
 
 The exclude file (+{excludeListFileName}+) contains all tests that are not
 required to be run. The file is used only for documentation purpose. The tests are excluded using
-@Disabled tag in Junit when necessary. The following is a list of reasons for a test to be
+@Disabled tag in JUnit when necessary. The following is a list of reasons for a test to be
 included in the Exclude List:
 
 * An error in a Compatible Implementation that does not allow the test to

tck/docs/userguide/src/main/jbake/content/intro.adoc

@@ -209,7 +209,7 @@ Each version of a TCK includes an Exclude List contained in a `TCK-Exclude-List.
 file. 
 This is a list of test file URLs that identify tests which do not
 have to be run for the specific version of the TCK being used. 
-Whenever tests are run, the Junit framework automatically excludes
+Whenever tests are run, the JUnit framework automatically excludes
 these tests from being executed as those are disabled using '@Disabled' tag in JUnit.
 
 A vendor's compatible implementation is not required to pass or run any test on the Exclude List.

tck/docs/userguide/src/main/jbake/content/preface.adoc

@@ -23,7 +23,7 @@ The {TechnologyShortName} TCK is a portable, configurable automated
 test suite for verifying the compatibility of a vendor's
 implementation of the {TechnologyShortName} {TechnologyVersion}
 Specification (hereafter referred to as the vendor implementation or VI).
-The {TechnologyShortName} TCK uses the Junit framework to run the test suite.
+The {TechnologyShortName} TCK uses the JUnit framework to run the test suite.
 
 
 [NOTE]

tck/docs/userguide/src/main/jbake/content/using-examples.inc

@@ -3,7 +3,7 @@ NOTE TO WRITERS:
 These CLI examples can be customized as necessary.
 ///////////////////////////////////////////////////////////////////////
 
-Start the Junit tests using the following command:
+Start the JUnit tests using the following command:
 
 --
 [source,oac_no_warn]

tck/docs/userguide/src/main/jbake/content/using.adoc

@@ -15,7 +15,7 @@ Executing Tests
 5 Executing Tests
 -----------------
 
-The {TechnologyShortName} TCK uses the Junit framework
+The {TechnologyShortName} TCK uses the JUnit framework
 to execute the tests.
 
 This chapter includes the following topics:
@@ -155,4 +155,4 @@ of the Tests."]
 
 A set of report files is created for every test run. These report files
 can be found in the target directory that the test is run. After a test run is
-completed, the Junit framework writes  reports for the test run.
+completed, the JUnit framework writes  reports for the test run.