cicd-with-nic5.md

@@ -4,6 +4,7 @@ title: Configuring a standard experiment for NIC5
 
 
 
+
 Thanks to GitLab CI/CD features and thanks to [Jacamar CI](https://ecp-ci.gitlab.io/docs/admin/jacamar/introduction.html), you can configure a standard experiment for BAMHBI to run on a cluster which you will be able to kickstart from ULiège GitLab with a simple click. For the time being, all CI/CD experiments of the MAST will be run on the NIC5 cluster, notably to benefit from the many MAST resources already stored on NIC5.
 
 This tutorial details the requirements you should meet beforehand, for both security and storage concerns, then how you can write a suitable CI/CD configuration to create your experiment.
@@ -107,7 +108,7 @@ By step 4 in the previous section, the job is normally already good to run on NI
 
 * Make sure to **include ``when: manual`` in the very first stage of your pipeline**. This will ensure your pipeline will start only when you ask (manually), and not at every commit. This matters especially at MAST, as there may be eventually multiple pre-configured standard experiments, and we don't want, obviously, to re-run all of them at each commit.
 
-* **To mitigate random crashes that may happen at job start-up, use the ``retry`` keyword** to tell your job to retry a few times. You can also tell it to retry on specific error codes. Typically, random crashes at start-up issue exit code 1, so the next job excerpt will retry up to two times the job if such error occurs.
+* **To mitigate random crashes that may happen at job start-up, use the ``retry`` keyword** to tell your job to retry a few times. You can also tell it to retry on specific error codes. Typically, random crashes at start-up issue exit code 1, so the next job excerpt will retry up to two times the job if such an error occurs.
 
 ```
   retry: