[GRASS-SVN] r68429 - grass/trunk/scripts/g.extension

[svn_grass at osgeo.org]

Author: neteler
Date: 2016-05-14 16:30:07 -0700 (Sat, 14 May 2016)
New Revision: 68429

Modified:
   grass/trunk/scripts/g.extension/g.extension.html
Log:
g.extension manual: language fixes

Modified: grass/trunk/scripts/g.extension/g.extension.html
===================================================================
--- grass/trunk/scripts/g.extension/g.extension.html	2016-05-14 22:59:22 UTC (rev 68428)
+++ grass/trunk/scripts/g.extension/g.extension.html	2016-05-14 23:30:07 UTC (rev 68429)
@@ -46,7 +46,7 @@
 The flag <b>-s</b> changes this install target directory to the GRASS GIS
 installation directory
 (determined by <tt>GISBASE</tt> environmental variable, e.g. <tt>/usr/</tt>)
-rather than the default directory defined via <tt>GRASS_ADDON_BASE</tt> 
+rather than the default directory defined as per  <tt>GRASS_ADDON_BASE</tt> 
 (see also documentation for <a href="variables.html">variables</a>).
 <em>g.extension</em> checks if the user has permission to write to
 <tt>GISBASE</tt> or <tt>GRASS_ADDON_BASE</tt>.
@@ -54,7 +54,7 @@
 <p>
 The place where the extensions are installed can be customized by
 the option <b>prefix</b>. Ensuring that these extensions will be accessible
-in GRASS GIS is in this case the responsibility of the user.
+in GRASS GIS is in this case in the responsibility of the user.
 
 
 <h3>Source code sources and repositories</h3>
@@ -117,7 +117,6 @@
 
 On MS-Windows systems, where compilation tools are typically not readily
 locally installed, <em>g.extension</em> downloads a precompiled executable
-locally installed, <em>g.extension</em> downloads a precompiled executable
 from the GRASS GIS project server. On all other operating systems
 where it is not difficult to install compilation tools,
 <em>g.extension</em> downloads the source code of the requested
@@ -203,7 +202,6 @@
 Note that because of MS-Windows operating system architecture,
 only official repository is supported on this platform.
 
-
 <h3>Installing when writing a module locally</h3>
 
 Having source code of a GRASS module in a directory on disk