From 875471a2a00d2afa53e8ad29e8aaa1304832b128 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Amaury=20Lev=C3=A9?= Date: Fri, 26 Jul 2024 10:07:31 +0200 Subject: [PATCH] Apply suggestions from code review Co-authored-by: David Pine --- docs/core/testing/mstest-analyzers/mstest0008.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/core/testing/mstest-analyzers/mstest0008.md b/docs/core/testing/mstest-analyzers/mstest0008.md index 058bab44de3e9..949b5f0c34f68 100644 --- a/docs/core/testing/mstest-analyzers/mstest0008.md +++ b/docs/core/testing/mstest-analyzers/mstest0008.md @@ -42,10 +42,10 @@ Methods marked with `[TestInitialize]` should follow the following layout to be The type declaring these methods should also respect the following rules: -- the type should be a class -- the class should be `public` or `internal` (if the test project is using the `[DiscoverInternals]` attribute) -- the class should not be `static` -- if the class is sealed, it should be marked with `[TestClass]` (or a derived attribute) +- The type should be a `class`. +- The `class` should be `public` or `internal` (if the test project is using the `[DiscoverInternals]` attribute). +- The `class` shouldn't be `static`. +- If the `class` is `sealed`, it should be marked with `[TestClass]` (or a derived attribute). ## How to fix violations