Missing macro annotations

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

Author: mrgarris0n

doc/_admin-guide/110_Template_and_rewrite/000_Customize_message_format/002_Date_related_macros.md

@@ -35,50 +35,50 @@ Rewrite the timezone of a message.
 Converting the timezone changes the values of the following date-related
 macros (macros MSEC and USEC are not changed):
 
-- AMPM
+- ${AMPM}
 
-- DATE
+- ${DATE}
 
-- DAY
+- ${DAY}
 
-- FULLDATE
+- ${FULLDATE}
 
-- HOUR
+- ${HOUR}
 
-- HOUR12
+- ${HOUR12}
 
-- ISODATE
+- ${ISODATE}
 
-- ISOWEEK
+- ${ISOWEEK}
 
-- MIN
+- ${MIN}
 
-- MONTH
+- ${MONTH}
 
-- MONTH_ABBREV
+- ${MONTH_ABBREV}
 
-- MONTH_NAME
+- ${MONTH_NAME}
 
-- MONTH_WEEK
+- ${MONTH_WEEK}
 
-- SEC
+- ${SEC}
 
-- STAMP
+- ${STAMP}
 
-- TZ
+- ${TZ}
 
-- TZOFFSET
+- ${TZOFFSET}
 
-- UNIXTIME
+- ${UNIXTIME}
 
-- WEEK
+- ${WEEK}
 
-- WEEK_DAY
+- ${WEEK_DAY}
 
-- WEEK_DAY_ABBREV
+- ${WEEK_DAY_ABBREV}
 
-- WEEK_DAY_NAME
+- ${WEEK_DAY_NAME}
 
-- YEAR
+- ${YEAR}
 
-- YEAR_DAY
+- ${YEAR_DAY}

doc/_admin-guide/110_Template_and_rewrite/000_Customize_message_format/003_Hard_vs_soft_macros.md

@@ -19,15 +19,15 @@ However, it is not possible to change the values of hard macros in
 rewrite rules or via any other means.
 
 The following macros in {{ site.product.short_name }} are hard macros and cannot be
-modified: BSDTAG, CONTEXT\_ID, DATE, DAY, FACILITY\_NUM, FACILITY,
-FULLDATE, HOUR, ISODATE, ISOWEEK, LEVEL\_NUM, LEVEL, MIN, MONTH\_ABBREV,
-MONTH\_NAME, MONTH, MONTH\_WEEK, PRIORITY, PRI, RCPTID, SDATA, SEC,
-SEQNUM, SOURCEIP, STAMP, TAG, TAGS, TZOFFSET, TZ, UNIXTIME,
-WEEK\_DAY\_ABBREV, WEEK\_DAY\_NAME, WEEK\_DAY, WEEK, YEAR\_DAY, YEAR.
+modified: ${BSDTAG}, ${CONTEXT_ID}, ${DATE}, ${DAY}, ${FACILITY_NUM}, ${FACILITY},
+${FULLDATE}, ${HOUR}, ${ISODATE}, ${ISOWEEK}, ${LEVEL_NUM}, ${LEVEL}, ${MIN}, ${MONTH_ABBREV},
+${MONTH_NAME}, ${MONTH}, ${MONTH_WEEK}, ${PRIORITY}, ${PRI}, ${RCPTID}, ${SDATA}, ${SEC},
+${SEQNUM}, ${SOURCEIP}, ${STAMP}, ${TAG}, ${TAGS}, ${TZOFFSET}, ${TZ}, ${UNIXTIME},
+${WEEK_DAY_ABBREV}, ${WEEK_DAY_NAME}, ${WEEK_DAY}, ${WEEK}, ${YEAR_DAY}, ${YEAR}.
 
-The following macros can be modified:FULLHOST\_FROM, FULLHOST,
-HOST\_FROM, HOST, LEGACY\_MSGHDR, MESSAGE, MSG,MSGID, MSGONLY, PID,
-PROGRAM, SOURCE. Custom values created using rewrite rules or parsers
+The following macros can be modified: ${FULLHOST_FROM}, ${FULLHOST},
+${HOST_FROM}, ${HOST}, ${LEGACY_MSGHDR}, ${MESSAGE}, ${MSG}, ${MSGID}, ${MSGONLY}, ${PID},
+${PROGRAM}, ${SOURCE}. Custom values created using rewrite rules or parsers
 can be modified as well, just like stored matches of regular expressions
 ($0 \... $255).
 

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

@@ -64,15 +64,15 @@ When used, the output specifies the local IP address of the
 source from which the message originates.
 
 For an example use case when using the macro is recommended, see
-[[Example use case: using the ${DESTIP}, the ${DESTPORT}, and the ${PROTO} macros]]
+Example use case: using the ${DESTIP}, the ${DESTPORT}, and the ${PROTO} macros
 
 ## ${DESTPORT}
 
 When used, the output specifies the local port of the
 source from which the message originates.
 
 For an example use case when using the macro is recommended, see
-[[Example use case: using the ${DESTIP}, the ${DESTPORT}, and the ${PROTO} macros]].
+Example use case: using the ${DESTIP}, the ${DESTPORT}, and the ${PROTO} macros.
 
 ## ${FACILITY}
 

doc/_admin-guide/180_Best_practices_and_examples/005_Load_balancing_logs/000_Round_robin.md

@@ -1,19 +1,19 @@
 ---
-title: Load balancing with a round robin load balancing method based on the R_MSEC macro of {{ site.product.short_name }}
+title: Load balancing with a round robin load balancing method based on the ${R_MSEC} macro of {{ site.product.short_name }}
 short_title: Load balancing with round robin
 id: adm-pract-round-robin
 description: >-
   This section describes a round robin load balancing method based on the
-  R_MSEC macro of {{ site.product.short_name }} to load
+  ${R_MSEC} macro of {{ site.product.short_name }} to load
   balance your logs between multiple {{ site.product.short_name }} destinations.
 ---
 
-**TIP:** If R_MSEC is not precise enough, you can replace it with R_USEC
+**TIP:** If ${R_MSEC} is not precise enough, you can replace it with R_USEC
 (which uses microseconds instead of milliseconds).
 {: .notice--info}
 
-For more information about the R_MSEC macro and further macros of
-{{ site.product.short_name }}, see Macros of {{ site.product.short_name }}.
+For more information about the ${R_MSEC} macro and further macros,
+see Macros of {{ site.product.short_name }}.
 
 ## Example: round robin load balancing between multiple destinations
 
@@ -51,7 +51,7 @@ destination d_lb_network {
 
 The filter {\" \<return value \>\" == \"$(% ${R_MSEC} 2)\"}; code
 snippets (in bold) serve as the basis of the method. This filter
-separates incoming log messages\' timestamp values based on the R_MSEC
+separates incoming log messages\' timestamp values based on the ${R_MSEC}
 macro, using a division with remainder method, and distributes the log
 messages equally between two destinations based on the return value (in
 this case, 0 or 1).
@@ -61,5 +61,5 @@ destination with the file in the example (and use the same analogy for
 any other {{ site.product.short_name }} destinations).
 
 For an alternative method to use the round robin load balancing method
-based on the R_MSEC macro, see
+based on the ${R_MSEC} macro, see
 Configuration generator for the load balancing method based on MSEC hashing.