syslog-ng name variables in doc guide

Signed-off-by: mrgarris0n <gergely.karacsonyi@gmail.com>

Author: mrgarris0n

doc/_doc-guide/02_Tools/01_Self_made_tools/01_Tests/README.md

@@ -24,7 +24,7 @@ macro in the destination definition.
 {: .notice--info}
 
 To parse non-syslog messages, for example, JSON, CSV, or other messages,
-you can use the built-in parsers of syslog-ng OSE. For details, see
+you can use the built-in parsers of {{ site.product.short_name }}. For details, see
 [[parser: Parse and segment structured messages]].
 
 `multi line backticked
@@ -33,10 +33,10 @@ text`
 Soft macros (sometimes also called name-value pairs) are either
 built-in macros automatically generated from the log message (for
 example, ${HOST}), or custom user-created macros generated by using
-the syslog-ng pattern database or a CSV-parser. The SDATA fields of
+the {{ site.product.short_name }} pattern database or a CSV-parser. The SDATA fields of
 RFC-5424 formatted log messages become soft macros as well. In
 contrast with hard macros, soft macros are writable and can be
-modified within syslog-ng OSE, for example, using rewrite rules.
+modified within {{ site.product.short_name }}, for example, using rewrite rules.
 
 **WARNING:** \{: .notice--warning\} Test \
 for the list of hard and soft macros, see [[Hard versus soft macros]].  
@@ -63,7 +63,7 @@ options {
 
 ---------------------
 
-Introduction to syslog-ng is a test for pages without description/subtitle, but text part between the title and the first heading which can have tooltips too this way.
+Introduction to {{ site.product.short_name }} is a test for pages without description/subtitle, but text part between the title and the first heading which can have tooltips too this way.
 
 Developer guide is a double (page title amd section heading) example with a description/subtitle.
 
@@ -75,7 +75,7 @@ Test of forced link with anchored ID part [[Install Homebrew|dev-inst-macos#home
 
 1. Same test like above in an enumeration [[Install Homebrew|dev-inst-macos#homebrew]].
 
-**Hint:** Same again in a notice block [[Install Homebrew|dev-inst-macos#homebrew]]. If you you have syslog-ng [[installed via brew|dev-inst-macos#installation]], as a reference, you can check the dependencies of the brew built version using `brew deps syslog-ng`
+**Hint:** Same again in a notice block [[Install Homebrew|dev-inst-macos#homebrew]]. If you you have {{ site.product.short_name }} [[installed via brew|dev-inst-macos#installation]], as a reference, you can check the dependencies of the brew built version using `brew deps syslog-ng`
 {: .notice--info}
 
 Embedded [link test](https://grpc.io/docs/guides/keepalive/) from a different domain
@@ -155,19 +155,18 @@ For details, see [[The syslog-ng.conf manual page]].
 
 [[The syslog-ng.conf manual page]]
 
-[[The syslog-ng manual page]]
+[[The {{ site.product.short_name }} manual page]]
 
 Here comes an include doc/admin-guide/manpages-footnote.md test
 {% include doc/admin-guide/manpages-footnote.md %}
 
 When encoding is set in a source (using the encoding() option) and the
 message is longer (in bytes) than log-msg-size() in UTF-8
-representation, syslog-ng OSE splits the message at an undefined
+representation, {{ site.product.short_name }} splits the message at an undefined
 location (because the conversion between different encodings is not
 trivial).
 
-The following is a simple configuration file for syslog-ng Open
-Source Edition that collects incoming log messages and stores them
-in a text file. syslog-ng Open Source Edition.
+The following is a simple configuration file for {{ site.product.name }}  that collects incoming log messages and stores them
+in a text file. {{ site.product.name }}.
 
 Aliast testing e.g ${LEVEL} or ${PRIORITY} should work like ${SDATA}

doc/_doc-guide/README.md

@@ -13,10 +13,10 @@ id: doc-guide
  5. If you modify a file in the `_includes/doc/` directory, it is probably included to multiple parts of the documentation. Make sure that your changes make sense in each context.
  6. Modify the files as you need (following our markup conventions). For example, you can add new examples, correct typos, and so on.
  7. Validate the files to make sure that the `markdown` is well-formed.
- 8. Commit and sign off your changes. If your changes apply only to syslog-ng OSE, begin the commit message with the `ose` prefix. If the changes apply only to specific versions, indicate them in the tag, for example, `ose 3.35`
+ 8. Commit and sign off your changes. If your changes apply only to {{ site.product.short_name }}, begin the commit message with the `ose` prefix. If the changes apply only to specific versions, indicate them in the tag, for example, `ose 3.35`
  9. Push your changes, for example, `git push origin my-typo-fixes`
  10. Submit a pull request.
- 11. Sign the syslog-ng Open Source Edition Documentation Contributor License Agreement when prompted.
+ 11. Sign the {{ site.product.name }} Documentation Contributor License Agreement when prompted.
  12. We will review your contribution and if accepted, integrate to the master branch of the documentation and publish it.
 
 ## Basic rules, conventions we try to follow