From 0076c20ff7961f7dd1fecbeb55a516f06a8dcbad Mon Sep 17 00:00:00 2001
From: Ravi Tripathi <ravi89@uab.edu>
Date: Wed, 15 Aug 2018 00:16:47 -0500
Subject: [PATCH] Slight modifications in README file

---
 bash_array_jobs/README.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/bash_array_jobs/README.md b/bash_array_jobs/README.md
index 439dadb..0f92ea7 100644
--- a/bash_array_jobs/README.md
+++ b/bash_array_jobs/README.md
@@ -8,7 +8,7 @@
 
 
 # Scenario #
-Often times, one needs to submit a huge number of very similar jobs on the cluster. For example, if you want to  run a software with same parameters over lots of subjects or if you want to run Quality Check on all the raw data that you have to process.
+Often times, users needs to submit huge number of very similar jobs on the cluster. For example, if you want to  run a software with same parameters over lots of subjects or if you want to run Quality Check on all the raw data that you have to process.
 
 # Methods #
 
@@ -69,7 +69,8 @@ sbatch array_seq.job
 ```  
 
 **Random File Name**  
-Well, job arrays are great if your files are named sequentially (e.g. test1, test2, etc). But what if they're not? One can use both shell arrays + SLURM arrays to solve this.
+Well, job arrays look great if your files are named sequentially (e.g. test1, test2, etc). But what if they're named randomly?  
+A: We can use both shell arrays + SLURM arrays to solve this.
 
 ```
 #!/bin/bash
-- 
GitLab