--- a/Sphinx/source/developers/db-versioning.rst	Wed Sep 19 21:29:17 2018 +0200
+++ b/Sphinx/source/developers/db-versioning.rst	Thu Sep 20 15:00:49 2018 +0200
@@ -26,7 +26,7 @@
 Version                           DB v2   DB v3   DB v4   DB v5   DB v6
 ===============================   =====   =====   =====   =====   =====
 Mainline                                  u       u       u       x
-Orthanc 0.9.5 - Orthanc 1.4.1             u       u       u       x
+Orthanc 0.9.5 - Orthanc 1.4.2             u       u       u       x
 Orthanc 0.8.5 - Orthanc 0.9.4             u       u       x
 Orthanc 0.7.3 - Orthanc 0.8.4             u       x
 Orthanc 0.4.0 - Orthanc 0.7.2             x

--- a/Sphinx/source/dicom-guide.rst	Wed Sep 19 21:29:17 2018 +0200
+++ b/Sphinx/source/dicom-guide.rst	Thu Sep 20 15:00:49 2018 +0200
@@ -240,11 +240,9 @@
 level (and not from the patient level) as soon as you deal with an
 application that handles patients from different hospitals.
 
-*Note:* The current version of the :ref:`Orthanc Explorer
-<orthanc-explorer>` interface (1.4.1 at the time of writing) is
-designed for single-hospital scenarios, and thus does not provide
-study-level access. But the core engine of Orthanc does support
-study-level access through its :ref:`REST API <rest>`.
+*Note:* Note that since Orthanc 1.4.0, the :ref:`Orthanc Explorer
+<orthanc-explorer>` interface provides a new tab entitled "Studies"
+for study-level access.
 
 Finally, the patient module is not always fully meaningful. This is
 for instance the case in emergency imaging, where the `radiology

--- a/Sphinx/source/faq/log.rst	Wed Sep 19 21:29:17 2018 +0200
+++ b/Sphinx/source/faq/log.rst	Thu Sep 20 15:00:49 2018 +0200
@@ -49,7 +49,7 @@
 2. Stop the Orthanc service. The actual process depends on your
    version of Windows.
 
-3. Copy the just-downloaded ``Orthanc-1.4.1-Release.exe`` together
+3. Copy the just-downloaded ``Orthanc-1.4.2-Release.exe`` together
    with your configuration file (that is by default located in
    ``C:\Orthanc\Configuration.json``) into the same folder
    (e.g. ``C:\Temp``).
@@ -57,7 +57,7 @@
 4. Type in a command-line shell, to generate the ``Orthanc.log`` file::
 
    $ cd C:\Temp
-   $ Orthanc-1.4.1-Release.exe --verbose Configuration.json > Orthanc.log 2<&1
+   $ Orthanc-1.4.2-Release.exe --verbose Configuration.json > Orthanc.log 2<&1
 
 5. Restart the Orthanc service.
 

--- a/Sphinx/source/users/configuration.rst	Wed Sep 19 21:29:17 2018 +0200
+++ b/Sphinx/source/users/configuration.rst	Thu Sep 20 15:00:49 2018 +0200
@@ -6,7 +6,7 @@
 
 Configuring Orthanc simply consists in copying and adapting the
 `default configuration file
-<https://bitbucket.org/sjodogne/orthanc/raw/Orthanc-1.4.1/Resources/Configuration.json>`_. This
+<https://bitbucket.org/sjodogne/orthanc/raw/Orthanc-1.4.2/Resources/Configuration.json>`_. This
 file is in the `JSON <https://en.wikipedia.org/wiki/JSON>`_ file
 format. You can generate a sample configuration file with the
 following call::

--- a/Sphinx/source/users/docker.rst	Wed Sep 19 21:29:17 2018 +0200
+++ b/Sphinx/source/users/docker.rst	Thu Sep 20 15:00:49 2018 +0200
@@ -45,7 +45,7 @@
 If more stability is required, you can select the official release of
 Orthanc to be run::
 
-  $ sudo docker run -p 4242:4242 -p 8042:8042 --rm jodogne/orthanc:1.4.1
+  $ sudo docker run -p 4242:4242 -p 8042:8042 --rm jodogne/orthanc:1.4.2
 
 Passing additional command-line options (e.g. to make Orthanc verbose)
 can be done as follows (note the ``/etc/orthanc`` option that is
@@ -94,7 +94,7 @@
 container to some path in the filesystem of your Linux host, e.g.::
 
   $ mkdir /tmp/orthanc-db
-  $ sudo docker run -p 4242:4242 -p 8042:8042 --rm -v /tmp/orthanc-db/:/var/lib/orthanc/db/ jodogne/orthanc:1.4.1 
+  $ sudo docker run -p 4242:4242 -p 8042:8042 --rm -v /tmp/orthanc-db/:/var/lib/orthanc/db/ jodogne/orthanc:1.4.2 
 
 
 Whole-slide imaging support