Integrated Steve's remarks to the Scheduler section (CHEP2016 paper).

doc/CHEP2016/CHEP_2016_paper_CTA.tex

@@ -275,7 +275,7 @@ jobs it contains to allow efficient mount scheduling.
 \subsection{Tape mount scheduling and job handling}
 The tape drives scheduling has to take into account several competing requirements.
 User-initiated accesses in both directions should be executed within a bound latency
-(measured in the order of hours). As mounting and unmounting tape cartridges to and 
+(measured in the order of hours). As mounting and dismounting tape cartridges to and 
 from the drive costs about a minute each, the execution
 of data accessed is postponed until the amount of data to transfer makes it worthwhile
 or the job age is too high. The user initiated mounts create an irregular
@@ -284,7 +284,7 @@ various analysis patterns.
 
 The maintenance tasks, retrieves and archives for repack, and verifications are
 high bandwidth tasks with very relaxed latency requirements which could extend to
-several month. Those low priority tasks get the drives when the user-initiated tasks
+several months. Those low priority tasks get the drives when the user-initiated tasks
 are not using the drives.
 
 When a drive is idle and ready, the tape daemon process retrieves the summaries of
@@ -296,11 +296,11 @@ atomically: at any point in time, only one drive takes a scheduling decision.
 Once a mount is started, the tape drive just consumes the jobs from the queue and
 executes them.
 
-This single step scheduling allows an flexibility with the scheduling rules
-adjustments are expected as experience with CTA will grow.
+This single step scheduling allows flexibility with the scheduling rules and
+adjustments are expected as experience with CTA grows.
 
 \subsection{Tape drive preemption}
-Long mount can last up to eight or more hours, which is greater than the
+A long mount can last up to eight or more hours, which is greater than the
 acceptable latency for user tasks. In order to not let the long-running
 low priority mounts block the drives from the higher priority ones, the tape
 daemon will keep polling the scheduling information at a low rate and interrupt
@@ -310,9 +310,8 @@ This mixing of high and low priority tasks previously had to be handled by hand
 scripts in CASTOR.
 
 \subsection{CTA to EOS communication and other operations}
-At the file level, the scheduler also handles the file lifecycle reporting. It coordinates
-the tape file information recording in the file catalog, and then the reporting of
-successful transfers back to EOS.
+The scheduler is responsible for reporting the steps in the lifecycle of each file. 
+It coordinates the updating of the file catalog, and EOS.
 
 Finally, the scheduler component handles queue listing and other house keeping
 tasks initiated through the front end by operators, via a command line tool.