docs: fix broken links (#114)

bmorelli25 · web-flow · commit 546db2156ae0 · 2020-11-23T10:50:20.000-08:00
diff --git a/.gitignore b/.gitignore
@@ -1,3 +1,6 @@
 target
 .idea
 **.iml
+
+# Local doc build files
+html_docs
diff --git a/docs/intro.asciidoc b/docs/intro.asciidoc
@@ -108,7 +108,7 @@ like Logstash, Kafka or Redis.
 *Index Lifecycle management*::
 +
 --
-Leverage Filebeat's default {filebeat-ref}/master/ilm.html[index lifemanagement settings].
+Leverage Filebeat's default {filebeat-ref}/ilm.html[index lifecycle management settings].
 This is much more efficient than using daily indices.
 --
 
diff --git a/docs/setup.asciidoc b/docs/setup.asciidoc
@@ -29,10 +29,7 @@ include::./tab-widgets/ecs-encoder-widget.asciidoc[]
 [[setup-step-2]]
 === Step 2: Enable APM log correlation (optional)
 If you are using the Elastic APM Java agent,
-set {apm-java-ref}/current/config-logging.html#config-enable-log-correlation[`enable_log_correlation`] to `true`.
-
-
-
+set {apm-java-ref}/config-logging.html#config-enable-log-correlation[`enable_log_correlation`] to `true`.
 
 [float]
 [[setup-step-3]]
diff --git a/docs/structured-logging-log4j2.asciidoc b/docs/structured-logging-log4j2.asciidoc
@@ -1,3 +1,4 @@
+[structured-logging-log4j2]
 == Structured logging with log4j2
 
 By leveraging log4j2's `MapMessage` or even by implementing your own `MultiformatMessage` with JSON support,
@@ -56,7 +57,7 @@ In recent Elasticsearch versions, the following JSON structures would result in
 }
 ----
 
-The property `foo` would be mapped to the {ref}/current/object.html[Object datatype].
+The property `foo` would be mapped to the {ref}/object.html[Object datatype].
 
 This means that you can't index a document where `foo` would be a different datatype, as in shown in the following example:
 

Original file line number	Diff line number	Diff line change
`@@ -108,7 +108,7 @@ like Logstash, Kafka or Redis.`
`108`	`108`	`Index Lifecycle management::`
`109`	`109`	`+`
`110`	`110`	`--`
`111`		`-Leverage Filebeat's default {filebeat-ref}/master/ilm.html[index lifemanagement settings].`
	`111`	`+Leverage Filebeat's default {filebeat-ref}/ilm.html[index lifecycle management settings].`
`112`	`112`	`This is much more efficient than using daily indices.`
`113`	`113`	`--`
`114`	`114`
Original file line number	Diff line number	Diff line change
`@@ -1,3 +1,4 @@`
	`1`	`+[structured-logging-log4j2]`
`1`	`2`	`== Structured logging with log4j2`
`2`	`3`
`3`	`4`	By leveraging log4j2's `MapMessage` or even by implementing your own `MultiformatMessage` with JSON support,
`@@ -56,7 +57,7 @@ In recent Elasticsearch versions, the following JSON structures would result in`
`56`	`57`	`}`
`57`	`58`	`----`
`58`	`59`
`59`		-The property `foo` would be mapped to the {ref}/current/object.html[Object datatype].
	`60`	+The property `foo` would be mapped to the {ref}/object.html[Object datatype].
`60`	`61`
`61`	`62`	This means that you can't index a document where `foo` would be a different datatype, as in shown in the following example:
`62`	`63`