Reword documentation sections

Author: acogoluegnes

src/docs/asciidoc/overview.adoc

@@ -91,12 +91,19 @@ The next section provides more details about the evolution of programming interf
 [[stability-of-programming-interfaces]]
 == Stability of Programming Interfaces
 
-The RabbitMQ Stream Java Client is in active development but its programming interfaces will remain as stable as possible. There is no guarantee though that they will remain completely stable, at least until it reaches version 1.0.0.
+The RabbitMQ Stream Java Client is in active development but its programming interfaces will remain as stable as possible.
+There is no guarantee though that they will remain completely stable, at least until it reaches version 1.0.0.
 
 The client contains 2 sets of programming interfaces whose stability are of interest for application developers:
 
-* Application Programming Interfaces (API): those are the ones used to write application logic. They include the interfaces and classes in the `com.rabbitmq.stream` package (e.g. `Producer`, `Consumer`, `Message`). These API constitute the main programming model of the client and will be kept as stable as possible.
-* Service Provider Interfaces (SPI): those are interfaces to implement mainly technical behavior in the client. They are not meant to be used to implement application logic. Application developers may have to refer to them in the configuration phase and if they want to custom some internal behavior in the client. SPI include interfaces and classes in the `com.rabbitmq.stream.codec`, `com.rabbitmq.stream.compression`, `com.rabbitmq.stream.metrics` packages, among others. _These SPI are susceptible to change, but this should not impact the majority of applications_, as the changes would typically stay intern to the client.
+* Application Programming Interfaces (API): those are the ones used to write application logic.
+They include the interfaces and classes in the `com.rabbitmq.stream` package (e.g. `Producer`, `Consumer`, `Message`).
+These API constitute the main programming model of the client and will be kept as stable as possible.
+* Service Provider Interfaces (SPI): those are interfaces to implement mainly technical behavior in the client.
+They are not meant to be used to implement application logic.
+Application developers may have to refer to them in the configuration phase and if they want to customize some internal behavior of the client.
+SPI include interfaces and classes in the `com.rabbitmq.stream.codec`, `com.rabbitmq.stream.compression`, `com.rabbitmq.stream.metrics` packages, among others.
+_These SPI are susceptible to change, but this should have no impact on most applications_, as the changes are likely to be limited to the client internals.
 
 == Pre-requisites