Updates

git-svn-id: http://svn.cactuscode.org/flesh/trunk@1298 17b73243-c579-4c4c-a9d2-2d5706c11dac

2 files changed, 13 insertions, 12 deletions

diff --git a/doc/UsersGuide/RunningCactus.tex b/doc/UsersGuide/RunningCactus.tex
index fc5d4a45..4444af9d 100644
--- a/doc/UsersGuide/RunningCactus.tex
+++ b/doc/UsersGuide/RunningCactus.tex
@@ -569,11 +569,11 @@ contains compilers and compilation flags for a configuration.
 \item [{\tt make.extra.defn}]
 contains details about extra packages used in the configuration.
 
-\item [{\tt config.h}]
+\item [{\tt cctk\_Config.h}]
 The main configuration header file, containing architecture specific
 definitions.
 
-\item [{\tt cctk\_archdefs.h}]
+\item [{\tt cctk\_Archdefs.h}]
 An architecture specific header file containing things which cannot be
 automatically detected, and have thus been hand-coded for this architecture.
 \end{Lentry}
@@ -733,6 +733,7 @@ the same.
 
 \begin{Lentry}
 
+\item [{\tt gmake <target> THORNLIST=<file> [THORNLIST\_DIR=<dir>]}] uses the file {\tt dir/file} as the ThornList for the configuration. The directory defaults to the current directory
 \item [{\tt gmake <target> SILENT=no}] prints the commands that gmake is executing
 \item [{\tt gmake <target> TJOBS=<number>}] compile in parallel, across thorns 
 \item [{\tt gmake <target> FJOBS=<number>}] compile in parallel, across files within each thorn
diff --git a/doc/UsersGuide/ThornWriters.tex b/doc/UsersGuide/ThornWriters.tex
index f157d74c..975bbd30 100644
--- a/doc/UsersGuide/ThornWriters.tex
+++ b/doc/UsersGuide/ThornWriters.tex
@@ -637,7 +637,7 @@ Any routine using Cactus argument lists (for example all
 routines called from the scheduler) should include at the
 top of the file the header
 \begin{verbatim}
-#include "cctk_arguments.h"
+#include "cctk_Arguments.h"
 \end{verbatim}
 
 A Cactus macro {\tt CCTK\_FARGUMENTS} is defined for each thorn
@@ -671,7 +671,7 @@ using them with the macro {\tt DECLARE\_PARAMETERS}
 Any routine using Cactus parameters should include at
 the top of the file the header
 \begin{verbatim}
-#include "cctk_parameters.h"
+#include "cctk_Parameters.h"
 \end{verbatim}
 
 In Fortran, special care should be taken with string valued parameters.
@@ -690,8 +690,8 @@ well as the standard Cactus variables. The source file should look like
 
 \begin{verbatim}
 #include "cctk.h"
-#include "cctk_arguments.h"
-#include "cctk_parameters.h"
+#include "cctk_Arguments.h"
+#include "cctk_Parameters.h"
 
       subroutine MyFRoutine(CCTK_FARGUMENTS)
 
@@ -774,7 +774,7 @@ Any routine using Cactus argument lists (for example all
 routines called from the scheduler) should include at the
 top of the file the header
 \begin{verbatim}
-#include "cctk_arguments.h"
+#include "cctk_Arguments.h"
 \end{verbatim}
 
 A Cactus macro {\tt CCTK\_CARGUMENTS} is defined for each thorn
@@ -806,7 +806,7 @@ changing a parameter is undefined (at best).
 Any routine using Cactus parameters should include at
 the top of the file the header
 \begin{verbatim}
-#include "cctk_parameters.h"
+#include "cctk_Parameters.h"
 \end{verbatim}
 
 The parameters should be declared at the start of the routine
@@ -818,8 +818,8 @@ The C routine "MyCRoutine" is scheduled in the {\tt schedule.ccl} file,
 and uses Cactus parameters. The source file should look like
 \begin{verbatim}
 #include "cctk.h"
-#include "cctk_arguments.h"
-#include "cctk_parameters.h"
+#include "cctk_Arguments.h"
+#include "cctk_Parameters.h"
 
 void MyCRoutine(CCTK_CARGUMENTS)
 {
@@ -1383,7 +1383,7 @@ processors.
 \item[{\tt int type\_out\_arrays}, {\tt type\_in\_arrays}] 
 specifies the type of the gridfunction 
 you are communicating. Use the values as specified in
-\ref{sec:cctk_datatypes}. Note: do not {\em mix} datatypes: e.g. in
+\ref{sec:datyansi}. Note: do not {\em mix} datatypes: e.g. in
 Fortran do not declare a variable as {\tt integer} and then specify  
 the type {\tt CCTK\_VARIABLE\_INT} in the reduction command. These
 types need not be the same on some architectures and will conflict.
@@ -1436,7 +1436,7 @@ set to $-1$. Otherwise {\tt processor} will hold the reduction result.
 \item[{\tt data\_type}]
 specifies the type of the gridfunction 
 you are communicating. Use the values as specified in
-\ref{sec:cctk_datatypes}.
+\ref{sec:datyansi}.
 \end{Lentry}
 
 \vskip 0.25cm