Fix NU1901 critical severity typo (#3200)

Author: zivkan

docs/reference/errors-and-warnings/NU1901-NU1904.md

@@ -39,15 +39,15 @@ Upgrading to a newer version of the package is likely to resolve the warning.
 You can check the URL provided by the vulnerability advisory to see what versions of the package have been fixed, or check your configured package source(s) to see what versions of the package are available.
 Visual Studio's package manager UI can show which package versions are affected and which do not have known vulnerabilities.
 
-If you do not wish to be notified of vulnerabilities that are less severe than a level you are comfortable with, you can edit the project file and add an MSBuild property `NuGetAuditLevel`, with value set to `low`, `moderate`, `high`, or `severe`.
+If you do not wish to be notified of vulnerabilities that are less severe than a level you are comfortable with, you can edit the project file and add an MSBuild property `NuGetAuditLevel`, with value set to `low`, `moderate`, `high`, or `critical`.
 For example, `<NuGetAuditLevel>high</NuGetAuditLevel>`.
 
 If these warnings are causing restore to fail because you are using `TreatWarningsAsErrors`, you can add `<WarningsNotAsErrors>NU1901;NU1902;NU1903;NU1904</WarningsNotAsErrors>` to allow these codes to remain as warnings.
 
 If you do not want NuGet to check for packages with known vulnerabilities during restore, add `<NuGetAudit>false</NuGetAudit>` inside a `<PropertyGroup>` in your project file, or a [`Directory.Build.props` file](/visualstudio/msbuild/customize-by-directory).
 
 > [!NOTE]
-> The initial release of NuGetAudit [does not provide a way to suppress specific advisories (URLs)](https://github.com/NuGet/Home/blob/dev/proposed/2022/vulnerabilities-in-restore.md#excluding-advisories).
+> The initial release of NuGetAudit [does not provide a way to suppress specific advisories (URLs)](https://github.com/NuGet/Home/issues/11926).
 > It is a feature we intend on adding based on prioritization of other improvements.
 >
 > As a mitigation, you can add an appropriate `NoWarn` to your `PackageReference` declarations.