Update CONFIGDOC.md

Author: mw-hrastega

CONFIGDOC.md

@@ -493,13 +493,13 @@ Starting in R2024b, if you have a MATLAB Test™ license, you can view your
 - Run tests with a [`matlab.buildtool.tasks.TestTask`](https://www.mathworks.com/help/matlab/ref/matlab.buildtool.tasks.testtask-class.html) instance using the **Run MATLAB Build** or `runMATLABBuild` step. 
 - Run tests with a default test runner using the **Run MATLAB Command** or `runMATLABCommand` step. A default test runner is equivalent to the runner that the testing framework configures by default when you call the [`runtests`](https://www.mathworks.com/help/matlab/ref/runtests.html) function.
 
-After your build runs, the Jenkins build summary page displays the number of tests in the test suite as well as the number of tests that passed, failed, were incomplete (due to assumption failure), and did not run (due to fatal assertion failure). You can click the **MATLAB Test Results** link on the page to access the table of test results. The status buttons above the table provide a summary of the test results. By default, the table includes a row for each file that defines a test in the test suite. Each table row displays the status of a test file, its name, and the time it took to run. You can point to a filename in the table to identify its path within your project.
+After your build runs, the Jenkins build summary page displays the number of tests in the test suite, as well as the number of tests that passed, failed, were incomplete (due to assumption failure), and did not run (due to fatal assertion failure). You can click the **MATLAB Test Results** link on the page to access the table of test results. The status buttons above the table provide a summary of the test results. By default, the table includes a row for each file that defines a test in the test suite. Each table row displays the status of a test file, its name, and the time it took to run. You can point to a filename in the table to identify its path within your project.
 
 ![Table of MATLAB test results including one test file. The row in the table displays an Incomplete status, filename, expander, and duration.](https://github.com/user-attachments/assets/1764d0f2-d4d9-4b93-bc82-0158a011c1fc)
 
-You can interact with the table of test results. To view the results of tests within each test file, click the expander to the right of the filename. The test results are displayed in a table under the filename. The row corresponding to each test includes the test status (Passed, Failed, Incomplete, or Not Run), test procedure name, test diagnostics, and duration. 
+You can interact with the table of test results. To view the results of tests within each test file, click the expander to the right of the filename. The test results appear in a table under the filename. The row corresponding to each test includes the test status (Passed, Failed, Incomplete, or Not Run), test procedure name, test diagnostics, and duration. 
 
-![Table of MATLAB test results including three passed tests and one incomplete test from a single test files. The tests within the first test file are visiable after clicking the expander to the right of the filename. The row corresponding to each test includes the test procedure name, its diagnostics, and duration.](https://github.com/user-attachments/assets/a275caa7-a297-4510-a151-b7f2dee9e3c9)
+![Table of MATLAB test results including three passed tests and one incomplete test from a single test files. The tests within the test file appear after clicking the expander to the right of the filename. The row corresponding to each test includes the test status, test procedure name, diagnostics, and duration.](https://github.com/user-attachments/assets/a275caa7-a297-4510-a151-b7f2dee9e3c9)
 
 You can use the status filters above the **MATLAB Test Results** table to customize your view. For example, to focus on any incomplete tests, select the Incomplete status filter.