Eliminating legacy links vol1

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

Author: mrgarris0n

doc/_admin-guide/070_Destinations/100_Kafka-c/002_Flow_control.md

@@ -18,4 +18,4 @@ You can specify a "high water mark" limit for the Kafka client in the
 properties-file().
 
 For more information about how the C implementation of the kafka()
-destination works with syslog-ng OSE, click [[here]].
+destination works with syslog-ng OSE, click [[here|adm-dest-kafkac]].

doc/_admin-guide/070_Destinations/200_Python/README.md

@@ -23,7 +23,7 @@ the second part of the Python destination. The Python class processes
 the log messages it receives, and can do virtually anything that you can
 code in Python. You can either embed the Python class into your
 syslog-ng OSE configuration file, or
-[[store it in an external Python file]].
+[[store it in an external Python file|adm-conf-python]].
 
 ```config
 destination <name_of_the_python_destination>{
@@ -102,9 +102,8 @@ Error handling in the python() destination.
 
 The send method sends a message to the target service. It should return
 True to indicate success, or self.QUEUED when using batch mode. For
-other possible return values, see the description of the [[flush()
-method|adm-dest-python#flushself-method-optional]]. Note that for batch mode, the
-flush() method must be implemented as well.
+other possible return values, see the description of the [[flush() method|adm-dest-python#flushself-method-optional]].
+Note that for batch mode, the flush() method must be implemented as well.
 
 This is the only mandatory method of the destination.
 
@@ -208,7 +207,7 @@ The Python destination handles errors as follows.
 
 The purpose of this example is only to demonstrate the basics of the
 Python destination, if you really want to write log messages into text
-files, use the [[file destination]] instead.
+files, use the [[file destination|adm-dest-file]] instead.
 
 The following sample code writes the body of log messages into the
 /tmp/example.txt file. Only the send() method is implemented, meaning
@@ -273,9 +272,8 @@ class TextDestination(object):
 ```
 
 For a more detailed example about sending log messages to an MQTT
-(Message Queuing Telemetry Transport) server, see the [Writing Python
-destination in syslog-ng: how to send log messages to MQTT blog
-post](https://www.syslog-ng.com/community/b/blog/posts/writing-python-destination-in-syslog-ng-how-to-send-log-messages-to-mqtt).
+(Message Queuing Telemetry Transport) server, see the
+[Writing Python destination in syslog-ng: how to send log messages to MQTT](https://www.syslog-ng.com/community/b/blog/posts/writing-python-destination-in-syslog-ng-how-to-send-log-messages-to-mqtt) blog post.
 
 ### Example: Print logs in batch mode
 
@@ -299,4 +297,4 @@ class MyDestination(object):
 ```
 
 For the list of available optional parameters, see
-[[python() destination options]].
+python() destination options.

doc/_admin-guide/070_Destinations/260_Splunk/000_Splunk-hec-event.md

@@ -72,6 +72,6 @@ destination d_splunk_hec_raw {
 };
 ```
 
-The options of the `splunk-hec-raw()` destination are similar to the [[splunk-hec-event()]] destination, however, the `channel()` option is mandatory. The `channel()` option must be a globally unique channel identifier (GUID), this ID differentiates the data from different clients. Note that Splunk does not generate this ID, you must create it for yourself. When Splunk sees a new channel identifier, it creates a new channel.
+The options of the `splunk-hec-raw()` destination are similar to the [[splunk-hec-event()|adm-dest-splunk-hec-event]] destination, however, the `channel()` option is mandatory. The `channel()` option must be a globally unique channel identifier (GUID), this ID differentiates the data from different clients. Note that Splunk does not generate this ID, you must create it for yourself. When Splunk sees a new channel identifier, it creates a new channel.
 
-Use the `template()` option to set the content of the log message sent to Splunk. Avoid using the `event()` option, that is used in the [[splunk-hec-event()]] destination.
+Use the `template()` option to set the content of the log message sent to Splunk. Avoid using the `event()` option, that is used in the [[splunk-hec-event()|adm-dest-splunk-hec-event]] destination.

doc/_admin-guide/070_Destinations/310_syslog-ng/README.md

@@ -7,7 +7,7 @@ description: >-
     syslog-ng node in EWMM format.
 ---
 
-The [[Enterprise-wide message model (EWMM)]] 
+The [[Enterprise-wide message model (EWMM)]]
 allows you to deliver structured messages from the initial
 receiving syslog-ng component right up to the central log server,
 through any number of hops. It does not matter if you parse the messages
@@ -18,11 +18,12 @@ component in your infrastructure has received it, which is important if
 you want to forward a message for example, to a SIEM system. To make use
 of the enterprise-wide message model, you have to use the syslog-ng()
 destination on the sender side, and the
-[[default-network-drivers() source]] on the receiver side.
+[[default-network-drivers() source|adm-src-def-netw]]
+on the receiver side.
 
 The syslog-ng() destination driver is available in version 3.16 and
 later. The node that receives this message must use the
-[[default-network-drivers() source]]
+[[default-network-drivers() source|adm-src-def-netw]]
 to properly handle the messages.
 
 The following is a sample log message in EWMM format.

doc/_admin-guide/180_Best_practices_and_examples/005_Load_balancing_logs/001_msec_hashing.md

@@ -11,14 +11,14 @@ description: >-
 ![]({{ site.baseurl}}/assets/images/caution.png) **CAUTION:**
 Consider that network-load-balancer() is not a destination, only a script that
 generates the example configuration described in
-[[Load balancing with round robin]].
+[[Load balancing with round robin|adm-pract-round-robin]].
 Also consider that the configuration generator script may change incompatibly
 in the future. As a result, One Identity does not officially support using
 this script, and recommends that you only use this script at your own risk.
 {: .notice--warning}
 
 As an alternative to using the example configuration described in
-[[Load balancing with round robin]], a
+[[Load balancing with round robin|adm-pract-round-robin]], a
 configuration generator script is also available in syslog-ng OSE:
 
 ```config