Merge pull request #202 from MrAnno/fix-readme

Fix readme

NEWS.md

@@ -3,6 +3,8 @@
 
 We are excited to announce the first [independent release](https://axoflow.com/axosyslog-syslog-ng-fork/) of AxoSyslog.
 
+AxoSyslog is binary-compatible with syslog-ng [[1]](#r1) and serves as a drop-in replacement.
+
 Explore and learn more about the new features in our [release announcement blog post](https://axoflow.com/axosyslog-release-4-8/).
 
 Check out the [AxoSyslog documentation](https://axoflow.com/docs/axosyslog-core/) for all the details.
@@ -132,6 +134,9 @@ elasticsearch-datastream(
   * `s3()`: new metric `syslogng_output_event_bytes_total`
     ([#4958](https://github.com/syslog-ng/syslog-ng/pull/4958))
 
+
+<a id="r1">[1]</a> syslog-ng is a trademark of One Identity.
+
 ## Discord
 
 For a bit more interactive discussion, join our Discord server:

README.md

@@ -15,7 +15,7 @@
 [![Binary packages](https://github.com/axoflow/axosyslog/actions/workflows/packages.yml/badge.svg)](https://github.com/axoflow/axosyslog/actions/workflows/packages.yml)
 
 AxoSyslog started as a syslog-ng [[1]](#r1) fork, branched right after
-syslog-ng v4.8.0 with the following focus:
+syslog-ng v4.7.1 with the following focus:
   * cloud native (containers, helm charts, kubernetes integration),
   * security data tailored parsing and transformation (filterx, app-parser, app-transform, etc)
   * performance (eBPF, memory allocator, etc),
@@ -37,7 +37,7 @@ deployment mechanisms:
   - Helm charts (Kubernetes)
   - packages (deb, rpm, etc)
 
-Once the binaries are deployed, create a configuration file called 
+Once the binaries are deployed, create a configuration file called
 `/etc/syslog-ng/syslog-ng.conf`, which will then be processed by
 the `syslog-ng` process.