Further minor improvements to CHEP_2016_paper_CTA.tex

doc/CHEP2016/CHEP_2016_paper_CTA.tex

@@ -136,7 +136,8 @@ queue.
 The CTA tape drive daemon was copied and evolved from CASTOR.  CTA benefits from
 the experience of CASTOR including how to control tape hardware and how to queue
 transfer requests in order to use tape hardware efficiently.  The CTA tape drive
-daemon queries the CTA metadata system for tapes to be mounted and files to be transferred.  The daemon transfers files between tapes and the EOS disk servers.
+daemon queries the CTA metadata system for tapes to be mounted and files to be
+transferred.  The daemon transfers files between tapes and the EOS disk servers.
 When the daemon has completed a transfer it writes the result back to the CTA
 metadata system.
 
@@ -177,8 +178,8 @@ The following steps describe how a file is retrieved from tape.
 \begin{enumerate}
   \item The user sends EOS a prepare request that instructs EOS to retrieve a
   file from tape.
-  \item The EOS workflow engine queues the prepare request with the CTA
-  front-end.
+  \item The EOS workflow engine queues the corresponding retrieve request with
+  the CTA front-end.
   \item The CTA front-end stores the retrieve request in the CTA metadata
   system.
   \item The file becomes eligible for recall.  Either the file has be been