# HG changeset patch
# User Sebastien Jodogne <s.jodogne@gmail.com>
# Date 1630138887 -7200
# Node ID 94f5fc38b927bf3e1adbf45c1e8b8de222b46939
# Parent  77496fd36a962a8904203d321279c3b04406ebf2
clarifications

diff -r 77496fd36a96 -r 94f5fc38b927 Sphinx/source/faq/dicom-tls.rst
--- a/Sphinx/source/faq/dicom-tls.rst	Fri Aug 27 14:06:27 2021 +0200
+++ b/Sphinx/source/faq/dicom-tls.rst	Sat Aug 28 10:21:27 2021 +0200
@@ -86,10 +86,12 @@
 <https://forum.dcmtk.org/viewtopic.php?t=5073>`__, which produces the
 errors ``DUL secure transport layer: no suitable signature algorithm``
 (in the DICOM SCP) and ``DUL secure transport layer: sslv3 alert
-handshake failure`` (in the DICOM SCU). Make sure to use either DCMTK
-3.6.2 or DCMTK 3.6.6. In particular, Debian Buster (10) will use DCMTK
-3.6.4 and should be avoided in non-static builds of Orthanc, or if
-using the DCMTK command-line tools.
+handshake failure`` (in the DICOM SCU). This problem is not specific
+to Orthanc, as it also occurs between two command-line tools of the
+DCMTK 3.6.4 suite. Make sure to use either DCMTK 3.6.2 or DCMTK
+3.6.6. In particular, Debian Buster (10) uses DCMTK 3.6.4 and should
+be avoided in non-static builds of Orthanc, or if using the DCMTK
+command-line tools.
 
 
 
diff -r 77496fd36a96 -r 94f5fc38b927 Sphinx/source/users/docker.rst
--- a/Sphinx/source/users/docker.rst	Fri Aug 27 14:06:27 2021 +0200
+++ b/Sphinx/source/users/docker.rst	Sat Aug 28 10:21:27 2021 +0200
@@ -30,21 +30,23 @@
   images that are described on this page are always kept in sync with
   the latest releases of the Orthanc project, with a basic
   configuration system that is inherited from the Debian packages
-  (i.e. manual edition of the configuration files).
+  (i.e. manual edition of the configuration files). These images are
+  most useful to **software developers and researchers**.
 
 * Our commercial partner `Osimis <https://www.osimis.io>`__ also
   `publishes separated Docker images
-  <https://hub.docker.com/r/osimis/orthanc>`__.
-  These ``osimis/orthanc`` images are used by the technical team of
-  Osimis in order to provide professional support to their customers,
-  with a configuration system that can be tuned through environment
-  variables (which is very handy if using ``docker-compose``). These
-  images are not necessarily always in sync with the Orthanc project,
-  but they also include the :ref:`plugins edited by Osimis
-  <plugins-osimis>`, notably the Osimis Web viewer (that is much more
-  advanced than the Orthanc Web viewer) and the advanced authorization
-  plugin. A :ref:`specific page <docker-osimis>` is available to describe 
-  how these images should be used.
+  <https://hub.docker.com/r/osimis/orthanc>`__.  These
+  ``osimis/orthanc`` images are used by the technical team of Osimis
+  in order to provide professional support to their customers, with a
+  configuration system that can be tuned through **environment
+  variables** (which is very handy if using ``docker-compose`` or
+  Kubernetes). These images are not necessarily always in sync with
+  the Orthanc project, but they also include the :ref:`plugins edited
+  by Osimis <plugins-osimis>`, notably the Osimis Web viewer (that is
+  much more advanced than the Orthanc Web viewer) and the advanced
+  authorization plugin. A :ref:`specific page <docker-osimis>` is
+  available to describe how these images should be used. These images
+  are targeted at **ops teams**.
 
 **Note for CentOS users:** The Docker environment might be difficult to
 configure on your platform. Hints are available on the `Orthanc Users