docs: apply suggestions from review

Author: tgodzik

_posts/2025-02-01-next-scala-lts.md

@@ -7,16 +7,15 @@ by: Tomasz Godzik
 
 **TLDR;**
 
-sun.misc.Unsafe, re-used in lazy val implementation, will be removed in a future
-JDK one of the Scala 3 Next minors in 2025 Q4 and the next LTS will drop JDK 8
-support
+API used in lazy val implementation, will be removed in a future JDK thus one of
+the Scala 3 Next minors in 2025 Q4 and the next LTS will drop JDK 8 support.
 
 ## Intro
 
 For the compiler’s second LTS version, the Scala 3 compiler team will be
 dropping support for JDK 8 and is considering which later JDK to use.
 
-## Reasons for the change
+## Immediate motivation
 
 One of the main reasons is that recent [JEP 471](https://openjdk.org/jeps/471)
 stated that the memory-access methods in sun.misc.Unsafe are scheduled for
@@ -28,18 +27,33 @@ which is being investigated under
 dawn on the compiler team that we might consider stopping to support JDK 8
 altogether in a future release of Scala 3.
 
-## Advantages
+## Long term motivation
 
 Switching to a newer version of the JDK would allow both the compiler and the
-Scala ecosystem to start using new features brought in by JDK 9+. This might
-include a number of JEPs, which will be investigated by the team the coming
-year. To check the current status take a look at the issues marked with the
+Scala ecosystem to start using new features and standard library improvements
+brought in by JDK 9+. This might include a number of JEPs, which will be
+investigated by the team the coming year. To check the current status take a
+look at the issues marked with the
 [JEP label](https://github.com/scala/scala3/issues?q=is%3Aissue+is%3Aopen+label%3Acompat%3Ajava%3Ajep).
 
+Some of the features that might be interesting to the Scala community are:
+
+- [JEP 181](https://github.com/scala/scala3/issues/22292) will allow classes
+  that are logically part of the same code entity, but which are compiled to
+  distinct class files, to access each other's private members without the need
+  for Scala compiler to insert accessibility-broadening bridge methods. This is
+  especially useful for nested classes or companions.
+- [JEP 334](https://github.com/scala/scala3/issues/22294) introduce an API to
+  model nominal descriptions of key class-file and run-time artifacts, which can
+  potentially help improve the internals of Scala 3 compiler.
+- [JEP 471](https://github.com/scala/scala3/issues/9013) which adds a new API
+  for memory access, which can be used to replace the usage of sun.misc.Unsafe
+  in Scala 3.
+
 Another advantage would be reducing the maintenance burden on tooling and
 library authors that currently have to take into account a large number of
 different versions to test and make sure that their code is performant on all of
-them.
+them. Thus, the benefits of this change will be felt ecosystem-wide.
 
 If we take a look at the timeline we'll see that JDK 8 was first published on
 18th March 2014, which is already over 10 years ago. Technology and especially
@@ -71,10 +85,10 @@ If you are using Scala 3 on JDK 8 do let us know! However the current line of
 LTS under 3.3.x will be supported for at least another year after the release of
 the next LTS version, which should give you plenty of time to migrate.
 
-If at any point it turns out it's not possible for you to switch, be sure to
-send us your feedback.
+If it's not possible for you to switch, be sure to send us your feedback so that
+we can figure out a way to help you migrate.
 
-## Summary
+## Discussions and further reading
 
 You can track the current work related to lazy values under
 [this issue](https://github.com/scala/scala3/issues/9013) and discuss the topic