Amended docs to remove ambiguity about MS Roslyn analyzers (#1800)

diff --git a/server/sonar-docs/src/pages/analysis/external-issues.md b/server/sonar-docs/src/pages/analysis/external-issues.md
index fc522ce0482f3b1960fadeb797e28f28671463b9..c65918749802ee111be55b563289d153f66c548b 100644 (file)
--- a/server/sonar-docs/src/pages/analysis/external-issues.md
+++ b/server/sonar-docs/src/pages/analysis/external-issues.md
@@ -42,7 +42,7 @@ Swift|`sonar.swift.swiftLint.reportPaths`|Comma-delimited list of paths to [Swif
 TypeScript|`sonar.typescript.tslint.reportPaths`|Comma-delimited list of paths to [TSLint](https://palantir.github.io/tslint/) reports in JSON format (use `-t json` TSLint option)|
 
 **Notes on external .NET issues**  
-Issues from third-party analyzers are included in the MSBuild output and imported by default into {instance}, so no properties exist to enable that behavior. Instead, properties are available to adjust the import and to _stop_ importing those issues.
+Issues from third-party Roslyn analyzers (including Roslyn analyzers provided by Microsoft) are included in the MSBuild output and imported by default into {instance} so no properties exist to enable that behavior. Instead, properties are available to adjust the import and to _stop_ importing those issues.
 
 Note that Roslyn issues with an *error* severity automatically fail the build, and it is not recommended to run the Scanner for MSBuild's end step if the MSBuild step fails for any reason because it will result in an essentially empty analysis, which will close all outstanding issues in the project.