Apply suggestions from code review

Co-authored-by: Sean Killeen <SeanKilleen@gmail.com>

Author: OsirisTerje

docs/articles/nunit/writing-tests/attributes/notests.md

@@ -63,25 +63,25 @@ Use `TestStatus.Inconclusive` when empty test cases indicate an indeterminate st
 
 ## Common Scenarios
 
-### Dynamic test data
+### Dynamic Test Data
 
 Typical when test cases come from a source that can legitimately be empty (a database, API, config file, or similar).
 
 [!code-csharp[NoTestsDynamicData](~/snippets/Snippets.NUnit/Attributes/NoTestsAttributeExamples.cs#NoTestsDynamicData)]
 
-### Conditional execution
+### Conditional Execution
 
 Typical when cases are only produced for some platforms, environments, or other prerequisites.
 
 [!code-csharp[NoTestsConditionalExecution](~/snippets/Snippets.NUnit/Attributes/NoTestsAttributeExamples.cs#NoTestsConditionalExecution)]
 
-### Feature flags
+### Feature Flags
 
 Typical when data-driven cases depend on feature flags or rollout state and may sometimes yield none.
 
 [!code-csharp[NoTestsFeatureFlag](~/snippets/Snippets.NUnit/Attributes/NoTestsAttributeExamples.cs#NoTestsFeatureFlag)]
 
-## Scope precedence
+## Scope Precedence
 
 * **Assembly** — parameterized tests across the assembly
 * **Fixture (class)** — parameterized tests in that fixture

docs/articles/nunit/writing-tests/attributes/onetimeteardown.md

@@ -24,7 +24,7 @@ With [`FixtureLifeCycle(LifeCycle.InstancePerTestCase)`](xref:fixturelifecycleat
 once after all tests despite each case having its **own** instance; instance teardown belongs in [`TearDown`](xref:teardown-attribute)
 per test instead.
 
-Methods may be **async** (`Task` / `Task<T>`): NUnit will wait for completion.
+Methods may be **async** (`Task` / `Task<T>`); NUnit will wait for completion.
 
 ## Test fixture versus SetUp fixture