Update using-nodes-interactively.snip

carpentries-incubator · Sep 21, 2023 · fe69a7b · fe69a7b
1 parent 0646b2a
commit fe69a7b
Showing 1 changed file with 4 additions and 4 deletions.
diff --git a/_includes/snippets_library/HPCC_MagicCastle_slurm/scheduler/using-nodes-interactively.snip b/_includes/snippets_library/HPCC_MagicCastle_slurm/scheduler/using-nodes-interactively.snip
@@ -1,6 +1,6 @@
 `{{ site.sched.interactive }}` runs a single command on the cluster and then
-exits. Let's demonstrate this by running the `hostname` command with `{{
-site.sched.interactive }}`. (We can cancel an `{{ site.sched.interactive }}`
+exits. Let's demonstrate this by running the `hostname` command with
+`{{ site.sched.interactive }}`. (We can cancel an `{{ site.sched.interactive }}`
 job with `Ctrl-c`.)
 
 ```
@@ -13,8 +13,8 @@ job with `Ctrl-c`.)
 ```
 {: .output}
 
-`{{ site.sched.interactive }}` accepts all of the same options as `{{
-site.sched.submit.name }}`. However, instead of specifying these in a script,
+`{{ site.sched.interactive }}` accepts all of the same options as
+`{{ site.sched.submit.name }}`. However, instead of specifying these in a script,
 these options are specified on the command-line when starting a job. To submit
 a job that uses 2 CPUs for instance, we could use the following command: