get rid of last remnants of "border" terminology

git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinAnalysis/AHFinderDirect/trunk@196 f88db872-0e4f-0410-b76b-b9085cfa78c5

1 files changed, 6 insertions, 6 deletions

diff --git a/src/patch/grid.hh b/src/patch/grid.hh
index 596cce1..fce5392 100644
--- a/src/patch/grid.hh
+++ b/src/patch/grid.hh
@@ -317,11 +317,11 @@ private:
 // in degrees (drho,dsigma); this is useful for humans trying to specify
 // things in parameter files.
 //
-// The nominal (non-bordered) angular grid boundaries may coincide with
-// grid points, or they may be at "half-integer" grid coordinates.  That
-// is, suppose we have a unit grid spacing, and a boundary at an angular
-// coordinate of 0; then the grid may be either 0, 1, 2, ..., or
-// 0.5, 1.5, 2.5, ... .
+// The nominal (not including the ghost zones) angular grid boundaries
+// may coincide with grid points, or they may be at "half-integer" grid
+// coordinates.  That is, suppose we have a unit grid spacing, and a boundary
+// at an angular coordinate of 0; then the grid may be either 0, 1, 2, ...,
+// or 0.5, 1.5, 2.5, ... .
 //
 
 class	grid
@@ -495,7 +495,7 @@ private:
 	grid& operator=(const grid& rhs);
 
 private:
-	// range of these is the bordered grid
+	// range of these is the full grid (including ghost zones)
 	const linear_map<fp> rho_map_, sigma_map_;
 
 	// angular boundaries of nominal grid