From 239f3589f9a95bab39c66deab807beef9570b3c9 Mon Sep 17 00:00:00 2001
From: Diego Alejandro Tejada Arango
 <12887482+datejada@users.noreply.github.com>
Date: Tue, 17 Oct 2023 09:56:54 +0200
Subject: [PATCH] Extend the introduction

Add to the introduction a short explanation of what the reserves are and why are important
---
 docs/src/tutorial/reserves.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/src/tutorial/reserves.md b/docs/src/tutorial/reserves.md
index 1ca6c8e677..876a4110d8 100644
--- a/docs/src/tutorial/reserves.md
+++ b/docs/src/tutorial/reserves.md
@@ -6,6 +6,8 @@ This tutorial provides a step-by-step guide to include reserve requirements in a
 
 Welcome to our tutorial, where we will walk you through the process of adding a new reserve node in SpineOpt using Spine Toolbox. To get the most out of this tutorial, we suggest first completing the Simple System tutorial, which can be found [here](https://spine-tools.github.io/SpineOpt.jl/latest/tutorial/simple_system/).
 
+Reserves refer to the capacity or energy that is kept as a backup to ensure the power system's reliability. This reserve capacity can be brought online automatically or manually in the event of unforeseen system disruptions such as generation failure, transmission line failure, or a sudden increase in demand. Operating reserves are essential to ensure that there is always enough generation capacity available to meet demand, even in the face of unforeseen system disruptions.
+
 ### Model assumptions
 
 - The reserve node has a requirement of 20MW for upwards reserve