Name changes

docs/source/accelerators.rst

@@ -1,8 +1,8 @@
 .. _accelerators:
 
-************
+*********************************
-Accelerators
+Accelerators - OpenMP/CUDA/OpenCL
-************
+*********************************
 
 The most computationally intensive parts of gprMax, which are the FDTD solver loops, have been parallelised using:
 

docs/source/benchmarking.rst

@@ -1,15 +1,15 @@
 .. _benchmarking:
 
-************************
+************
-Performance benchmarking
+Benchmarking
-************************
+************
 
 This section provides information and results from performance benchmarking of gprMax.
 
 How to benchmark?
 =================
 
-The following simple models (found in the ``tests/benchmarking`` sub-package) can be used to benchmark gprMax on your own system. The models feature different domain sizes (from 100^3 to 800^3 cells) and contain a simple Hertzian dipole source in free space. The following shows an example of the 100^3 cell model:
+The following simple models (found in the ``testing/benchmarking`` sub-package) can be used to benchmark gprMax on your own system. The models feature different domain sizes (from 100^3 to 800^3 cells) and contain a simple Hertzian dipole source in free space. The following shows an example of the 100^3 cell model:
 
 .. literalinclude:: ../../testing/benchmarking/bench_100x100x100.in
     :language: none

docs/source/hpc.rst

@@ -1,10 +1,10 @@
 .. _hpc:
 
-********************************
+**************************
-High-performance computing (HPC)
+High-performance computing
-********************************
+**************************
 
-HPC environments usually require jobs to be submitted to a queue using a job script. The following are examples of job scripts for a HPC environment that uses `Open Grid Scheduler/Grid Engine <http://gridscheduler.sourceforge.net/index.html>`_, and are intended as general guidance to help you get started. Using gprMax in an HPC environment is heavily dependent on the configuration of your specific HPC/cluster, e.g. the names of parallel environments (``-pe``) and compiler modules will depend on how they were defined by your system administrator.
+High-performance computing (HPC) environments usually require jobs to be submitted to a queue using a job script. The following are examples of job scripts for a HPC environment that uses `Open Grid Scheduler/Grid Engine <http://gridscheduler.sourceforge.net/index.html>`_, and are intended as general guidance to help you get started. Using gprMax in an HPC environment is heavily dependent on the configuration of your specific HPC/cluster, e.g. the names of parallel environments (``-pe``) and compiler modules will depend on how they were defined by your system administrator.
 
 
 OpenMP example

docs/source/input_api.rst

@@ -1,8 +1,8 @@
 .. _api:
 
-*******************************
+***************************
-Model building using Python API
+Model building - Python API
-*******************************
+***************************
 
 Introduction
 ============

docs/source/input_hash_cmds.rst

@@ -1,8 +1,8 @@
 .. _commands:
 
-**********************************
+******************************
-Model building using hash commands
+Model building - hash commands
-**********************************
+******************************
 
 An input file has to be supplied to gprMax which should contain all the necessary information to run a GPR model. The input file is an ASCII text file which can be prepared with any text editor or word-processing program. In the input file the hash character (``#``) is reserved and is used to denote the beginning of a command which will be passed to gprMax. The general syntax of commands is: