diff --git a/docs/agent-api.asciidoc b/docs/agent-api.asciidoc
index 0f84daae0..ec68b8089 100644
--- a/docs/agent-api.asciidoc
+++ b/docs/agent-api.asciidoc
@@ -68,7 +68,7 @@ For each call, the properties of the context argument are shallow merged with th
 The given `context` argument must be an object and can contain any property that can be JSON encoded.
 
 TIP: Before using custom context, ensure you understand the different types of
-{apm-guide-ref}/metadata.html[metadata] that are available.
+{apm-guide-ref}/api-metadata.html[metadata] that are available.
 
 
 [float]
@@ -80,13 +80,13 @@ TIP: Before using custom context, ensure you understand the different types of
 apm.addLabels({ [name]: value })
 ----
 
-Set labels on transactions and errors. 
+Set labels on transactions and errors.
 Starting with APM Server 7.6+, the labels are added to spans as well.
 
 Labels are key/value pairs that are indexed by Elasticsearch and therefore searchable (as opposed to data set via <<apm-set-custom-context,`apm.setCustomContext()`>>). You can set multiple labels.
 
 TIP: Before using custom labels, ensure you understand the different types of
-{apm-guide-ref}/metadata.html[metadata] that are available.
+{apm-guide-ref}/api-metadata.html[metadata] that are available.
 
 Arguments:
 
diff --git a/docs/sourcemap.asciidoc b/docs/sourcemap.asciidoc
index 09cbe2e7f..827f84fd8 100644
--- a/docs/sourcemap.asciidoc
+++ b/docs/sourcemap.asciidoc
@@ -10,12 +10,12 @@ without losing the ability to quickly and easily debug your applications.
 
 There are three steps required to enable, upload, and apply a source map to error stack traces.
 An overview is listed below, and a complete walk-through is available in the
-{apm-guide-ref}/sourcemaps.html[generate and upload a source map] guide.
+{apm-guide-ref}/source-map-how-to.html[generate and upload a source map] guide.
 
 1. Set the <<service-version,`serviceVersion`>> when initializing the RUM Agent.
-2. {apm-guide-ref}/sourcemaps.html#sourcemap-rum-generate[Generate a source map]
+2. {apm-guide-ref}/source-map-how-to.html#source-map-rum-generate[Generate a source map]
 for your application with the `serviceVersion` from step one.
-3. {apm-guide-ref}/sourcemaps.html#sourcemap-rum-upload[Enable and upload the source map file] to APM Server.
+3. {apm-guide-ref}/source-map-how-to.html#source-map-rum-upload[Enable and upload the source map file] to APM Server.
 
 // Don't link to this section
 [[secret-token]]
diff --git a/docs/transaction-api.asciidoc b/docs/transaction-api.asciidoc
index c5e3c840a..aa60c2f9b 100644
--- a/docs/transaction-api.asciidoc
+++ b/docs/transaction-api.asciidoc
@@ -126,7 +126,7 @@ it will also get tagged with the same labels.
 Labels are key/value pairs that are indexed by Elasticsearch and therefore searchable (as opposed to data set via <<apm-set-custom-context,`apm.setCustomContext()`>>).
 
 TIP: Before using custom labels, ensure you understand the different types of
-{apm-guide-ref}/metadata.html[metadata] that are available.
+{apm-guide-ref}/api-metadata.html[metadata] that are available.
 
 Arguments: