From 1e76fd1a45d8b20a7f4075a477b8a0fd7f4c4740 Mon Sep 17 00:00:00 2001
From: Taras Lazariv <taras.lazariv@tu-dresden.de>
Date: Wed, 18 May 2022 09:58:17 +0200
Subject: [PATCH] Use sacct <job id> instead of ws_find.

---
 doc.zih.tu-dresden.de/docs/contrib/content_rules.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc.zih.tu-dresden.de/docs/contrib/content_rules.md b/doc.zih.tu-dresden.de/docs/contrib/content_rules.md
index 98adfe220..8b758e90d 100644
--- a/doc.zih.tu-dresden.de/docs/contrib/content_rules.md
+++ b/doc.zih.tu-dresden.de/docs/contrib/content_rules.md
@@ -284,7 +284,7 @@ give a general idea of how a command or code snippet can be used, e. g. to expla
 some command argument:
 
 ```bash
-marie@login$ ws_find <job id>
+marie@login$ sacct -j <job id>
 ```
 
 Here, a placeholder explains the intention better than just a specific value:
-- 
GitLab