Fix typos

Author: mw-hrastega

CONFIGDOC.md

@@ -57,7 +57,7 @@ Artifacts are not autogenerated if you choose to run tests using this build step
 #### Run MATLAB Tests
 This build step uses a default setting to run tests authored using the MATLAB Unit Testing Framework or Simulink Test™. By default, if your code is organized into files and folders within a MATLAB project, then the plugin includes any test files in the project that have been labeled as `Test`. If your code does not leverage a MATLAB project or uses a MATLAB release before R2019a, then the plugin includes all tests in the project workspace, including its subfolders.
 
-With the **Run MATLAB Tests** build step, you can customize your test run using the existing options in the step configuration panel. For example, you can add folders to the MATLAB search path, have control over which tests to run, and generate different types of artifacts. If you do not select any of the check boxes, all of the tests in your project run and test failures fail the build.
+With the **Run MATLAB Tests** build step, you can customize your test run using the existing options in the step configuration panel. For example, you can add folders to the MATLAB search path, have control over which tests to run, and generate different types of artifacts. If you do not select any of the check boxes, all the tests in your project run and test failures fail the build.
 
 ![run_matlab_tests](https://user-images.githubusercontent.com/48831250/105909610-c2842b00-5ff5-11eb-9b6a-9530ae7289ff.png)
 
@@ -134,7 +134,7 @@ Once you have specified the axes, add the required build steps in the **Build**
    *   If you add the [**Run MATLAB Command**](#run-matlab-command) build step, enter your commands in the **Command** box. You can use the user-defined axes to create your commands. For example:
 
 ```
-results = runtests(pwd,'Tag','$TEST_TAG); assertSuccess(results);'
+results = runtests(pwd,'Tag','$TEST_TAG'); assertSuccess(results);
 ```
 
 **Note:**
@@ -230,7 +230,7 @@ When you use the `runMATLABCommand` step, all of the required files must be on t
 
 ### Use the runMATLABTests Step
 
-Use the `runMATLABTests` step in your Pipeline to run the tests in your MATLAB project and generate artifacts. By default, MATLAB includes any files in your project that have a `Test` label. If your Pipeline does not leverage a MATLAB project or uses a MATLAB release before R2019a, then MATLAB includes all tests in the the root of your repository, including its subfolders.
+Use the `runMATLABTests` step in your Pipeline to run the tests in your MATLAB project and generate artifacts. By default, MATLAB includes any files in your project that have a `Test` label. If your Pipeline does not leverage a MATLAB project or uses a MATLAB release before R2019a, then MATLAB includes all tests in the root of your repository, including its subfolders.
 
 For example, in your `Jenkinsfile`, define a Declarative Pipeline to run the tests in your project and fail the build if any of the tests fails.