diff --git a/doc.zih.tu-dresden.de/docs/jobs_and_resources/barnard_test.md b/doc.zih.tu-dresden.de/docs/jobs_and_resources/barnard_test.md
index d3e0ca785adf6fe9b2bc5c0ab3baac536595469a..be6f165362cf5ea0a0e055d8207353fb3d272d12 100644
--- a/doc.zih.tu-dresden.de/docs/jobs_and_resources/barnard_test.md
+++ b/doc.zih.tu-dresden.de/docs/jobs_and_resources/barnard_test.md
@@ -57,7 +57,7 @@ below. In order to support the data life cycle management, the well-known
 
 !!! Warning
 
-    All old filesystems will be shutdown by the end of 2023.
+    All old filesystems, i.e., `ssd`, `beegfs`, and `scratch`, will be shutdown by the end of 2023.
     To work with your data from Taurus you might have to move/copy them to the new storages.
 
     Please, carefully read the following documentation and instructions.
@@ -137,10 +137,9 @@ directory on datamover      mounting clusters   directory on cluster
 
 In the following, we will provide instructions with comprehensive examples for the data transfer of
 your data to the new `/home` filesystem, as well as the working filesystems `/data/horse` and
-`/data/walrus`. With respect to the later, the instructions and examples are divided by the target
-not the source filesystem.
+`/data/walrus`.
 
-??? "Migration of Home Directory"
+??? "Migration of Your Home Directory"
 
     Your personal (old) home directory at Taurus will not be automatically transferred to the new
     Barnard system. Please do not copy your entire home, but clean up your data. E.g., it might
@@ -188,24 +187,19 @@ not the source filesystem.
         Please be aware that there is **no synchronisation process** between your home directories
         at Taurus and Barnard. Thus, after the very first transfer, they will become divergent.
 
-#### Migration of Working Data from Old Filesystems `ssd`, `beegfs`, and `scratch`
+Please follow this instructions for transferring you data from `ssd`, `beegfs` and `scratch` to the
+new filesystems. The instructions and examples are divided by the target not the source filesystem.
 
-In the following, we will provide instructions for the data transfer of your old working data to the
-new filesystems `/data/horse` and `/data/walrus` with comprehensive examples.
-Please **do not copy your entire work data** from the old to the new filesystems, but consider this
-opportunity for cleaning up your data. E.g., it might make sense to delete outdated scripts, old log
-files, etc., and move other files, e.g., results, to the `/data/walrus` filesystem. Thus, please
-take your time and make a plan which directories and files need to be transferred to `/data/horse`
-and which to `/data/walrus`. Therefor, the following instructions and examples are divided by the
-target not the source filesystem.
+This migration task requires a preliminary step: You need to allocate workspaces on the
+target filesystems.
 
-??? Note "First Step: Allocate a workspace"
+??? Note "Preliminary Step: Allocate a workspace"
 
     Both `/data/horse/` and `/data/walrus` can only be used with
     [workspaces](../data_lifecycle/workspaces.md). Before you invoke any data transer from the old
     working filesystems to the new ones, you need to allocate a workspace first.
 
-    The command `ws_list -l` lists the available and the default filesystem for worspaces.
+    The command `ws_list -l` lists the available and the default filesystem for workspaces.
 
     ```
     marie@barnard$ ws_list --list
@@ -220,10 +214,16 @@ target not the source filesystem.
     refer to our [workspace documentation](../data_lifecycle/workspaces.md), if you need refresh
     your knowledge.
 
+    The most simple command to allocate a workspace is as follows
+
     ```
     marie@barnard$ ws_allocate numbercrunch 90
     ```
 
+    Please refer to the table holding the settings
+    (cf. [subection workspaces on Barnard](#workspaces-on-barnard)) for the max. duration and
+    `ws_allocate --help` for all available options.
+
 ??? "Migration to `/data/horse`"
 
     === "Source: old `/scratch`"