warning and suggestion fixes

Author: chcomley

docs/test/associate-automated-test-with-test-case.md

@@ -87,7 +87,7 @@ See the following frequently asked questions (FAQs).
 * Tests that use the .NET core framework **can** be associated with a test case
   work item when using Visual Studio 15.9 Preview 2 or later.
   Run the .NET core tests. The appropriate target framework must be specified
-  in a [.runsettings file](/visualstudio/test/configure-unit-tests-by-using-a-dot-runsettings-file.md).
+  in a [.runsettings file](/visualstudio/test/configure-unit-tests-by-using-a-dot-runsettings-file?).
   However, these tests can't be run using Microsoft Test Manager and XAML builds.
 * Tests that use other test frameworks such as Chutzpah (for JavaScript tests
   such as Mocha or QUnit), or Jest **cannot** be associated with a test case.

docs/test/run-automated-tests-from-test-hub.md

@@ -228,8 +228,7 @@ test runs in parallel if:
 
 * Testers don't run the same tests in parallel. Doing so might cause results to be overwritten depending on the order of execution.
 
-To enable multiple different test runs to execute in parallel, set the Azure Pipelines stage trigger option for [behavior when multiple releases are waiting to be deployed](../pipelines/release/triggers.md#env-triggers)
-as follows:
+To enable multiple different test runs to execute in parallel, set the Azure Pipelines stage trigger option for [behavior when multiple releases are waiting to be deployed](../pipelines/release/triggers.md) as follows:
 
 * If your application supports tests running in parallel from different sources, set this option to **Allow multiple releases to be deployed at the same time**.