Update blog/_posts/2021-10-21-scala-3.1.0-released.md

Co-authored-by: Julien Richard-Foy <julien@richard-foy.fr>

Author: Kordyjan

blog/_posts/2021-10-21-scala-3.1.0-released.md

@@ -16,7 +16,7 @@ This is a first *minor* release after the initial release of Scala 3.0. This has
 
 Although we cannot guarantee full source compatibility between minor versions, we have put a lot of effort into assuring that all code that was working in 3.0.2, except some rare cases, will also work in 3.1.0. This means that if you are an application developer, you can confidently update the compiler version to take advantage of the newest improvements.
 
-If you are a library maintainer, *updating to 3.1.0 will force all of your users to need to update as well*. You may consider still publishing your library using 3.0.2 to ensure that users who are reluctant to update a compiler can still use it. On the other hand, we still encourage you to test your library using 3.1.0. We understand that the current state of binary compatibility may be unsatisfactory for library maintainers. We are actively working on improvements in this area in future releases of Scala. We are taking the problem of forward-compatibility seriously, and we will provide a technical solution for 3.2.0
+If you are a library maintainer, *updating to 3.1.0 will force all of your users to update to 3.1.0 as well*. We understand that the current state of binary compatibility may be unsatisfactory. We are actively working on technical solutions to support forward-compatibility in 3.2.0. In the meantime, we recommend testing your library with Scala 3.1.0 and 3.0.2, but _publishing_ it with 3.0.2. This will allow downstream users to use your library even if they can’t update to Scala 3.1.0. You can find an example of build that follows this recommendation [here](https://github.com/typelevel/scalacheck/pull/847).
 
 ## What's new in 3.1