Improved the wording related to synchronous vs asynchronous as both could be...

Improved the wording related to synchronous vs asynchronous as both could be implemented with EOS's WFE.

doc/EOS-CTA interface.tex

@@ -71,7 +71,7 @@ Figure \ref{fig:write-archive-wfe} shows the sequence of a client writing a file
 	    \end{call}
     \end{sequencediagram}
   }
-  \caption{File write and archive queueing (with workflow engine)}
+  \caption{File write and archive queueing (asynchronous)}
   \label{fig:write-archive-wfe}
 \end{figure}
 
@@ -126,7 +126,7 @@ EOS should filter and forbid updates to files located on tape. Otherwise, a poli
 
 \subsection{Explicit retrieves (prepare)} \label{user_retrieves}
 
-Explicit retrieve will face several use cases. The way we deal with them should be decided. Synchronous and asynchronous (WFE based) behaviors make little difference, but allow (catastrophic) problems to be reported to the user.
+Explicit retrieve will face several use cases. The way we deal with them should be decided. Synchronous and asynchronous (through WFE) behaviors make little difference, but allow (catastrophic) problems to be reported to the user.
 
 \begin{itemize}
 \item The file is not on disk, no request is queued yet and so we should queue the retrieve request.
@@ -177,7 +177,7 @@ A double criteria garbage collection will probably be necessary to keep free spa
 
 \subsection{Complete deletion of files}
 
-There is no interest in reporting failure to delete the file in CTA while the deletion proceeds in EOS, so synchronous and WFE-based implementations are equivalent. The complete deletion of files from EOS raises several race conditions (delete while archiving, delete while retrieving), but all will probably be resolved by failure of data or metadata operations initiated from CTA to EOS, plus slow reconciliation.
+There is no interest in reporting failure to delete the file in CTA while the deletion proceeds in EOS, so synchronous and asynchronous implementations are equivalent. The complete deletion of files from EOS raises several race conditions (delete while archiving, delete while retrieving), but all will probably be resolved by failure of data or metadata operations initiated from CTA to EOS, plus slow reconciliation.
 
 \subsection{Fast reconciliation}