reformat comment

git-svn-id: http://svn.osgeo.org/metacrs/proj/trunk@2154 4e78687f-474d-0410-85f9-8d5e500ac6b2

1 files changed, 8 insertions, 7 deletions

diff --git a/src/pj_apply_gridshift.c b/src/pj_apply_gridshift.c
index c231f77e..54ef376b 100644
--- a/src/pj_apply_gridshift.c
+++ b/src/pj_apply_gridshift.c
@@ -220,13 +220,14 @@ int pj_apply_gridshift_3( projCtx ctx, PJ_GRIDINFO **tables, int grid_count,
             }
 
             /* 
-             * We don't actually have any machinery currently to set the following
-             * macro, so this is mostly kept here to make it clear how we ought to 
-             * operate if we wanted to make it super clear that an error has occured
-             * when points are outside our available datum shift areas.  But if this
-             * is on, we will find that "low value" points on the fringes of some 
-             * datasets will completely fail causing lots of problems when it is more
-             * or less ok to just not apply a datum shift.  So rather than deal with
+             * We don't actually have any machinery currently to set the 
+             * following macro, so this is mostly kept here to make it clear 
+             * how we ought to operate if we wanted to make it super clear 
+             * that an error has occured when points are outside our available
+             * datum shift areas.  But if this is on, we will find that "low 
+             * value" points on the fringes of some datasets will completely 
+             * fail causing lots of problems when it is more or less ok to 
+             * just not apply a datum shift.  So rather than deal with
              * that we just fallback to no shift. (see also bug #45).
              */
 #ifdef ERR_GRID_AREA_TRANSIENT_SEVERE