Small styling improvements

doc.zih.tu-dresden.de/docs/jobs_and_resources/hardware_overview.md

@@ -20,7 +20,10 @@ users and the ZIH.
   - IPs: 141.30.73.82/83
 - Direct access to these nodes is granted via IP whitelisting (contact
   hpcsupport@zih.tu-dresden.de) - otherwise use TU Dresden VPN.
-- Run time limitation: any process will timeout after 5 minutes.
+
+!!! warning "Run time limit"
+
+    Any process on login nodes is stopped after 5 minutes.
 
 ## AMD Rome CPUs + NVIDIA A100
 

doc.zih.tu-dresden.de/docs/jobs_and_resources/partitions_and_limits.md

@@ -6,23 +6,23 @@ resources, like memory (but not CPU). On the other hand, a higher throughput can
 smaller jobs. Thus, restrictions w.r.t. [memory](#memory-limits) and
 [runtime limits](#runtime-limits) have to be respected when submitting jobs.
 
+## Runtime Limits
+
 !!! warning "Runtime limits on login nodes"
 
-    There is a time limit set for processes on login nodes. If you run applications
-    outside of a compute job, it will be stopped automatically after 5 minutes with
+    There is a time limit set for processes on login nodes. If you run applications outside of a
+    compute job, it will be stopped automatically after 5 minutes with
 
     ```
     CPU time limit exceeded
     ```
 
-    Please start a job using a [batch system](slurm.md).
-
-## Runtime Limits
+    Please start a job using the [batch system](slurm.md).
 
 !!! note "Runtime limits are enforced."
 
-    This means, a job will be canceled as soon as it exceeds its requested limit. Currently, the
-    maximum run time is 7 days.
+    A job is canceled as soon as it exceeds its requested limit. Currently, the maximum run time is
+    7 days.
 
 Shorter jobs come with multiple advantages:
 
@@ -54,8 +54,7 @@ not capable of checkpoint/restart can be adapted. Please refer to the section
 
 !!! note "Memory limits are enforced."
 
-    This means that jobs which exceed their per-node memory limit will be killed automatically by
-    the batch system.
+    Jobs which exceed their per-node memory limit are killed automatically by the batch system.
 
 Memory requirements for your job can be specified via the `sbatch/srun` parameters: