Fixed typos and misspellings, added links to potential figure drawing approaches

Lectures/L15_MIS/MIS.tex

@@ -77,6 +77,11 @@
 \item L18 - MIS Presentations
 \ei
 \item Mathematical review (\cite{HoffmanAndStrooper1995} and separate slides)
+\item Potential software for drawing figures
+\bi
+\item \href{https://app.diagrams.net/} {draw.io}
+\item \href{https://www.bu.edu/math/files/2013/08/tikzpgfmanual.pdf} {Tkiz} 
+\ei
 \ei
 
 \end{frame}
@@ -165,7 +170,7 @@ Final Documentation & Dec 9\\
 \item Uses Relation Hierarchy
 \item Syntax
 \bi
-\item Access Programs (types of inptus and outputs)
+\item Access Programs (types of inputs and outputs)
 \item State Variables
 \item Environment Variables
 \item Type of module (record, library, abstract object, ADT, generic)
@@ -614,8 +619,10 @@ are isolated to their own access programs (like submodules). %    This, combined
 \item Specify imported constants
 \item Specify imported types
 \item Specify imported access programs
-\item The specification of one module will often depend on using the interface specified by another module
-\item When there are many modules the uses information is very useful for navigation of the documentation
+\item The specification of one module will often depend on using the interface
+  specified by another module
+\item When there are many modules the uses information is very useful for
+  navigation of the documentation
 \item Documents the use relation between modules
 \end{itemize}
 \end{frame}
@@ -693,7 +700,7 @@ seq\_size & ~ & integer & ~\\
 \item After every access routine call, the state should satisfy the invariant
 \item Cannot have a state invariant without state variables
 \item Just stating the invariant does not ``enforce'' it, the access routine semantics need to maintain it
-\item Useful for understandabilty, testing and for proof
+\item Useful for understandability, testing and for proof
 \end{itemize}
 \end{itemize}
 
@@ -802,7 +809,7 @@ seq\_init():
 
 \begin{frame}
 
-\frametitle{Exception Signaling}
+\frametitle{Exception Signalling}
 
 \begin{itemize}
 \item Useful to think about exceptions in the design process
@@ -826,11 +833,15 @@ seq\_init():
 \frametitle{Assumptions versus Exceptions}
 
 \begin{itemize}
-\item The assumptions section lists assumptions the module developer is permitted to make about the programmer's behaviour
+\item The assumptions section lists assumptions the module developer is
+  permitted to make about the programmer's behaviour
 \item Assumptions are expressed in prose
-\item Use assumptions to simplify the MIS and to reduce the complexity of the final implementation
-\item Interface design should provide the programmer with a means to check so that they can avoid exceptions
-\item When an exceptions occurs no state transitions should take place, any output is {\it don't care}
+\item Use assumptions to simplify the MIS and to reduce the complexity of the
+  final implementation
+\item Interface design should provide the programmer with a means to check so
+  that they can avoid exceptions
+\item When an exceptions occurs no state transitions should take place, any
+  output is {\it don't care}
 \end{itemize}
 
 \end{frame}
@@ -906,7 +917,7 @@ seq\_init():
   procedures that manipulate instances of the type
 \item Encapsulates the details of the implementation of the type
 \item Multiple instances of the object
-\item Keyword \textbf{Tempalate} in MIS
+\item Keyword \textbf{Template} in MIS
 \item Example
 \bi
 \item