diff --git a/doc.zih.tu-dresden.de/docs/jobs_and_resources/alpha_centauri.md b/doc.zih.tu-dresden.de/docs/jobs_and_resources/alpha_centauri.md
index e74a67eef78cdae2e9705b978858e8fc615d1cce..cec4a1dcd71340073794b43c9a96ed3012a6e7bf 100644
--- a/doc.zih.tu-dresden.de/docs/jobs_and_resources/alpha_centauri.md
+++ b/doc.zih.tu-dresden.de/docs/jobs_and_resources/alpha_centauri.md
@@ -18,7 +18,7 @@ of the new cluster [`Barnard`](barnard.md).
 
 !!! hint "Maintenance Work"
 
-    On **June 4+5**, we will shut down and migrate `Alpha Centauri` to the Barnard Infiniband
+    On **June 4+5**, we will shut down and migrate `Alpha Centauri` to the Barnard InfiniBand
     infrastructure.
 
 As consequences,
@@ -32,21 +32,21 @@ For your convenience, we already have started migrating your data from `/beegfs`
 
 !!! hint "User Action Required"
 
-    The less we have to synchronize the faster the overall process. So clean-up
+    The less we have to synchronize the faster will be the overall process. So, please clean-up
     as much as possible as soon as possible.
 
 Important for your work is:
 
 * Do not add terabytes of data to `/beegfs` if you cannot "consume" it before June 4.
-* After final successful data transfer to `/data/horse/beegfs` you then have to
-  move it to normal workspaces on `/data/horse`.
+* After the final successful data transfer to `/data/horse/beegfs`, you then have to
+  move it to the normal workspaces on `/data/horse`.
 * Be prepared to adapt your workflows to the new paths.
 
 What happens afterward:
 
   * complete deletion of all user data in `/beegfs`
   * complete recabling of the storage nodes (BeeGFS hardware)
-  * Software+Firmware updates
+  * software and firmware updates
   * set-up of a new WEKA filesystem for high I/O demands on the same hardware
 
 In case of any question regarding this maintenance or required action, please do not hesitate to