From b71b5fc486464ea0e740a83845c7c79aa7d1a155 Mon Sep 17 00:00:00 2001
From: Guilherme Pantoja Calandrini de Azevedo Junior
 <guilherme.calandrini@tu-dresden.de>
Date: Mon, 5 Dec 2022 11:10:51 +0100
Subject: [PATCH] Update doc.zih.tu-dresden.de/docs/software/fem_software.md

---
 doc.zih.tu-dresden.de/docs/software/fem_software.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/doc.zih.tu-dresden.de/docs/software/fem_software.md b/doc.zih.tu-dresden.de/docs/software/fem_software.md
index b61be02a9..4d74f0b06 100644
--- a/doc.zih.tu-dresden.de/docs/software/fem_software.md
+++ b/doc.zih.tu-dresden.de/docs/software/fem_software.md
@@ -188,7 +188,9 @@ that you can simply change to something like 16 or 24. For now, you should stay
 boundaries, because multi-node calculations require additional parameters. The number you choose
 should match your used `--cpus-per-task` parameter in your job file.
 
-### Running mapdl in interactive mode
+### Running MAPDL in interactive mode
+
+ANSYS Mechanical APDL (sometimes called ANSYS Classic, the older MAPDL scripted environment).
 
 ```console
 marie@login$ srun --partition=haswell --ntasks=1 --cpus-per-task=4 --time=1:00:00 --mem-per-cpu=1700 --pty bash
-- 
GitLab