Two small clarifications

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 on scala.
+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 on scala.
 
 ## What's new in 3.1
 
@@ -83,7 +83,7 @@ case class Middle() extends Top with Bottom
 sealed trait Bottom extends Top
 ```
 
-Previously you would not be able to summon an instance of `scala.deriving.Mirror.SumOf` for `Top`, as its child `Bottom` is also sealed. In Scala 3.1 this is now possible, enabling compiletime reflection over nested hierarchies of sealed types.
+Previously you would not be able to summon an instance of `scala.deriving.Mirror.SumOf` for `Top`, as its child `Bottom` is not a case class. In Scala 3.1 this is now possible, enabling compiletime reflection over nested hierarchies of sealed types.
 
 The only change necessary for users is that you should now consider that one of the `MirroredElemTypes` for a `Mirror.SumOf` could also be a sum type, not just product types.