Merge branch 'slurm/zen2' of github.com:bcumming/cscs-docs into slurm/zen2

Author: bcumming

docs/alps/hardware.md

@@ -82,8 +82,8 @@ Each node contains four Grace-Hopper modules and four corresponding network inte
 
 These nodes have two [AMD Epyc 7742](https://en.wikichip.org/wiki/amd/epyc/7742) 64-core CPU sockets, and are used primarily for the [Eiger][ref-cluster-eiger] system. They come in two memory configurations:
 
-* *Standard-memory*:  256 GB in 16x16 GB DDR4 Dimms.
-* *Large-memory*:  512 GB in 16x32 GB DDR4 Dimms.
+* *Standard-memory*:  256 GB in 16x16 GB DDR4 DIMMs.
+* *Large-memory*:  512 GB in 16x32 GB DDR4 DIMMs.
 
 !!! note "Not all memory is available"
     The total memory available to jobs on the nodes is roughly 245 GB and 497 GB on the standard and large memory nodes respectively.

docs/running/slurm.md

@@ -43,7 +43,7 @@ sbatch --account=g123 ./job.sh
 ```
 
 !!! note
-    The flag `--account` and `-Cmc` that were required on the old Eiger cluster are no longer required.
+    The flags `--account` and `-Cmc` that were required on the old Eiger cluster are no longer required.
 
 ## Prioritization and scheduling
 
@@ -62,7 +62,7 @@ At CSCS, SLURM is configured to accommodate the diverse range of node types avai
 These nodes vary in architecture, including CPU-only nodes and nodes equipped with different types of GPUs.
 Because of this heterogeneity, SLURM must be tailored to ensure efficient resource allocation, job scheduling, and workload management specific to each node type.
 
-Each type of node has different resource constraints and capabilities, which SLURM takes into account when scheduling jobs.
+Each type of node has different resource constraints and capabilities, which Slurm takes into account when scheduling jobs.
 For example, CPU-only nodes may have configurations optimized for multi-threaded CPU workloads, while GPU nodes require additional parameters to allocate GPU resources efficiently.
 SLURM ensures that user jobs request and receive the appropriate resources while preventing conflicts or inefficient utilization.
 
@@ -317,7 +317,7 @@ The configuration that is optimal for your application may be different.
 [NVIDIA's Multi-Process Service (MPS)]: https://docs.nvidia.com/deploy/mps/index.html
 
 [](){#ref-slurm-amdcpu}
-## AMD CPU Nodes
+## AMD CPU nodes
 
 Alps has nodes with two AMD Epyc Rome CPU sockets per node for CPU-only workloads, most notably in the [Eiger][ref-cluster-eiger] cluster provided by the [HPC Platform][ref-platform-hpcp].
 For a detailed description of the node hardware, see the [AMD Rome node][ref-alps-zen2-node] hardware documentation.