From d4c3a916398e4eee9c1eaaa840968d4b19f40c91 Mon Sep 17 00:00:00 2001
From: mjkwiatkowski <mati.rewa@gmail.com>
Date: Wed, 15 Jul 2026 15:56:09 +0200
Subject: feat: finished section 2.4.3

---
 content/conclusion.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'content/conclusion.tex')

diff --git a/content/conclusion.tex b/content/conclusion.tex
index 1df3d95..86d9f68 100644
--- a/content/conclusion.tex
+++ b/content/conclusion.tex
@@ -37,7 +37,7 @@ We answer the main research question by addressing each sub-research question.
 
 	\item \emph{How to validate and evaluate a datacenter digital twin architecture in relation to system requirements?}\\
 	      To answer the last research question we crated a prototype.
-	      During the prototype design, we used state-of-the-practice software, such as \code{Confluent Kafka}, \code{Redis} and \code{PostgreSQL} (see \Cref{ss:implementation_overview}).
+	      During the prototype design, we used state-of-the-practice software, such as \code{Confluent Kafka}, \code{Redis} and \code{PostgreSQL} (see \Cref{ss:detailed_implementation_overview}).
 	      However, as it turns out, evaluating \gls{dcdt}s is not a trivial task.
 	      Lacking the physical datacenter to experiment with, we came up with a novel digital twin evaluation method.
 	      Our method, relies solely on discrete-event simulation to model the physical datacenter, overcoming the problems of real-world experimentation (\eg sustainability, costliness, reproducibility).
-- 
cgit v1.2.3

