From 181d1fc47add95c7fc0bbb5970a561ceaa44f2b9 Mon Sep 17 00:00:00 2001
From: Miroslav Kratochvil <miroslav.kratochvil@uni.lu>
Date: Wed, 14 Feb 2024 11:47:44 +0100
Subject: [PATCH] Apply 1 suggestion(s) to 1 file(s)

---
 external/exchange-channels/atlas-hpc/atlas-hpc.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/external/exchange-channels/atlas-hpc/atlas-hpc.md b/external/exchange-channels/atlas-hpc/atlas-hpc.md
index 963f4e39..9e344757 100644
--- a/external/exchange-channels/atlas-hpc/atlas-hpc.md
+++ b/external/exchange-channels/atlas-hpc/atlas-hpc.md
@@ -10,7 +10,7 @@ redirect_from:
 ---
 
 # Data transfer between Atlas and UL HPC Clusters
-A recommended storage pattern is to have the master copy of data on Atlas (project folder) and to only store data on the UL HPC Clusters temporarily for the duration of computational analysis. All analysis performed on the UL HPC Clusters must therefore be regularly transferred to Atlas. This How-to Card describes the different methods to transfer data between Atlas and the UL HPC Clusters. The three recommended methods to transfer data are: 
+A recommended storage pattern is to have the master copy of data on Atlas (project folder) and only store data on the UL HPC Clusters temporarily for the required practical duration of computational analysis. All data analyzed on the UL HPC Clusters should therefore be transferred from Atlas, and the derived data and results should be transferred back to Atlas. This How-to Card describes the different methods to transfer data between Atlas and the UL HPC Clusters. The three recommended methods to transfer data are:
 
 1. [Via laptop with ```scp``` or ```rsync```](#1. Via laptop using scp or rsync)
 2. [Via dedicated Virtual Machine (VM)](#2. Via dedicated Virtual Machine (VM) using rsync)
-- 
GitLab