Merge pull request #4818 from DelazJ/spelling

Fix some spelling issues

INSTALL

@@ -116,7 +116,7 @@ Optional dependencies:
   is not installed with rpath. The desired GRASS version is chosen on runtime by setting
   LD_LIBRARY_PATH or PATH.
 - for georeferencer - GSL >= 1.8
-- for postgis support - PostgreSQL >= 8.0.x
+- for PostGIS support - PostgreSQL >= 8.0.x
 - for gps plugin - gpsbabel
 - for mapserver export and PyQGIS - Python >= 3.3
 - for python support - SIP >= 4.12, PyQt >= 5.3 must match Qt version, Qscintilla2
@@ -1245,17 +1245,17 @@ osgEarth), try bypassing ccache.
   =========================================================
 
 Download William Kyngesburye's excellent GDAL Complete package that includes
-PROJ, GEOS, GDAL, SQLite3, Spatialite, and image libraries, as frameworks.
+PROJ, GEOS, GDAL, SQLite3, SpatiaLite, and image libraries, as frameworks.
 There are also GSL and FreeType frameworks.
 
 http://www.kyngchaos.com/software/frameworks
 
 Once downloaded, open and install the frameworks.
 
-William provides an additional installer package for Postgresql (for PostGIS
-support).  QGIS just needs the libpq client library, so unless you want to
+William provides an additional installer package for PostgreSQL (for PostGIS
+support). QGIS just needs the libpq client library, so unless you want to
 setup the full Postgres + PostGIS server, all you need is the client-only
-package.  It's available here:
+package. It's available here:
 
 http://www.kyngchaos.com/software/postgres
 

NEWS

@@ -800,7 +800,7 @@ changed so we will just provide a bullet list of key new features here.
  - Make NULL value string representation configurable.
  - Fix feature updates in feature form from attribute table.
  - Add support for NULL values in value maps (comboboxes).
- - Use layer names instead of ids in drop down list when loading value maps from layers.
+ - Use layer names instead of ids in drop-down list when loading value maps from layers.
  - Support feature form expression fields: line edits on the form which
       name prefix "expr_" are evaluated. Their value is interpreted as field
       calculator string and replaced with the calculated value.
@@ -1695,7 +1695,7 @@ Added Simon splash screen
 Fixed command line loading bug to eliminate bogus warning for vector layers
 Modified splashscreen.cpp to allow specification of x,y for text drawing on
    the splash image
-Imperfectly fixed problem where postgis attributes aren't displayed if the
+Imperfectly fixed problem where PostGIS attributes aren't displayed if the
    primary key is not of type int4 (bug 1042706).
 Added Latvian translation file (untranslated at present)
 
@@ -2540,7 +2540,7 @@ Added QgsRasterLayer::filterLayer which gets called near the end of each of
 
 2004-03-06 [didge] 0.1.0devel6
 Changed configure stuff to write DEFINES in config.h.
-   Postgresql stuff needs testing as I commented the compileflags in src/Makefile.am
+   PostgreSQL stuff needs testing as I commented the compileflags in src/Makefile.am
 Infos will be posted on the devel mailinglist
 
 2004-03-04 [ts] 0.1.0devel5

README.md

@@ -42,7 +42,7 @@ modified.
  * PostgreSQL/PostGIS
  * GRASS
  * GeoPackage
- * Spatialite
+ * SpatiaLite
  * [Other OGR supported formats](http://www.gdal.org/ogr_formats.html)
  * MSSQL
  * Oracle

cmake/FindSpatiaLite.cmake

@@ -31,7 +31,7 @@ IF (APPLE)
     SET (CMAKE_FIND_FRAMEWORK_save ${CMAKE_FIND_FRAMEWORK} CACHE STRING "" FORCE)
     SET (CMAKE_FIND_FRAMEWORK "ONLY" CACHE STRING "" FORCE)
     FIND_PATH(SPATIALITE_INCLUDE_DIR SQLite3/spatialite.h)
-    # if no spatialite header, we don't want sqlite find below to succeed
+    # if no SpatiaLite header, we don't want SQLite find below to succeed
     IF (SPATIALITE_INCLUDE_DIR)
       FIND_LIBRARY(SPATIALITE_LIBRARY SQLite3)
       # FIND_PATH doesn't add "Headers" for a framework

doc/INSTALL.html

@@ -226,7 +226,7 @@ <H1>2. Overview</H1>
   is not installed with rpath. The desired GRASS version is chosen on runtime by setting
   LD_LIBRARY_PATH or PATH.
 <LI>for georeferencer - GSL &gt;= 1.8
-<LI>for postgis support - PostgreSQL &gt;= 8.0.x
+<LI>for PostGIS support - PostgreSQL &gt;= 8.0.x
 <LI>for gps plugin - gpsbabel
 <LI>for mapserver export and PyQGIS - Python &gt;= 3.3
 <LI>for python support - SIP &gt;= 4.12, PyQt &gt;= 5.3 must match Qt version, Qscintilla2
@@ -1744,10 +1744,10 @@ <H2>5.4. Install development frameworks for QGIS dependencies</H2>
 Once downloaded, open and install the frameworks.
 </P>
 <P>
-William provides an additional installer package for Postgresql (for PostGIS
-support).  QGIS just needs the libpq client library, so unless you want to
+William provides an additional installer package for PostgreSQL (for PostGIS
+support). QGIS just needs the libpq client library, so unless you want to
 setup the full Postgres + PostGIS server, all you need is the client-only
-package.  It's available here:
+package. It's available here:
 </P>
 <P>
 <A HREF="http://www.kyngchaos.com/software/postgres">http://www.kyngchaos.com/software/postgres</A>

doc/news.html

@@ -917,7 +917,7 @@ <H2>14.6. Providers and Data Handling</H2>
  <LI>Make NULL value string representation configurable.
  <LI>Fix feature updates in feature form from attribute table.
  <LI>Add support for NULL values in value maps (comboboxes).
- <LI>Use layer names instead of ids in drop down list when loading value maps from layers.
+ <LI>Use layer names instead of ids in drop-down list when loading value maps from layers.
  <LI>Support feature form expression fields: line edits on the form which
       name prefix "expr_" are evaluated. Their value is interpreted as field
       calculator string and replaced with the calculated value.
@@ -2865,7 +2865,7 @@ <H1>28. 0.5</H1>
 <P>
 2004-03-06 [didge] 0.1.0devel6
 Changed configure stuff to write DEFINES in config.h.
-   Postgresql stuff needs testing as I commented the compileflags in src/Makefile.am
+   PostgreSQL stuff needs testing as I commented the compileflags in src/Makefile.am
 Infos will be posted on the devel mailinglist
 </P>
 <P>

doc/news.t2t

@@ -779,7 +779,7 @@ changed so we will just provide a bullet list of key new features here.
  - Make NULL value string representation configurable.
  - Fix feature updates in feature form from attribute table.
  - Add support for NULL values in value maps (comboboxes).
- - Use layer names instead of ids in drop down list when loading value maps from layers.
+ - Use layer names instead of ids in drop-down list when loading value maps from layers.
  - Support feature form expression fields: line edits on the form which
       name prefix "expr_" are evaluated. Their value is interpreted as field
       calculator string and replaced with the calculated value.
@@ -1646,7 +1646,7 @@ Added Simon splash screen
 Fixed command line loading bug to eliminate bogus warning for vector layers
 Modified splashscreen.cpp to allow specification of x,y for text drawing on
    the splash image
-Imperfectly fixed problem where postgis attributes aren't displayed if the
+Imperfectly fixed problem where PostGIS attributes aren't displayed if the
    primary key is not of type int4 (bug 1042706).
 Added Latvian translation file (untranslated at present)
 

doc/overview.t2t

@@ -36,7 +36,7 @@ Optional dependencies:
   is not installed with rpath. The desired GRASS version is chosen on runtime by setting
   LD_LIBRARY_PATH or PATH.
 - for georeferencer - GSL >= 1.8
-- for postgis support - PostgreSQL >= 8.0.x
+- for PostGIS support - PostgreSQL >= 8.0.x
 - for gps plugin - gpsbabel
 - for mapserver export and PyQGIS - Python >= 3.3
 - for python support - SIP >= 4.12, PyQt >= 5.3 must match Qt version, Qscintilla2

python/analysis/openstreetmap/qgsosmdatabase.sip

@@ -41,7 +41,7 @@ class QgsOSMDatabase
 
     void setFileName( const QString &dbFileName );
 %Docstring
-Setter for the spatialite database.
+Setter for the SpatiaLite database.
 %End
     QString filename() const;
 %Docstring

python/console/console_sci.py

@@ -629,7 +629,7 @@ def __init__(self, parent):
         self.setWindowTitle(QCoreApplication.translate("PythonConsole",
                                                        "Python Console - Command History"))
         self.listView.setToolTip(QCoreApplication.translate("PythonConsole",
-                                                            "Double click on item to execute"))
+                                                            "Double-click on item to execute"))
         self.model = QStandardItemModel(self.listView)
 
         self._reloadHistory()

python/core/qgscoordinatereferencesystem.sip

@@ -190,7 +190,7 @@ Constructs an invalid CRS object
 
     explicit QgsCoordinateReferenceSystem( const long id, CrsType type = PostgisCrsId );
 %Docstring
- Constructor a CRS object using a postgis SRID, an EPSG code or an internal QGIS CRS ID.
+ Constructor a CRS object using a PostGIS SRID, an EPSG code or an internal QGIS CRS ID.
 .. note::
 
    We encourage you to use EPSG code, WKT or Proj4 to describe CRS's in your code
@@ -304,7 +304,7 @@ Allows direct construction of QVariants from QgsCoordinateReferenceSystem.
     bool createFromSrid( const long srid );
 %Docstring
  Sets this CRS by lookup of the given PostGIS SRID in the CRS database.
- \param srid The postgis SRID for the desired spatial reference system.
+ \param srid The PostGIS SRID for the desired spatial reference system.
  :return: True on success else false
 /     // TODO QGIS 3: remove unless really necessary - let's use EPSG codes instead
  :rtype: bool

python/core/qgsvectorlayer.sip

@@ -25,10 +25,10 @@ class QgsVectorLayer : QgsMapLayer, QgsExpressionContextGenerator, QgsFeatureSin
  The QgsVectorLayer is instantiated by specifying the name of a data provider,
  such as postgres or wfs, and url defining the specific data set to connect to.
  The vector layer constructor in turn instantiates a QgsVectorDataProvider subclass
- corresponding to the provider type, and passes it the url.  The data provider
+ corresponding to the provider type, and passes it the url. The data provider
  connects to the data source.
 
- The QgsVectorLayer provides a common interface to the different data types.  It also
+ The QgsVectorLayer provides a common interface to the different data types. It also
  manages editing transactions.
 
   Sample usage of the QgsVectorLayer class:
@@ -45,8 +45,8 @@ class QgsVectorLayer : QgsMapLayer, QgsExpressionContextGenerator, QgsFeatureSin
  \subsection memory Memory data providerType (memory)
 
  The memory data provider is used to construct in memory data, for example scratch
- data or data generated from spatial operations such as contouring.  There is no
- inherent persistent storage of the data.  The data source uri is constructed.  The
+ data or data generated from spatial operations such as contouring. There is no
+ inherent persistent storage of the data. The data source uri is constructed. The
  url specifies the geometry type ("point", "linestring", "polygon",
  "multipoint","multilinestring","multipolygon"), optionally followed by url parameters
  as follows:
@@ -59,35 +59,35 @@ class QgsVectorLayer : QgsMapLayer, QgsExpressionContextGenerator, QgsFeatureSin
    Specifies that the layer will be constructed with a spatial index
 
  - field=name:type(length,precision)
-   Defines an attribute of the layer.  Multiple field parameters can be added
-   to the data provider definition.  type is one of "integer", "double", "string".
+   Defines an attribute of the layer. Multiple field parameters can be added
+   to the data provider definition. type is one of "integer", "double", "string".
 
  An example url is "Point?crs=epsg:4326&field=id:integer&field=name:string(20)&index=yes"
 
  \subsection ogr OGR data provider (ogr)
 
  Accesses data using the OGR drivers (http://www.gdal.org/ogr/ogr_formats.html). The url
- is the OGR connection string.  A wide variety of data formats can be accessed using this
+ is the OGR connection string. A wide variety of data formats can be accessed using this
  driver, including file based formats used by many GIS systems, database formats, and
- web services.  Some of these formats are also supported by custom data providers listed
+ web services. Some of these formats are also supported by custom data providers listed
  below.
 
- \subsection spatialite Spatialite data provider (spatialite)
+ \subsection spatialite SpatiaLite data provider (spatialite)
 
- Access data in a spatialite database. The url defines the connection parameters, table,
- geometry column, and other attributes.  The url can be constructed using the
+ Access data in a SpatiaLite database. The url defines the connection parameters, table,
+ geometry column, and other attributes. The url can be constructed using the
  QgsDataSourceUri class.
 
- \subsection postgres Postgresql data provider (postgres)
+ \subsection postgres PostgreSQL data provider (postgres)
 
- Connects to a postgresql database.  The url defines the connection parameters, table,
- geometry column, and other attributes.  The url can be constructed using the
+ Connects to a PostgreSQL database. The url defines the connection parameters, table,
+ geometry column, and other attributes. The url can be constructed using the
  QgsDataSourceUri class.
 
  \subsection mssql Microsoft SQL server data provider (mssql)
 
- Connects to a Microsoft SQL server database.  The url defines the connection parameters, table,
- geometry column, and other attributes.  The url can be constructed using the
+ Connects to a Microsoft SQL server database. The url defines the connection parameters, table,
+ geometry column, and other attributes. The url can be constructed using the
  QgsDataSourceUri class.
 
  \subsection wfs WFS (web feature service) data provider (wfs)