wording improvements

Author: jstedfast

docs/modeling/customizing-file-storage-and-xml-serialization.md

@@ -251,11 +251,11 @@ We recommend that you study the code in **Dsl\Generated Code\Serializer.cs** and
 1. Override methods in Dsl\GeneratedCode\SerializationHelper.cs
 
 > [!NOTE]
-> Starting with Visual Studio 2022 17.13, the default serialization implementation will no longer support the serialization or deserialization of custom data types using BinaryFormatter due to [security risks with BinaryFormatter](/dotnet/standard/serialization/binaryformatter-security-guide).
+> Starting with Visual Studio 2022 17.13, the default serialization implementation no longer supports the serialization or deserialization of custom data types using BinaryFormatter due to [security risks with BinaryFormatter](/dotnet/standard/serialization/binaryformatter-security-guide).
 >
 > If you use a custom data type for any domain properties, you need to either override the serialization methods in the `SerializationHelper` class, or implement a `TypeConverter` capable of converting each custom data type to and from a string.
 >
-> To maintain backward compatibility with models that use `BinaryFormatter` serialization, you can implement a `TypeConverter` that deserializes the binary data. The following code snippet serves as a template for implementing this compatibility:
+> While we do not recommend using `BinaryFormatter` for security reasons, if you must maintain backward compatibility with older models that used `BinaryFormatter` serialization, you can implement a `TypeConverter` that deserializes the binary data. The following code snippet serves as a template for implementing this compatibility:
 
 ```csharp
 class MyCustomDataTypeConverter : TypeConverter