fixed link to example project and typo

GoogleTestAdapter/VsPackage.GTA/Resources/ReleaseNotes/0.16.0.md

@@ -3,7 +3,7 @@
 Changes within this version:
 
 * enhancement: option *Debugger engine* has new choice *Managed and native*, which allows to debug into managed code also ([#276](https://github.com/csoltenborn/GoogleTestAdapter/issues/276))
-* enhancement: [*settings helper files*](https://github.com/csoltenborn/GoogleTestAdapter#settings_helper_files) allow to provide additional information to GTA at test discovery and execution time ([example project](https://github.com/csoltenborn/GoogleTestAdapter/tree/master/SampleTests/DllProject)). This feature can be used to remove the need for a special configuration file for CI, or to reduce configuration redundancy between project and GTA settings ([#278](https://github.com/csoltenborn/GoogleTestAdapter/issues/278))
+* enhancement: [*settings helper files*](https://github.com/csoltenborn/GoogleTestAdapter#settings_helper_files) allow to provide additional information to GTA at test discovery and execution time ([example project](https://github.com/csoltenborn/GoogleTestAdapter/tree/master/SampleTests/HelperFileTests)). This feature can be used to remove the need for a special configuration file for CI, or to reduce configuration redundancy between project and GTA settings ([#278](https://github.com/csoltenborn/GoogleTestAdapter/issues/278))
 * enhancement: speedup of test discovery. Hint: disabling or uninstalling unnecessary test adapters might also speed up test discovery ([#282](https://github.com/csoltenborn/GoogleTestAdapter/issues/282))
 * enhancement: new options allow better control of GTA output: output modes *None* and *Verbose* have been added, printing timestamp and/or severity can be disabled, output can be tagged with `[GTA]`, and summary of warnings and errors can be disabled ([#283](https://github.com/csoltenborn/GoogleTestAdapter/issues/283))
 * usability: reorganized options. Note that this potentially is a **breaking change**, since some XML options have been renamed; if your settings files happen to use these options, GTA will print a warning and tell you how to adjust them ([#271](https://github.com/csoltenborn/GoogleTestAdapter/issues/271))

README.md

@@ -94,7 +94,7 @@ Note that due to the overriding hierarchy described above, you probably want to
 For reference, see a settings file [AllTestSettings.gta.runsettings](https://raw.githubusercontent.com/csoltenborn/GoogleTestAdapter/master/GoogleTestAdapter/Resources/AllTestSettings.gta.runsettings) containing all available settings, a more realistic solution settings file [SampleTests.gta.runsettings](https://raw.githubusercontent.com/csoltenborn/GoogleTestAdapter/master/SampleTests/SampleTests.gta.runsettings) as delivered with the SampleTests solution, and a user settings file [NonDeterministic.runsettings](https://raw.githubusercontent.com/csoltenborn/GoogleTestAdapter/master/SampleTests/NonDeterministic.runsettings) as used by GTA's end-to-end tests. The syntax of the GTA settings files (excluding the `<RunSettings>` node) is specified by [this schema](https://raw.githubusercontent.com/csoltenborn/GoogleTestAdapter/master/GoogleTestAdapter/TestAdapter/GoogleTestAdapterSettings.xsd).
 
 ##### <a name="settings_helper_files"></a>Settings helper files
-GTA does not provide direct access to VS project settings such as *Project* > *Properties* > *Debugging* > *Environment*. Additionally, when run as NuGet dependency, GTA does not have access to information such as solution dir or Platform/Configuration a test executable has been build with.
+GTA does not provide direct access to VS project settings such as *Project* > *Properties* > *Debugging* > *Environment*. Additionally, when run as NuGet dependency, GTA does not have access to information such as solution dir or Platform/Configuration a test executable has been built with.
 
 To overcome these problems, GTA supports so-called *settings helper files* which provide that information to GTA. Helper files are usually generated as part of the build, e.g. within a post-build event, which might look like this: