starpu_initialize is needed for SCC only, not for MIC

doc/chapters/api.texi

@@ -267,8 +267,8 @@ indicates that no worker was available (so that StarPU was not initialized).
 
 @deftypefun int starpu_initialize ({struct starpu_conf *}@var{conf}, int @var{argc}, {char ***}@var{argv})
 This is the same as @code{starpu_init}, but also takes the @code{argc} and
-@code{argv} as gotten by the application. This is needed for MIC and SCC
-execution so that instances of StarPU can know whether they are slaves or masters.
+@code{argv} as gotten by the application. This is needed for SCC
+execution to initialize the communication library.
 @end deftypefun
 
 @deftypefun int starpu_conf_init ({struct starpu_conf *}@var{conf})

doc/chapters/mic-scc-support.texi

@@ -38,7 +38,7 @@ name of the CPU implementation. StarPU will thus simply use the existing CPU
 implementation (cross-rebuilt in the MIC case). The functions have to be
 globally-visible (i.e. not @code{static}) for StarPU to be able to look them up.
 
-@code{starpu_initialize} also has to be used instead of @code{starpu_init}, so
+For SCC execution, @code{starpu_initialize} also has to be used instead of @code{starpu_init}, so
 as to pass @code{argc} and @code{argv}.
 
 @section Launching programs