index.asciidoc in logstash-input-udp-3.4.1

- old
+ new

@@ -29,12 +29,13 @@
 [id="plugins-{type}s-{plugin}-ecs_metadata"]
 ===== Event Metadata and the Elastic Common Schema (ECS)
 
 This plugin adds a field containing the source IP address of the UDP packet.
 By default, the IP address is stored in the host field.
-When ECS is enabled (in <<plugins-{type}s-{plugin}-ecs_compatibility>>), the
-source IP address is stored in the [host][ip] field.
+When {ecs-ref}[Elastic Common Schema (ECS)] is enabled (in
+<<plugins-{type}s-{plugin}-ecs_compatibility>>), the source IP address is stored
+in the [host][ip] field.
 
 You can customize the field name using the <<plugins-{type}s-{plugin}-source_ip_fieldname>>.
 See <<plugins-{type}s-{plugin}-ecs_compatibility>> for more information.
 
 
@@ -78,11 +79,12 @@
 ** `v1`: structured connection metadata added under ECS compliant namespaces
 * Default value depends on which version of Logstash is running:
 ** When Logstash provides a `pipeline.ecs_compatibility` setting, its value is used as the default
 ** Otherwise, the default value is `disabled`.
 
-Controls this plugin's compatibility with the https://www.elastic.co/guide/en/ecs/current/index.html[Elastic Common Schema (ECS)].
+Controls this plugin's compatibility with the {ecs-ref}[Elastic Common Schema (ECS)].
+
 The value of this setting affects the placement of a TCP connection's metadata on events.
 
 .Metadata Location by `ecs_compatibility` value
 [cols="<l,<l,e,<e"]
 |=======================================================================
@@ -140,10 +142,10 @@
 
 Example:
 [source,ruby]
     input {
       udp {
-        source_ip_fieldname => "[appliace][monitoring][ip]"
+        source_ip_fieldname => "[appliance][monitoring][ip]"
       }
     }
 
 [id="plugins-{type}s-{plugin}-workers"]
 ===== `workers` 