Change log code pages formatting for problems (#3327)

Author: nkolev92

docs/reference/errors-and-warnings/NU1001.md

@@ -12,7 +12,7 @@ f1_keywords:
 
 # NuGet Error NU1001
 
-<pre>The project 'Project' does not specify any target frameworks in 'ProjectFile'</pre>
+> The project 'Project' does not specify any target frameworks in 'ProjectFile'
 
 ### Issue
 The project doesn't contain one or more frameworks.

docs/reference/errors-and-warnings/NU1002.md

@@ -12,7 +12,7 @@ f1_keywords:
 
 # NuGet Error NU1002
 
-<pre>'CLEAR' cannot be used in conjunction with other values</pre>
+> 'CLEAR' cannot be used in conjunction with other values
 
 ### Issue
 Invalid combination of inputs along with a CLEAR keyword.

docs/reference/errors-and-warnings/NU1003.md

@@ -12,7 +12,7 @@ f1_keywords:
 
 # NuGet Error NU1003
 
-<pre>PackageTargetFallback and AssetTargetFallback cannot be used together. Remove PackageTargetFallback(deprecated) references from the project environment.</pre>
+> PackageTargetFallback and AssetTargetFallback cannot be used together. Remove PackageTargetFallback(deprecated) references from the project environment.
 
 ### Issue
 `PackageTargetFallback` and `AssetTargetFallback` provide different behavior for selecting assets and cannot be used together.

docs/reference/errors-and-warnings/NU1004.md

@@ -13,8 +13,8 @@ f1_keywords:
 
 ## Scenario 1
 
-<pre>The project target frameworks are different than the lock file's target frameworks. Lock file target frameworks: net6.0,net5.0. Project target frameworks net6.0.
-The packages lock file is inconsistent with the project dependencies so restore can't be run in locked mode. Disable the RestoreLockedMode MSBuild property or pass an explicit --force-evaluate option to run restore to update the lock file.</pre>
+> The project target frameworks are different than the lock file's target frameworks. Lock file target frameworks: net6.0,net5.0. Project target frameworks net6.0.
+The packages lock file is inconsistent with the project dependencies so restore can't be run in locked mode. Disable the RestoreLockedMode MSBuild property or pass an explicit --force-evaluate option to run restore to update the lock file.
 
 ### Issue
 
@@ -30,8 +30,8 @@ Consult the recommendations in the error message and do one of the following:
 
 ## Scenario 2
 
-<pre>The package reference Contoso.Library version has changed from [2.0.0, ) to [1.2.3, ).The packages lock file is inconsistent with the project dependencies so restore can't be run
- in locked mode. Disable the RestoreLockedMode MSBuild property or pass an explicit --force-evaluate option to run restore to update the lock file.</pre>
+> The package reference Contoso.Library version has changed from [2.0.0, ) to [1.2.3, ).The packages lock file is inconsistent with the project dependencies so restore can't be run
+ in locked mode. Disable the RestoreLockedMode MSBuild property or pass an explicit --force-evaluate option to run restore to update the lock file.
 
 ### Issue
 

docs/reference/errors-and-warnings/NU1005.md

@@ -13,7 +13,7 @@ f1_keywords:
 
 ## Scenario 1
 
-<pre>Invalid restore input where RestorePackagesWithLockFile property is set to false but a packages lock file exists at C:\SourceCode\ContosoProject\Contoso.Library\packages.lock.json</pre>
+> Invalid restore input where RestorePackagesWithLockFile property is set to false but a packages lock file exists at C:\SourceCode\ContosoProject\Contoso.Library\packages.lock.json
 
 ### Issue
 
@@ -27,7 +27,7 @@ There are 2 opt-in methods the lock file functionality, by setting the RestorePa
 
 ## Scenario 2
 
-<pre>RestoreForceEvaluate should not be used with RestoreLockedMode in the same command.</pre>
+> RestoreForceEvaluate should not be used with RestoreLockedMode in the same command.
 
 ### Issue
 

docs/reference/errors-and-warnings/NU1006.md

@@ -11,7 +11,7 @@ f1_keywords:
 
 # NuGet Error NU1006
 
-<pre>NuGet.Config has an invalid package source value 'C:\PackageSource>\'. Reason: Illegal characters in path.</pre>
+> NuGet.Config has an invalid package source value 'C:\PackageSource>\'. Reason: Illegal characters in path.
 
 ### Issue
 

docs/reference/errors-and-warnings/NU1007.md

@@ -11,8 +11,8 @@ f1_keywords:
 
 # NuGet Error NU1007
 
-<pre>The runtime.json specified in the project 'C:\Program Files\dotnet\sdk\X.Y.Z00\RuntimeIdentifierGraph.json
-' could not be parsed.</pre>
+> The runtime.json specified in the project 'C:\Program Files\dotnet\sdk\X.Y.Z00\RuntimeIdentifierGraph.json
+' could not be parsed.
 
 ### Issue
 

docs/reference/errors-and-warnings/NU1008.md

@@ -11,7 +11,7 @@ f1_keywords:
 
 # NuGet Error NU1008
 
-<pre>Projects that use central package version management should not define the version on the PackageReference items but on the PackageVersion items: PackageId.</pre>
+> Projects that use central package version management should not define the version on the PackageReference items but on the PackageVersion items: PackageId.
 
 ### Issue
 

docs/reference/errors-and-warnings/NU1009.md

@@ -11,8 +11,7 @@ f1_keywords:
 
 # NuGet Error NU1009
 
-<pre>The packages PackageId are implicitly referenced. You do not typically need to reference them from your project or in your central package versions management file. For more inform
-ation, see https://aka.ms/sdkimplicitrefs</pre>
+> The packages PackageId are implicitly referenced. You do not typically need to reference them from your project or in your central package versions management file. For more information, see https://aka.ms/sdkimplicitrefs
 
 ### Issue
 

docs/reference/errors-and-warnings/NU1010.md

@@ -11,7 +11,7 @@ f1_keywords:
 
 # NuGet Error NU1010
 
-<pre>The PackageReference items PackageId do not have corresponding PackageVersion.</pre>
+> The PackageReference items PackageId do not have corresponding PackageVersion.
 
 ### Issue