[GitHub] [incubator-pekko-connectors] mdedetrich commented on a diff in pull request #22: remove version info from docs and some small doc updates

["mdedetrich (via GitHub)" <gi...@apache.org>]

mdedetrich commented on code in PR #22:
URL: https://github.com/apache/incubator-pekko-connectors/pull/22#discussion_r1095053076


##########
docs/src/main/paradox/other-docs/versioning.md:
##########
@@ -16,27 +16,28 @@ Apache Pekko Connectors publishes
 
 ### Compatibility
 
-Our ambition is to evolve Apache Pekko Connectors modules without breaking users’ code. There are two sides to that: One is **binary-compatibility** which effectively means you can replace just the jar with a later version’s jar in your installation and everything will work. This becomes extremely important as soon as you use other libraries that rely on the same jar. They will continue to work without recompilation. The other is **source-compatibility** which, when upgrading to a later minor version, would not require any code changes. Akka and Apache Pekko Connectors strive for binary-compatibility and source-compatibility, but we do not guarantee source-compatibility.
+Our ambition is to evolve Apache Pekko Connectors modules without breaking users’ code. There are two sides to that: One is **binary-compatibility** which effectively means you can replace just the jar with a later version’s jar in your installation and everything will work. This becomes extremely important as soon as you use other libraries that rely on the same jar. They will continue to work without recompilation. The other is **source-compatibility** which, when upgrading to a later minor version, would not require any code changes. Apache Pekko and Apache Pekko Connectors strive for binary-compatibility and source-compatibility, but we do not guarantee source-compatibility.
 
-Read about the details in the @extref:[Akka documentation](akka:common/binary-compatibility-rules.html). 
+Read about the details in the @extref:[Apache Pekko documentation](pekko:common/binary-compatibility-rules.html). 
 
 
 ### Mixing versions
 
 **All connectors of Apache Pekko Connectors can be used independently**, you may mix Apache Pekko Connectors versions for different libraries. Some may share dependencies which could be incompatible, though (eg. Apache Pekko Connectors connectors to AWS services).
 
 
-### Akka versions
+### Apache Pekko versions
 
-With Akka though, it is important to be strictly using one version (never blend eg. `akka-actor 2.5.21` and `akka-stream 2.5.12`), and do not use an Akka version lower than the one the Apache Pekko Connectors dependency requires (sometimes Apache Pekko Connectors modules depend on features of the latest Akka release).
+With Apache though, it is important to be strictly using one version (never blend eg. `pekko-actor 1.0.21` and `pekko-stream 1.0.12`), and do not use a Pekko version lower than the one the Apache Pekko Connectors dependency requires (sometimes Apache Pekko Connectors modules depend on features of the latest Apache Pekko release).

Review Comment:
   This should be pekko



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org