Eliminating legacy links vol4

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

doc/_admin-guide/100_TLS-encrypted_message_transfer/003_Password_protected_keys.md

@@ -22,7 +22,7 @@ description: >-
     destination, and you use this destination in a log path that has
     multiple destinations, neither destinations will receive log
     messages until you provide the password. In this cases, always
-    [[use disk-based buffering to avoid data loss]].
+    use disk-based buffering to avoid data loss.
 
 - The path and the filename of the private key cannot contain
     whitespaces.

doc/_admin-guide/100_TLS-encrypted_message_transfer/README.md

@@ -14,7 +14,7 @@ standard syslog protocols, that is, the network() and syslog() drivers,
 for example, to forward log messages between two syslog-ng nodes, or to
 send log data to syslog-ng Store Box or another log server. Other
 destinations that support TLS-encryption are not discussed in this
-chapter (for example, [[http())]]).
+chapter (for example, [[http())|adm-dest-http-nonjava]]).
 {: .notice--info}
 
 TLS uses certificates to authenticate and encrypt the communication, as

doc/_admin-guide/110_Template_and_rewrite/000_Customize_message_format/004_Macros_of_syslog-ng.md

@@ -483,7 +483,7 @@ The week number of the year, prefixed with a zero for the
 first nine weeks of the year. (The first Monday in the year marks the
 first week.)
 
-See also [[ISOWEEK, C_ISOWEEK, R_ISOWEEK, S_ISOWEEK]].
+See also ${ISOWEEK}, ${C_ISOWEEK}, ${R_ISOWEEK}, ${S_ISOWEEK}.
 
 ## ${WEEK_DAY_ABBREV}, ${C_WEEK_DAY_ABBREV}, ${R_WEEK_DAY_ABBREV}, ${S_WEEK_DAY_ABBREV}
 

doc/_admin-guide/120_Parser/005_Parsing_dates/README.md

@@ -15,7 +15,7 @@ the entire template or field. Since by default syslog-ng Open Source
 Edition (syslog-ng OSE) uses the ${MESSAGE} part of the log message,
 parsing will fail, unless the log message contains only a date, but that
 is unlikely, so practically you will have to segment the message (for
-example, using a [[csv-parser()]].
+example, using a [[csv-parser()|adm-parser-csv]].
 You can also use date-parser() to parse dates received in
 a JSON or key-value-formatted log message.
 {: .notice--info}

doc/_admin-guide/120_Parser/023_db_parser/001_Using_pattern_databases/002_Correlating_log_messages.md

@@ -96,5 +96,5 @@ Note the following points about timeout values:
 ```
 
 For details on configuring message correlation, see the
-[[context-id, context-timeout, and context-scope]]
+[[context-id, context-timeout, and context-scope|adm-parser-db-elem-rule#attributes]]
 attributes of pattern database rules.

doc/_admin-guide/120_Parser/023_db_parser/004_The_syslog-ng_patterndb_format/000_patterndb/000_ruleset/002_actions/000_action/README.md

@@ -43,7 +43,7 @@ when a message matching the rule is received.
         the rule is received.
 
   - *timeout*: Execute the action when the correlation timer
-        ([[context-timeout]] of the
+        ([[context-timeout|adm-parser-db-elem-rule#attributes]] of the
         pattern database rule expires. This is available only if actions
         are used together with correlating messages.
 

doc/_admin-guide/120_Parser/023_db_parser/README.md

@@ -1,6 +1,5 @@
 ---
-title: 'db-parser: Process message content with a pattern database
-  (patterndb)'
+title: 'db-parser: Process message content with a pattern database (patterndb)'
 short_title: db-parser
 id: adm-parser-db
 ---

doc/_admin-guide/120_Parser/README.md

@@ -32,7 +32,7 @@ parse the messages, or parts of the messages:
 - To parse XML-formatted messages, see [[XML parser]].
 
 - To identify and parse the messages using a pattern database, see
-    [[db-parser: Process message content with a pattern database]].
+    [[db-parser: Process message content with a pattern database (patterndb)]].
 
 - To parse a specially-formatted date or timestamp, see
     [[Parsing dates and timestamps]].

doc/_admin-guide/150_Statistics_of_syslog-ng/000_Metrics_and_counters.md

@@ -60,8 +60,7 @@ The displayed metrics have the following structure.
         To avoid performance issues or even overloading syslog-ng OSE,
         you might want to limit the number of registered dynamic
         counters in the message statistics. To do this, configure the
-        [[stats-max-dynamics()]]
-        global option.
+        max-dynamics() parameter of the stats() global option.
 
     - **o** - This object was once active, but stopped receiving messages.
         (For example, a dynamic object may disappear and become orphan.)
@@ -249,7 +248,7 @@ The displayed metrics have the following structure.
 ## Availability of statistics
 
 Certain statistics are available only if the
-[[stats-level()]] global option is set to a higher value.
+level parameter of stats() global option is set to a higher value.
 
 - Level 0 collects only statistics about the sources and destinations.
 

doc/_admin-guide/150_Statistics_of_syslog-ng/001_Log_statistic_from_internal_source.md

@@ -27,8 +27,7 @@ messages are sent to both destinations.
 
 The statistics include a list of source groups and destinations, as well
 as the number of processed messages for each. You can control the
-verbosity of the statistics using the
-[[stats-level()]] global option.  
+verbosity of the statistics using the level parameter of stats() global option.  
 
 The following is an example output.
 

doc/_admin-guide/190_The_syslog-ng_manual_pages/007_syslog-ng_control_tool.md

@@ -226,7 +226,7 @@ The stats command has the following options:
     >dst.file;#anon-destination0#0;/tmp/2021-08-17.log;o;processed;156
     >dst.file;#anon-destination0#0;/tmp/2021-08-18.log;a;processed;961
 
-    **NOTE:** The [[stats-lifetime()]] can be used to do the same
+    **NOTE:** The stats-lifetime() can be used to do the same
     automatically and periodically, but currently stats-lifetime()
     removes only dynamic counters that have a timestamp field set.
     {: .notice--info}