%s/PostgresQL/PostgreSQL/g #3672

doc/sphinx-guides/source/_static/util/createsequence.sql

@@ -19,7 +19,7 @@ CACHE 1;
 
 ALTER TABLE datasetidentifier_seq OWNER TO "dvnapp";
 
--- And now create a PostgresQL FUNCTION, for JPA to 
+-- And now create a PostgreSQL FUNCTION, for JPA to
 -- access as a NamedStoredProcedure:
 
 CREATE OR REPLACE FUNCTION generateIdentifierAsSequentialNumber(

doc/sphinx-guides/source/admin/timers.rst

@@ -24,7 +24,7 @@ The following JVM option instructs the application to act as the dedicated timer
 
 **IMPORTANT:** Note that this option is automatically set by the Dataverse installer script. That means that when **configuring a multi-server cluster**, it will be the responsibility of the installer to remove the option from the :fixedwidthplain:`domain.xml` of every node except the one intended to be the timer server. We also recommend that the following entry in the :fixedwidthplain:`domain.xml`: ``<ejb-timer-service timer-datasource="jdbc/VDCNetDS">`` is changed back to ``<ejb-timer-service>`` on all the non-timer server nodes. Similarly, this option is automatically set by the installer script. Changing it back to the default setting on a server that doesn't need to run the timer will prevent a potential race condition, where multiple servers try to get a lock on the timer database. 
 
-**Note** that for the timer to work, the version of the PostgresQL JDBC driver your instance is using must match the version of your PostgresQL database. See the 'Timer not working' section of the :doc:`/admin/troubleshooting` guide.
+**Note** that for the timer to work, the version of the PostgreSQL JDBC driver your instance is using must match the version of your PostgreSQL database. See the 'Timer not working' section of the :doc:`/admin/troubleshooting` guide.
 
 Harvesting Timers 
 -----------------

doc/sphinx-guides/source/admin/troubleshooting.rst

@@ -41,7 +41,7 @@ Note that it may or may not work on your system, so it is provided as an example
 Timer not working 
 -----------------
 
-Dataverse relies on the EJB timer to perform scheduled tasks: harvesting from remote servers, updating the local OAI sets and running metadata exports. If these scheduled jobs are not running on your server, this may be the result of the incompatibility between the version of PostgresQL database you are using, and PostgresQL JDBC driver in use by your instance of Glassfish. The symptoms: 
+Dataverse relies on the EJB timer to perform scheduled tasks: harvesting from remote servers, updating the local OAI sets and running metadata exports. If these scheduled jobs are not running on your server, this may be the result of the incompatibility between the version of PostgreSQL database you are using, and PostgreSQL JDBC driver in use by your instance of Glassfish. The symptoms:
 
 If you seeing the following in your server.log: 
 
@@ -55,6 +55,6 @@ followed by an Exception stack trace with these lines in it:
 
 
 it most likely means that it is the JDBC driver incompatibility that's preventing the timer from working correctly. 
-Make sure you install the correct version of the driver. For example, if you are running the version 9.3 of PostgresQL, make sure you have the driver postgresql-9.3-1104.jdbc4.jar in your :fixedwidthplain:`<GLASSFISH FOLDER>/glassfish/lib` directory. Go `here <https://jdbc.postgresql.org/download.html>`_ 
+Make sure you install the correct version of the driver. For example, if you are running the version 9.3 of PostgreSQL, make sure you have the driver postgresql-9.3-1104.jdbc4.jar in your :fixedwidthplain:`<GLASSFISH FOLDER>/glassfish/lib` directory. Go `here <https://jdbc.postgresql.org/download.html>`_
 to download the correct version of the driver. If you have an older driver in glassfish/lib, make sure to remove it, replace it with the new version and restart Glassfish. (You may need to remove the entire contents of :fixedwidthplain:`<GLASSFISH FOLDER>/glassfish/domains/domain1/generated` before you start Glassfish).