diff --git a/code/python/teste.ipynb b/code/python/teste.ipynb
new file mode 100644
index 0000000..e69de29
--- /dev/null
+++ b/code/python/teste.ipynb
diff --git a/text/paper_01/pre-paper.pdf b/text/paper_01/pre-paper.pdf
index 1b59b86..cd7cc2f 100644
Binary files a/text/paper_01/pre-paper.pdf and b/text/paper_01/pre-paper.pdf differ
diff --git a/text/paper_01/pre-paper.tex b/text/paper_01/pre-paper.tex
index 15111b0..57b4d0a 100644
--- a/text/paper_01/pre-paper.tex
+++ b/text/paper_01/pre-paper.tex
@@ -123,7 +123,8 @@ In summary, if an ASP specification is intended to describe some observable syst
     \item If that specification is only but one of many possible candidates then that performance measure can be used, \textit{e.g.} as fitness, by algorithms searching (optimal) specifications of a dataset of observations.
 \end{enumerate}
 
-Currently, we are on the step two above: Extending a probability function (with parameters such as $x$), defined on the stable sets of a specification, to all the events of the specification. This extension must, of course, respect the axioms of probability so that probabilistic reasoning is consistent with the ASP specification. 
+Currently, we are on the step two above: Extending a probability function (with parameters such as $x$), defined on the stable sets of a specification, to all the events of the specification. This 
+ must, of course, respect the axioms of probability so that probabilistic reasoning is consistent with the ASP specification. 
 
 \section{Extending Probabilities}
 
--
libgit2 0.21.2