@@ -224,11 +224,11 @@ Often this will require extra libraries to be linked in, or extra header and obj
224This is made possible through the following directives:
224This is made possible through the following directives:
226\begin{itemize}
226\begin{itemize}
227−\item \texttt{\%lib target "x"} --- include the \texttt{libx} library. If the target is \texttt{C} equivalent to passing the
227+\item \texttt{\%lib target "x"} --- include the \texttt{libx} library. If the target is \texttt{C} this is equivalent to passing the
228\texttt{-lx} option to \texttt{gcc}. If the target is Java the library will be interpreted as a
228\texttt{-lx} option to \texttt{gcc}. If the target is Java the library will be interpreted as a
229−"groupId:artifactId:packaging:version" coordinate for maven.
229+"groupId:artifactId:packaging:version" dependency coordinate for maven.
230−\item \texttt{\%include target "x"} --- use the header file or import \texttt{x} for the given backend target.
230+\item \texttt{\%include target "x"} --- use the header file or import \texttt{x} for the given back end target.
231−\item \texttt{\%link target "x.o"} --- link with the object file \texttt{x.o} when using the given backend target.
231+\item \texttt{\%link target "x.o"} --- link with the object file \texttt{x.o} when using the given back end target.
232\item \texttt{\%dynamic "x.so"} --- dynamically link the interpreter with the shared object \texttt{x.so}.
232\item \texttt{\%dynamic "x.so"} --- dynamically link the interpreter with the shared object \texttt{x.so}.
233\end{itemize}
233\end{itemize}