Sockeye TN: Update hake section
@@ -605,8 +605,9 @@ Listings~\ref{lst:prolog_example} shows the generated Prolog code for the Sockey
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
SoC descriptions are placed in the directory \pathname{SOURCE/socs} with the file extension \pathname{soc}.
Each top-level Sockeye file has to be added to the list of SoCs in the Hakefile in the same directory.
-The Hake rule for Sockeye files compiles all the listed files to \pathname{BUILD/sockeyefacts/<filename>.pl} if they are specified as a dependency in some Hakefile.
-The rule will also generate a \pathname{.depend} file (with the \texttt{-d} option of the Sockeye compiler) so that \texttt{make} recompiles the file also when imported files are changed.
+When passed a filename (without extension), the function \verb|sockeye :: String -> HRule| creates a rule to compile the file \pathname{SOURCE/socs/<filename>.soc} to \pathname{BUILD/sockeyefacts/<filename>.pl}.
+The rule will also generate \pathname{BUILD/sockeyefacts/<filename>.pl.depend} (with the \texttt{-d} option of the Sockeye compiler) and include it in the Makefile.
+This causes \texttt{make} to rebuild the file also when imported files are changed.
To add a compiled Sockeye specification to the SKB RAM-disk, the filename can be added to the \varname{sockeyeFiles} list in the SKBs Hakefile.
