A couple of typos in the guide.

git-svn-id: https://svn.ligo.caltech.edu/svn/bayeswave/trunk@88 c56465c9-8126-4a4f-9d7d-ac845eff4865

doc/guide.tex

@@ -237,7 +237,7 @@ Move to a new directory and try running the example command line.   You will hav
 \code{export PATH=[path to]/bayeswave/trunk/src/:\$PATH}
 This will run for $\sim$10 minutes.  Real runs take $\sim4-48$ hours, depending on the settings and the models being used.  Really long segments (1024 s) of really glitchy data can take a week.
 
-This run will simulate Advanced LIGO data for H1 with a random seed for the noise realization {\tt dataseed} $=1234$; a low-frequency cutoff of {\tt IFO-flow} $=40$ Hz; a total observation time of {\tt seglen} $=1234$ s; and a sampling rate of {\tt state} $=512$ Hz.
+This run will simulate Advanced LIGO data for H1 with a random seed for the noise realization {\tt dataseed} $=1234$; a low-frequency cutoff of {\tt IFO-flow} $=40$ Hz; a total observation time of {\tt seglen} $=4$ s; and a sampling rate of {\tt srate} $=512$ Hz.
 
 Because we are using {\tt LALInference} for data handling (which expects in-spiral signals) the {\tt trigtime} argument gives the GPS time which will be analyzed.  
 {\bf The analysis window will be {\tt seglen} seconds long and will end 2 seconds after {\tt trigtime} }.
@@ -273,7 +273,7 @@ The *.run files contain settings for each phase of the run
 \end{quote}
 	
 The {\tt [model]\_1\_evidence.dat} files contain the integrand of the evidence ($Z$) integral.  They are used for diagnosing the run.
-The file {\tt evidence.dat} has contains the computed evidence for each model  
+The file {\tt evidence.dat} contains the computed evidence for each model. 
 The columns are:
 \begin{quote}
  {\tt model} , $\ln Z({\rm \tt model})$ , $P({\rm \tt model})$
@@ -309,7 +309,7 @@ There are four types of chain files:
 \end{quote}
 where $I = [0,N_{IFO}-1]$ and $N_{IFO}$ is the number of IFOs,
 
-The {\tt intchain} files contain roughly the sam information as the intrinsic parameter  (which is roughly the same as the intrinsic parameters from the chain -- these files need to be renamed and reformatted):
+The {\tt intchain} files contain roughly the same information as the intrinsic parameter  (which is roughly the same as the intrinsic parameters from the chain -- these files need to be renamed and reformatted):
 \begin{quote}
 ${\rm cycle} , \ln {\rm likelihood} , N_\signal , N_\glitch({\rm ifo}_0) , ... , N_\glitch({\rm ifo}_{\NI-1}) , \eta({\rm ifo}_0) , ... , \eta(\rm{ifo}_{\NI-1})$
 \end{quote}
@@ -416,7 +416,7 @@ The time slides should all be integer seconds but the difference of the GPS time
 \hyperlink{ToC}{\textcolor{blue}{Back to Table of Contents}}
 
 \subsection{Channels }
-We are set up to run on h(t) and DARM-ERR.  If other channels are of interest they are easy to add, we just need to know reasonable ranges for the PSD
+We are set up to run on h(t) and DARM-ERR.  If other channels are of interest they are easy to add, we just need to know reasonable ranges for the PSD.
 Currently the supported channel types are 
 For H1 or L1:
 \begin{quote}