From 361be3827ecb0e2145a308964d6bd86f7fce8490 Mon Sep 17 00:00:00 2001
From: Brian Huffman <huffman@galois.com>
Date: Thu, 5 Oct 2017 11:08:34 -0700
Subject: [PATCH] Fix incorrect spacing after abbreviation "vs."

---
 docs/ProgrammingCryptol/crashCourse/CrashCourse.tex | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/ProgrammingCryptol/crashCourse/CrashCourse.tex b/docs/ProgrammingCryptol/crashCourse/CrashCourse.tex
index f2762036..e590bb1e 100644
--- a/docs/ProgrammingCryptol/crashCourse/CrashCourse.tex
+++ b/docs/ProgrammingCryptol/crashCourse/CrashCourse.tex
@@ -2877,7 +2877,7 @@ yields the inferred type:
 \end{Answer}
 
 %=====================================================================
-\section{Type vs. value variables}\indTypeVariables
+\section{Type vs.\ value variables}\indTypeVariables
 \label{sec:type-vs.-value}
 
 \todo[inline]{Rewrite this whole section to better clarify object- vs. type
@@ -2920,7 +2920,7 @@ statically---they never change at runtime.\footnote{In this way,
   the term ``type-level naturals''.}
 
 %~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-\subsection{Positional vs. named type
+\subsection{Positional vs.\ named type
   arguments}\indTypePositionalArguments
 \label{sec:positional-vs.-named}
 
@@ -2968,7 +2968,7 @@ clear, as in:
   resolution, in the presence of positional arguments.}
 
 %~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-\subsection{Type context vs. variable context}\indTypeContext
+\subsection{Type context vs.\ variable context}\indTypeContext
 \label{sec:type-context-vs}
 
 You have seen, in the discussion of type variables above, that Cryptol