Eliminating legacy links vol2

Signed-off-by: mrgarris0n <[email protected]>

Author: mrgarris0n

_includes/doc/admin-guide/http-batch.md

@@ -1,2 +1,2 @@
 For details on how this option influences HTTP batch mode, see 
-[[this chapter | adm-dest-http-nonjava-batch]]
+[[this chapter|adm-dest-http-nonjava-batch]]

_includes/doc/admin-guide/options/trim-large-messages.md

@@ -30,4 +30,4 @@ drivers ignore the trim-large-messages() option.
 
 Available in syslog-ng OSE version 3.21 and later.
 
-Uses the value of the [[global option]] if not specified.
+Uses the value of the global option if not specified.

_includes/doc/admin-guide/options/ts-format.md

@@ -11,5 +11,5 @@ ts-format() parameter) for the specific destination. For details, see
 Destinations that use specific protocols (for example, network(), or
 syslog()) ignore this option. For protocol-like destinations, use a
 template locally in the destination, or use the
-[[proto-template]] option.
+proto-template() option.
 {: .notice--info}

doc/_admin-guide/020_The_concepts_of_syslog-ng/009_Structuring_macros/000_Specifying_data_types.md

@@ -15,8 +15,7 @@ description: >-
 From syslog-ng OSE version 4.0 onwards, name-value pairs are now
 triplets (name, type, value). Typing support is available for several
 other components, for example, json-parser() and the $(format-json)
-template function. For more information, see [[Components supported by
-data types]].
+template function. For more information, see Components supported by data types.
 
 ![]({{ site.baseurl}}/assets/images/caution.png)
 **CAUTION:** Hazard of data loss!  
@@ -111,8 +110,7 @@ destination.
 Elements without type data are handled as strings.
 
 JSON lists (arrays) are converted to syslog-ng OSE lists, and can be
-manipulated using the [[list-append]]
-template functions.  
+manipulated using the $(list-append) template functions.  
 
 ### set() and groupset() rewrite rules
 

doc/_admin-guide/050_The_configuration_file/007_Managing_complex_syslog-ng_configurations/001_Reusing_config_blocks.md

@@ -222,7 +222,7 @@ source s_example {
 ### Example: Using arguments in blocks
 
 The following example is the code of the
-[[pacct() source driver]], which is actually a block that
+[[pacct() source driver|adm-src-pacct]], which is actually a block that
 can optionally receive two arguments.
 
 ```config

doc/_admin-guide/060_Sources/200_systemd-syslog/README.md

@@ -10,7 +10,7 @@ description: >-
 Note the following points about this driver:
 
 - If possible, use the more reliable
-    [[systemd-journal()]] driver instead.
+    [[systemd-journal() driver|adm-src-systemd-journal]] instead.
 
 - The socket activation of systemd is buggy, causing some log messages
     to get lost during system startup.

doc/_admin-guide/060_Sources/220_unix-stream_unix-dgram/000_Unix_credentials.md

@@ -10,7 +10,7 @@ description: >-
 The syslog-ng OSE application can extract the following information on 
 Linux and FreeBSD platforms (examples show the value of the macro for the `su - myuser`
 command). Similar information is available for the
-[[systemd-journal source]].  
+[[systemd-journal source|adm-src-systemd-journal]].  
 
 | Macro             | Description                                     |
 |---|---|

doc/_admin-guide/070_Destinations/050_Graphite/README.md

@@ -47,5 +47,5 @@ destination d_graphite { graphite(payload("--key monitor.*")); };
 **NOTE:** The graphite() destination is only a wrapper around the network()
 destination and the graphite-output template function. If you want to
 fine-tune the TCP parameters, use the **network()** destination instead,
-as described in [[graphite-output]].
+as described in $(graphite-output).
 {: .notice--info}