Acrolinx

Author: ghogen

docs/msbuild/errors/msb3823.md

@@ -34,7 +34,7 @@ This article describes the MSB3823 error code.
 -->
 ## Description
 
-There is a difference in how non-string resources are serialized and deserialized between .NET Framework and .NET Core. In .NET Framework applications, resources are both deserialized and then preserialized, which is not efficient but was meant to handle diverse serialization and deserialization techniques. In .NET Core, the extra steps are avoided. However, you can also opt-in to preserialization for .NET Framework projects, by setting the property mentioned in the error message.
+There's a difference in how nonstring resources are serialized and deserialized between .NET Framework and .NET Core. In .NET Framework applications, resources are both deserialized and then preserialized, which isn't efficient, but was meant to handle diverse serialization and deserialization techniques. In .NET Core, the extra steps are avoided. However, you can also opt in to preserialization for .NET Framework projects, by setting the property mentioned in the error message.
 
 ## Resolution
 

docs/msbuild/errors/msb3825.md

@@ -34,13 +34,13 @@ 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, is not 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 .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.
 
-.NET 9 handles BinaryFormatter using a secure algorithm, so there is no issue when using .NET 9.
+.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, and your app won't be exposed to the security risk if it uses `BinaryFormatter`.
 
 For .NET 8 and earlier, see the [migration guide](https://aka.ms/binaryformatter-migration-guide) for alternatives to `BinaryFormatter`.