Add missing link texts to fields references (#4919)

elastic · Sep 8, 2017 · 9f2795e · 9f2795e
1 parent 01841ce
commit 9f2795e
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 4 deletions.
diff --git a/heartbeat/docs/heartbeat-options.asciidoc b/heartbeat/docs/heartbeat-options.asciidoc
@@ -139,7 +139,7 @@ will be overwritten by the value declared here.
 [[monitor-fields-under-root]]
 ==== `fields_under_root`
 
-If this option is set to true, the custom <<monitor-fields>>
+If this option is set to true, the custom <<monitor-fields,fields>>
 are stored as top-level fields in the output document instead of being grouped
 under a `fields` sub-dictionary. If the custom field names conflict with other
 field names added by Heartbeat, then the custom fields overwrite the other

diff --git a/packetbeat/docs/packetbeat-options.asciidoc b/packetbeat/docs/packetbeat-options.asciidoc
@@ -369,7 +369,7 @@ will be overwritten by the value declared here.
 [float]
 ==== `fields_under_root`
 
-If this option is set to true, the custom <<packetbeat-configuration-flows-fields>>
+If this option is set to true, the custom <<packetbeat-configuration-flows-fields,fields>>
 are stored as top-level fields in the output document instead of being grouped
 under a `fields` sub-dictionary. If the custom field names conflict with other
 field names added by Packetbeat, then the custom fields overwrite the other
@@ -514,7 +514,7 @@ packetbeat.protocols:
 [[packetbeat-fields-under-root]]
 ==== `fields_under_root`
 
-If this option is set to true, the custom <<packetbeat-configuration-fields>>
+If this option is set to true, the custom <<packetbeat-configuration-fields,fields>>
 are stored as top-level fields in the output document instead of being grouped
 under a `fields` sub-dictionary. If the custom field names conflict with other
 field names added by Packetbeat, then the custom fields overwrite the other

diff --git a/winlogbeat/docs/winlogbeat-options.asciidoc b/winlogbeat/docs/winlogbeat-options.asciidoc
@@ -335,7 +335,7 @@ winlogbeat.event_logs:
 [float]
 ==== `event_logs.fields_under_root`
 
-If this option is set to true, the custom <<winlogbeat-configuration-fields>>
+If this option is set to true, the custom <<winlogbeat-configuration-fields,fields>>
 are stored as top-level fields in the output document instead of being grouped
 under a `fields` sub-dictionary. If the custom field names conflict with other
 field names added by Winlogbeat, then the custom fields overwrite the other