chore: paper patches.

Signed-off-by: Amlal El Mahrouss <amlal@nekernel.org>

1 files changed, 13 insertions, 3 deletions

diff --git a/source/wg03/articles/article.tex b/source/wg03/articles/article.tex
index 2b6acb3..12576fc 100644
--- a/source/wg03/articles/article.tex
+++ b/source/wg03/articles/article.tex
@@ -165,7 +165,7 @@
 }]
 
 %% ============================================================
-\section{Denoting CL Execution}
+\section{Introduction}
 \label{sec:cl-introduction}
 
 We propose the following approach to represent the CL execution flow, as execution context a way to mathematically present:
@@ -174,7 +174,7 @@ We propose the following approach to represent the CL execution flow, as executi
 \end{equation}
 Such that an execution context (denoted as $\operatorname{C}$) is a program currently running with rules (denoted as $\operatorname{Trait}(\operatorname{C})$) and domains. We derive the program by its context in this formula, as we depend on $\operatorname{C}$, the $\operatorname{C}$ variable must be valid and computable in a domain $\operatorname{D}$.
 
-\section{Syntax}
+\section{The CL Syntax}
 \label{sec:cl-syntax}
 
 The syntax of a Context Language may consist of traits, and implementations. The traits can be expressed as defined in Nectar. One way to represent it mathematically is:
@@ -187,7 +187,17 @@ Traits and such must be valid in $\operatorname{C} \And$ $\Theta(\operatorname{C
 \section{Example: The Nectar 'CL'}
 \label{sec:cl-example-nectar}
 
-Developing such languages would benefit Software Engineering as we noticed a much faster cycle of software development when using the CL approach rather than the classic CL approach. We also notice that Nectar programs tends to be shorter and more expressive than average.
+Developing such languages would benefit Software Engineering as we noticed a much faster cycle of software development when using the CL approach rather than the classic CL approach.
+\\\\\\\\
+\begin{lstlisting}
+extern palloc; // parallel alloc
+
+const main() {
+  palloc(0, 0, 0);
+  return 0;
+}    
+\end{lstlisting}
+We also notice that Nectar programs tends to be shorter and more expressive than average.
 
 \section{Conclusion}
 \label{sec:cl-conclusion}