Apply most of wording suggestions from code review

Co-authored-by: Caitlin Haedrich <[email protected]>
Co-authored-by: Veronica Andreo <[email protected]>

doc/grass_database.html

@@ -3,7 +3,7 @@
 A GRASS GIS Database is simply a set of directories and files
 with certain structure which GRASS GIS works efficiently with.
 Project is a directory with data related to
-one geographic location or a real-world project.
+one geographic location or a project.
 All data within one project has the same coordinate reference system.
 A project contains Mapsets and each Mapset contains data related to
 a specific task, user or a smaller project.
@@ -57,22 +57,22 @@ <h3>GRASS Projects</h3>
 
 Project is a directory which contains GRASS Mapsets which are its subdirectories.
 All data in one Project have the same coordinate reference system (projection, datum).
-Each project must contain Mapset called PERMANENT.
+Each project must contain a Mapset called PERMANENT.
 Typically, a project contains all data related to one real-world project
 or a geographic area (geographic location or region).
-Alternatively, project can simply contain all data in a given coordinate
+Alternatively, a project can simply contain data in a given coordinate
 reference system.
 
 <p>
-GRASS project can be safely copied or moved as any other directories.
-Compressed project is usually what GRASS users exchange between each other
+GRASS projects can be safely copied or moved as any other directories.
+Compressed projects are usually what GRASS users exchange between each other
 when they want to share a lot of data.
 For example, GRASS GIS sample data are provided as projects.
 
 <p>
-Note that projects are called <em>locations</em> at some places
+Note that projects are referred to as <em>locations</em> in some places, such as older documentation.
 and in old documentation. Location is an older name for GRASS projects
-and was not completely removed yet from the code and documentation
+and has not been completely removed from the code and documentation yet 
 (contributions welcome).
 
 <p>
@@ -109,10 +109,10 @@ <h3>GRASS Mapsets</h3>
 <p>
 Mapsets are used to store maps related to one project, smaller project,
 specific task, issue or subregions.
-In multi-user environment, when a team works together on one project,
+In a multi-user environment, where team members work together on a single project,
 Mapsets support simultaneous access of several users to the maps
 stored within the same project.
-Besides access to his or her own
+Besides access to their own
 Mapset, each user can also read maps in PERMANENT Mapsent
 and in other users' Mapsets when set.
 However, each user can modify or remove only the maps
@@ -126,10 +126,10 @@ <h3>GRASS Mapsets</h3>
 and managed by <a href="g.region.html"><em>g.region</em></a>.
 
 <p>
-Mapsets can be copied and moved as directories, however only when it is clear
-that the projections of both projects
+Mapsets can be copied and moved as directories only when it is clear
+that their projections 
 (as reported by <a href="g.proj.html"><em>g.proj</em></a>)
-match each other. Since this is sometimes hard to to establish,
+match. Since this is sometimes hard to to establish,
 it is recommended to use <a href="r.proj.html"><em>r.proj</em></a>
 or <a href="v.proj.html"><em>v.proj</em></a> to reproject the data.
 The files and directories should not be moved or modified directly,
@@ -173,7 +173,7 @@ <h3>Importing, exporting and linking data</h3>
 
 <p>
 For cases when import is not desirable, an option to link external data exists.
-Projection of the linked data must match the projects's
+Projection of the linked data must match the project's
 coordinate reference system
 otherwise the external data cannot be linked. (Linking data in different
 projection is not allowed as it would require on-the-fly reprojection

doc/projectionintro.html

@@ -9,7 +9,7 @@ <h3>Projection management in general</h3>
 the desired maps have to be reprojected into it from the source project
 as explained below.
 
-<h3>Raster map projections</h3>
+<h3>Reprojecting raster maps</h3>
 
 Raster maps are backward projected in GRASS. This means that the
 user has to run the raster projection command (<a href=r.proj.html>r.proj</a>)