typos

Author: lambdageek

docs/workflow/testing/testing-managed-tools.md

@@ -1,24 +1,24 @@
 # Testing managed tools
 
-Managed unit and functional tests for a number of tools are included in the product including the
-compiler for NativeAOT, and the trimmer (illink)
+There are managed unit and functional tests for a number of tools including the
+compiler for NativeAOT (`ILCompiler`), and the trimmer (`illink`).
 
 ## Adding new testsuites
 
-To add new test suite, create a new `.csproj` with a name that ends in `Tests`, such as:
+To add a new test suite, create a new `.csproj` with a name that ends in `Tests`, such as:
 `MyTool.Tests.csproj`.  The property `IsTestProject` will be set by the `Directories.Build.props` in
 the repository root.  The property will, in turn, add references to the xunit package and the
 apropriate test runner.
 
-Now add a `ProjectToBuild` item to `eng/Substes.props` to one of the existing subsets such as
-`clr.toolstests` or add a new subset.
+Now add a `ProjectToBuild` item in `eng/Substes.props` to one of the existing subsets, such as
+`clr.toolstests`, or a new subset.
 
 ## Adding new testsuites to CI
 
 To run the tests in CI, add a new pipeline or add to an exsiting pipeline such as `CLR_Tools_Tests`
 in `eng/pipelines/runtime.yml`.  Update the trigger condition, perhaps by adding a new set of paths
 to `eng/pipelines/common/evaluate-default-paths.yml` in order to run the tests when the tool source
-or the test sources change./
+or the test sources change.
 
 ## Running tests locally