From 74f0c5507f14a48d8d767bbddbd792b75a6d78f8 Mon Sep 17 00:00:00 2001
From: Martyn Welch <martyn.welch@collabora.com>
Date: Wed, 24 Feb 2021 12:39:17 +0000
Subject: [PATCH] Addressing "preparing hawkbit for production" review comments

Add links to other documents as proposed by Daniela.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>
---
 content/concepts/preparing-hawkbit-for-production.md | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/content/concepts/preparing-hawkbit-for-production.md b/content/concepts/preparing-hawkbit-for-production.md
index b0f3ef973..51c888ce9 100644
--- a/content/concepts/preparing-hawkbit-for-production.md
+++ b/content/concepts/preparing-hawkbit-for-production.md
@@ -11,10 +11,12 @@ outputs = ["html", "pdf-in"]
 
 The Apertis project has been experimenting with the use of
 [Eclipse hawkBit](https://www.eclipse.org/hawkbit/) as a mechanism for the
-deployment of system updates and applications to target devices in the field.
-The current emphasis is being placed on system updates, though hawkBit can also
-be used to address different software distribution use cases such as to
-distribute system software, updates and even apps from an app store.
+deployment of [system updates]({{< ref "system-updates-and-rollback.md" >}})
+and [applications]({{< ref "application-framework.md#the-app-store" >}}) to
+target devices in the field.  The current emphasis is being placed on system
+updates, though hawkBit can also be used to address different software
+distribution use cases such as to distribute system software, updates and even
+apps from an app store.
 
 Apertis has recently deployed a [hawkBit instance](https://hawkbit.apertis.org)
 into which the
-- 
GitLab