Remove information on configuring code quality severity from Error List

Author: Mikejo5000

docs/code-quality/in-source-suppression-overview.md

@@ -49,6 +49,7 @@ To suppress violations using the code editor, follow these steps:
 
       :::image type="content" source="media/suppress-diagnostic-from-editor-attribute.png" alt-text="Screenshot that shows in Source (attribute) selection from the Quick Actions Suppress menu." lightbox="media/suppress-diagnostic-from-editor-attribute.png":::
 
+::: moniker range="vs-2019"
 ### Suppress violations using the Error List
 
 To suppress violations using the **Error List** window, follow these steps:
@@ -74,6 +75,7 @@ Diagnostics from live analysis, or IntelliSense, are always up-to-date with curr
    ![Screenshot that shows the Error List source filter.](media/error-list-filter.png)
 
 1. Select the diagnostics you want to suppress and proceed as described previously.
+::: moniker-end
 
 ## Suppress violations using a global suppression file
 
@@ -89,6 +91,7 @@ To suppress violations with a global suppression file by using the code editor,
 
     Visual Studio creates a tab in the code editor containing the new global suppression file.
 
+::: moniker range="vs-2019"
 ### Use a global suppression file from the Error List
 
 To suppress violations with a global suppression file by using the **Error List** window, follow these steps:
@@ -102,6 +105,7 @@ To suppress violations with a global suppression file by using the **Error List*
    ![Screenshot that shows the Preview Changes dialog box with a SuppressMessageAttribute attribute in the suppression file.](media/preview-changes-in-suppression-file.png)
 
 1. Select **Apply** to save the global suppression file.
+::: moniker-end
 
 ## Suppress all current violations
 

docs/code-quality/use-roslyn-analyzers.md

@@ -19,6 +19,14 @@ Each Roslyn analyzer rule, or *diagnostic*, has a default severity and suppressi
 
 ## Severity levels
 
+::: moniker range=">=vs-2022"
+You can configure the severity of analyzer rules in an [EditorConfig file](#set-rule-severity-in-an-editorconfig-file) and from the [light bulb menu](#set-rule-severity-from-the-light-bulb-menu).
+::: moniker-end
+
+::: moniker range="vs-2019"
+In Visual Studio 2019 version 16.3 and later, you can configure the severity of analyzer rules in an [EditorConfig file](#set-rule-severity-in-an-editorconfig-file), from the [light bulb menu](#set-rule-severity-from-the-light-bulb-menu), and from the **Error List** window.
+::: moniker-end
+
 In Visual Studio 2019 version 16.3 and later, you can configure the severity of analyzer rules in an [EditorConfig file](#set-rule-severity-in-an-editorconfig-file), from the [light bulb menu](#set-rule-severity-from-the-light-bulb-menu), and from the **Error List** window.
 
 The following table shows the different severity options that you can configure for a diagnostic:
@@ -53,7 +61,6 @@ You can set the rule severity using any of the following methods:
 ::: moniker range=">=vs-2022"
 - [EditorConfig](#set-rule-severity-in-an-editorconfig-file)
 - [Light bulb menu](#set-rule-severity-from-the-light-bulb-menu)
-- [Error List window](#set-rule-severity-from-the-error-list-window)
 - [Solution Explorer](#set-rule-severity-from-solution-explorer)
 ::: moniker-end
 
@@ -170,6 +177,7 @@ Visual Studio provides a convenient way to configure a rule's severity from the
 
    If you don't already have an EditorConfig file in the project, Visual Studio creates one for you.
 
+::: moniker range=">=vs-2022"
 ### Set rule severity from the Error List window
 
 Visual Studio also provides a convenient way to configure a rule's severity from the error list context menu. Follow these steps:
@@ -183,6 +191,7 @@ Visual Studio also provides a convenient way to configure a rule's severity from
    Visual Studio adds an entry to the EditorConfig file to configure the rule to the requested level.
 
    If you don't already have an EditorConfig file in the project, Visual Studio creates one for you.
+::: moniker-end
 
 ### Set rule severity from Solution Explorer