Adding upstream version 1.39.0.upstream/1.39.0

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

2 files changed, 4 insertions, 20 deletions

diff --git a/docs/export/enable-connector.md b/docs/export/enable-connector.md
index 28208e2f4..02e380e15 100644
--- a/docs/export/enable-connector.md
+++ b/docs/export/enable-connector.md
@@ -5,7 +5,7 @@ custom_edit_url: "https://github.com/netdata/netdata/edit/master/docs/export/ena
 sidebar_label: "Enable an exporting connector"
 learn_status: "Published"
 learn_topic_type: "Tasks"
-learn_rel_path: "Setup"
+learn_rel_path: "Configuration"
 -->
 
 # Enable an exporting connector
@@ -92,8 +92,8 @@ details.
 If you want to further configure your exporting connectors, see
 the [exporting engine reference](https://github.com/netdata/netdata/blob/master/exporting/README.md#configuration).
 
-For a comprehensive example of using the Graphite connector, read our guide:
-[_Export and visualize Netdata metrics in Graphite_](https://github.com/netdata/netdata/blob/master/docs/guides/export/export-netdata-metrics-graphite.md). Or, start
+For a comprehensive example of using the Graphite connector, read our documentation on 
+[exporting metrics to Graphite providers](https://github.com/netdata/netdata/blob/master/exporting/graphite/README.md). Or, start
 [using host labels](https://github.com/netdata/netdata/blob/master/docs/guides/using-host-labels.md) on exported metrics.
 
 ### Related reference documentation
diff --git a/docs/export/external-databases.md b/docs/export/external-databases.md
index 00ca7410e..715e8660d 100644
--- a/docs/export/external-databases.md
+++ b/docs/export/external-databases.md
@@ -22,7 +22,7 @@ Based on your needs and resources you allocated to your external time-series dat
 that metrics are exported or export only certain charts with filtering. You can also choose whether metrics are exported
 as-collected, a normalized average, or the sum/volume of metrics values over the configured interval.
 
-Exporting is an important part of Netdata's effort to be [interoperable](https://github.com/netdata/netdata/blob/master/docs/overview/netdata-monitoring-stack.md)
+Exporting is an important part of Netdata's effort to be interoperable
 with other monitoring software. You can use an external time-series database for long-term metrics retention, further
 analysis, or correlation with other tools, such as application tracing.
 
@@ -75,19 +75,3 @@ documentation and the [enabling a connector](https://github.com/netdata/netdata/
 Can't find your preferred external time-series database? Ask our [community](https://community.netdata.cloud/) for
 solutions, or file an [issue on
 GitHub](https://github.com/netdata/netdata/issues/new?assignees=&labels=bug%2Cneeds+triage&template=BUG_REPORT.yml).
-
-## What's next?
-
-We recommend you read our document on [enabling a connector](https://github.com/netdata/netdata/blob/master/docs/export/enable-connector.md) to learn about the
-process and discover important configuration options. If you would rather skip ahead, click on any of the above links to
-connectors for their reference documentation, which outline any prerequisites to install for that connector, along with
-connector-specific configuration options.
-
-Read about one possible use case for exporting metrics in our guide: [_Export and visualize Netdata metrics in
-Graphite_](https://github.com/netdata/netdata/blob/master/docs/guides/export/export-netdata-metrics-graphite.md).
-
-### Related reference documentation
-
--   [Exporting engine reference](https://github.com/netdata/netdata/blob/master/exporting/README.md)
-
-