Update TESTING.md (#610)

TESTING.md

@@ -2,15 +2,9 @@
 
 ## Introduction
 
-### When to use this article
-
 - Before we release Microsoft.Identity.Web project templates (usually for each release of Microsoft.Identity.Web), we want to make sure that we test them from the release build.
 - Before we commit changes in the project templates (under ProjectTemplates\templates) in the Microsoft.Identity.Web repo, we want to make sure that we test them in depth from the repo. Changes can be changes of major versions of package references of Microsoft.Identity.Web, sync from ASP.NET Core templates. This can also help detecting product bugs so we can do the same before releases of Microsoft.Identity.Web.
 
-### When not to use this article
-
-There is another article, explaining how to test templates from a NuGet package generated by ASP.NET Core team: How to test the ASP.NET core templates before they release.
-
 ## Principle
 
 In this article you will:
@@ -120,8 +114,8 @@ Once the projects are generated from the templates, test them manually.
 Test each project in the solution:
 
 - Starting by the no-auth (we don't want to break this scenario)
-- Then the AAD simple, AAD with Graph, and AAD with web API (the API is really graph so no need to start a web API)
+- Then the AAD simple, AAD with Microsoft Graph, and AAD with web API (the API is really Microsoft Graph so no need to start a web API)
 - Then the B2C simple templates
 - To test the B2C-calls-web-api templates, you'll need to run the TodoListService of the B2CWebAppCallsWebApi test app in the Microsoft.Identity.Web solution
   - Note that we could do with testing the B2C-calls-web-api against the web API deployed in Azure, but testing it against our test project has the interest of enabling debugging
-- To test the web apis templates … TBD …
+- To test the web APIs templates … TBD …