small changes in various places - will submit this morning

WSSSPE1_report/WSSSPE1_summary_report.tex

@@ -286,7 +286,7 @@ \section{Introduction}
 
 This report attempts to summarize the various aspects of the workshop.
 The remainder of this paper first gives an overview of the process
-with which the workshop was put together (\S\ref{sec:process}), then
+with which the workshop was organized (\S\ref{sec:process}), then
 proceeds with summaries of the two keynote
 presentations~(\S\ref{sec:keynotes}), followed by summaries of the
 workshop papers grouped by the three thematic workshop panels to which
@@ -362,7 +362,7 @@ \section{Workshop Process and Agenda} \label{sec:process}
 Roughly following the call for papers topics, the accepted submissions
 were grouped into three main
 categories, namely \emph{Developing and Supporting Software},
-\emph{Policy}, and \emph{Communities}. Each category was assigned a
+\emph{Policy}, and \emph{Communities}. Each category was assigned to a
 panel, with three to four panelists drawn from authors of the
 associated submissions, who were each assigned to read and summarily
 present a subset of the papers associated with the panel. The process
@@ -1901,11 +1901,12 @@ \section{Case Studies} \label{sec:use-cases} % \note{lead: Ketan Maheshwari, con
 
 In this section, we discuss some of the software projects as case
 studies to better understand the points discussed during the workshop
-and described in the previous sections. We dive deeper to find how 
-they are affected by the sustainability related issues in
-practice. Additionally, we discuss issues surrounding people,
-especially the career paths of original developers and investigate to
-answer the question: \emph{are the original developers still around?}
+and described in the previous sections, and to find how 
+they are affected by sustainability issues in
+practice. 
+%Additionally, we discuss issues surrounding people,
+%especially the career paths of original developers and investigate to
+%answer the question: \emph{are the original developers still around?}
 
 We classify the software projects discussed in the workshop in two
 broad categories. First, the \emph{utility} software, comprising of
@@ -1916,7 +1917,7 @@ \section{Case Studies} \label{sec:use-cases} % \note{lead: Ketan Maheshwari, con
 \emph{scientific} software, comprising the software that was
 originally developed with an aim to solve a specific scientific
 problem.
-
+%
 % Why are we classifying software like above?
 This classification is motivated by our argument that the two kinds of
 software projects wildly vary in factors such as scope, purpose and
@@ -2055,6 +2056,8 @@ \subsection{Scientific software}
 %associated with the project, often in a part-time or ``benefactor''
 %role, or in a larger role (e.g., manager).
 
+\subsection{Distinctions}
+
 In conclusion, we find that there are distinctions in the
 characteristics and challenges faced between utility and
 scientific software projects.  
@@ -2360,7 +2363,7 @@ \section{Call For Papers} \label{sec:cfp}
 
 \section{Papers Accepted and Discussed at WSSSPE1} \label{sec:papers}
 
-\section*{Developing and Supporting Software}
+\subsection*{Developing and Supporting Software}
 
 \subsubsection*{Development Experiences}
 
@@ -2465,7 +2468,7 @@ \subsubsection*{Best Practices, Challenges, and Recommendations}
 
 \end{itemize}
 
-\section*{Policy}
+\subsection*{Policy}
 
 \subsubsection*{Modeling Sustainability}
 
@@ -2554,7 +2557,7 @@ \subsubsection*{Implementing Policy}
 
 \end{itemize}
 
-\section*{Communities, Models, and Education}
+\subsection*{Communities, Models, and Education}
 
 \subsubsection*{Communities}