deletions | additions       diff --git a/serendipity-in-computational-context.tex b/serendipity-in-computational-context.tex  index fb98170..491b6fa 100644  --- a/serendipity-in-computational-context.tex  +++ b/serendipity-in-computational-context.tex 
...
above formal enough? Could these bulleted ideas be condensed into  one or two paragraphs]}  \textbf{[AJ I'd say Yes to including the repetition. Always good to include ’linking’ 'linking’  text between sections, makes the narrative easier to read. Regarding condensing bulleted ideas into paragraphs, would prefer to keep the bullets as it's a cleaner layout compared to dense text.]} \subsubsection*{Key condition for serendipity} 
...
%% Workshop ``technologically unrealistic'' or similar, so let's try to  %% make sure we're not overpromising. I think the other paper makes it  %% all fairly realistic.]}  To evaluate our computational framework in usage, we apply a thought experiments around scenarios where there is high potential for serendipity serendipity.  In \cite{poetry-workshop}, we investigate investigated  the feasibility of using designs of this sort in multi-agent systems that learn by sharing and  discussing partial understandings. %%This earlier paper remains broadly  %% indicative, however, and the ideas it describes can see considerable 
...
in other words, what they find in the presented work. In some  settings this is augmented with {\tt suggestions}. After any {\tt  questions} from the author, the commentators may make {\tt replies}  to offer clarification. We return to discuss Writers Workshops and serendipity in Section \ref{future}.} \ref{sec:futurework}.}  This is how these steps map into the diagram  we introduced in Section \ref{sec:background}: