docs: doc review comments

docs/src/app/concepts/ConceptsTab.jsx

@@ -50,7 +50,7 @@ turing-validating-security-definitions-during-development-process'}
           <p>
             An SDV pipeline does all the same tasks as any existing CI/CD pipeline, however,
             if an application code change request results in a change to the security definitions
-            required for that application to run an
+            required for that application to run, an
             <strong> approval process </strong>
             is initiated, which&nbsp;
             <strong>must be approved by a Security Admin</strong>

docs/src/app/how/approval-bot/ApprovalBotStep.jsx

@@ -29,7 +29,7 @@ export default function ApprovalBotStep({
           of the SDV workflow.
           <br />
           <br />
-          At this point, there are two open changes requests, one for the app or test code, and one for the
+          At this point, there are two open change requests, one for the app or test code, and one for the
           security baseline, and from the perspective of the SCM tool there is no direct relation between them.
           Additionally, SCM tools currently do not provide the ability for actions in a change request to directly
           affect the status of another change request in a completely different repository.

docs/src/app/how/ci-pipeline/ciPipelineStep.jsx

@@ -2371,7 +2371,7 @@ wk '{gsub(/\\./,"-"); print}'\`
             </li>
 
             <li>
-              If running in an Galasa Ecosystem, build a list of tests to run by&nbsp;
+              If running in a Galasa Ecosystem, build a list of tests to run by&nbsp;
               <a
                 href='https://galasa.dev/docs/cli-command-reference/ecosystem-cli-runs-prepare'
                 target='_blank'

docs/src/app/how/galasa-architecture/GalasaArchitectureStep.jsx

@@ -63,7 +63,7 @@ export default function GalasaArchitectureStep({
           tests are finished running.
           <br />
           <br />
-          This option works well if there is a small number of tests with no requirement to run test in parallel.
+          This option works well if there are a small number of tests with no requirement to run test in parallel.
         </p>
 
         <h3 className='galasa-architecture-step-subheading-inner'>Ecosystem using DSE</h3>

docs/src/app/how/zos-configuration/ZosConfigStep.jsx

@@ -78,8 +78,8 @@ export default function ZosConfigurationStep({
           as this will increase the number of tests that can be ran in parallel.
           <br />
           This is because a user must only be used for one test at a time, to eliminate the risk of capturing
-          &quot;Security noise&quot;, which would be the capturing of security being used by another test using
-          the same user at the same time.
+          &quot;Security noise&quot;, which would be the capturing of security requests from another test
+          using the same user at the same time.
           <br />
           The number of users in the pool should be relative to the amount of tests using the role.
         </p>

docs/src/app/problem/ProblemTab.jsx

@@ -36,7 +36,7 @@ export default function ProblemTab({
             SDV automates and improves the efficiency of identifying required changes to security when changes are
             made to
             CICS applications. This is currently a slow, error prone, and manual process, often leading to
-            application breakages when the application is first ran in an environment with security switched on, which
+            application breakages when the application is first run in an environment with security switched on, which
             is more common than not, pre-production!
           </p>
           <br />