Tweaks

Author: ghogen

docs/msbuild/errors/msb1060.md

@@ -45,7 +45,7 @@ This article describes the MSB1060 error code.
 
 There are two errors that can give this error code. The first relates to the `-warnNotAsError` (or the short form `-noerr`) command-line switch. See [MSBuild command line reference](../msbuild-command-line-reference.md). The error is shown when the `-warnNotAsError` (or `-noerr`) switch is used, but no error codes were given. The switch is expected to be followed by a list of error codes, separated by a semicolon or comma. For example:
 
-`msbuild.exe -err -noerr MSB3187;MSBxxxx`
+`msbuild.exe -err -noerr MSB3187;MSB3243`
 
 The other error condition that gives this code is when a response file (`.rsp` file) contains an environment variable name, but the environment variable didn't exist or has no value.
 

docs/msbuild/errors/msb3825.md

@@ -34,17 +34,15 @@ This article describes the MSB3825 warning code.
 -->
 ## Description
 
-This warning occurs with .NET 8 and earlier. The .NET type <xref:BinaryFormatter>, previously commonly used for serializing and deserializing arbitrary .NET types, isn't considered secure, because it allows arbitrary .NET types to be injected into an assembly via the deserialization process.
+This warning occurs with .NET 8 and earlier. The deprecated .NET type <xref:System.Runtime.Serialization.Formatters.Binary.BinaryFormatter>, previously commonly used for serializing and deserializing arbitrary .NET types, isn't considered secure, because it allows arbitrary .NET types to be injected into an assembly via the deserialization process.
 
 .NET 9 handles BinaryFormatter using a secure algorithm, so there's no issue when using .NET 9.
 
 ## Resolution
 
-If you upgrade to .NET 9, you won't get this warning, and your app won't be exposed to the security risk if it uses `BinaryFormatter`.
+If you upgrade to .NET 9, you won't get this warning, but you'll have to implement another solution if your code uses `BinaryFormatter`. See the [migration guide](https://aka.ms/binaryformatter-migration-guide) for alternatives to `BinaryFormatter`.
 
-For .NET 8 and earlier, see the [migration guide](https://aka.ms/binaryformatter-migration-guide) for alternatives to `BinaryFormatter`.
-
-You can also suppress the warning either by setting the `GenerateResourceWarnOnBinaryFormatterUse` property to false, as mentioned in the message, or by setting the `$(NoWarn)` property to a property group in your project file, as follows:
+For .NET 8 and earlier, you can suppress the warning either by setting the `GenerateResourceWarnOnBinaryFormatterUse` property to false, as mentioned in the message, or by setting the `$(NoWarn)` property to a property group in your project file, as follows:
 
 ```xml
 <PropertyGroup>