Update user_guide.rst

doc/user_guide.rst

@@ -9,10 +9,10 @@ User guide
 Problem setting
 ---------------
 
-Consider a scientist, Yann, who has designed multiple *C++* libraries for statistical analysis (**Tool**, **StatTool**, **SequenceAnalysis**).
-Yann would like to distribute his libraries and decide to make them available in *Python* in order to reach a public of statisticians but also less expert scientists such as biologist.
-Yet, Yann is not interested in becoming an expert in *C++*/*Python* wrapping, even if it exists classical approaches consisting in writing wrappers with **SWIG** or **Boost.Python**.
-Moreover, he would never complete the wrapping of his libraries into *Python* packages and would have serious difficulties to maintain the wrappers, since this semi-automatic process is time consuming and error prone.
+Consider a scientist who has designed multiple *C++* libraries for statistical analysis.
+He would like to distribute his libraries and decide to make them available in *Python* in order to reach a public of statisticians but also less expert scientists such as biologists.
+Yet, he is not interested in becoming an expert in *C++*/*Python* wrapping, even if it exists classical approaches consisting in writing wrappers with **SWIG** :cite:`Bea03` or **Boost.Python** :cite:`AG03`.
+Moreover, he would have serious difficulties to maintain the wrappers, since this semi-automatic process is time consuming and error prone.
 Instead, he would like to automate the process of generating wrappers in sync with his evolving *C++* libraries.
 That's what the **AutoWIG** software aspires to achieve.