Replace TargetFrameworks with TargetFramework where possible (#66198)

1 files changed, 5 insertions, 5 deletions

diff --git a/docs/coding-guidelines/libraries-packaging.md b/docs/coding-guidelines/libraries-packaging.md
index be1a1c8ae8f..d3cd475bb12 100644
--- a/docs/coding-guidelines/libraries-packaging.md
+++ b/docs/coding-guidelines/libraries-packaging.md
@@ -79,16 +79,16 @@ To include an analyzer in a package, simply add an `AnalyzerReference` item to t
 
 In the analyzer project make sure to do the following. Ensure it only targets `netstandard2.0` since this is a requirement of the compiler. Enable localization by setting `UsingToolXliff`. Set the `AnalyzerLanguage` property to either `cs` or `vb` if the analyzer is specific to that language. By default the analyzer will be packaged as language-agnostic. Avoid any dependencies in Analyzer projects that aren't already provided by the compiler.
 ```xml
-  <PropertyGroup> 
-    <TargetFrameworks>netstandard2.0</TargetFrameworks> 
+  <PropertyGroup>
+    <TargetFramework>netstandard2.0</TargetFramework>
     <UsingToolXliff>true</UsingToolXliff>
-    <AnalyzerLanguage>cs</AnalyzerLanguage> 
+    <AnalyzerLanguage>cs</AnalyzerLanguage>
   </PropertyGroup>
 ```
 
 In order to mitigate design-time/build-time performance issues with source generators, we generate build logic to allow the end user to disable the source generator from the package. By default, the MSBuild property an end user can set is named `Disable{PackageId}SourceGenerator`. If a package needs a custom property name, this can be overriden by setting the following property in the project that produces the package
 ```xml
-  <PropertyGroup> 
-    <DisableSourceGeneratorPropertyName>CustomPropertyName</DisableSourceGeneratorPropertyName> 
+  <PropertyGroup>
+    <DisableSourceGeneratorPropertyName>CustomPropertyName</DisableSourceGeneratorPropertyName>
   </PropertyGroup>
 ```