# HG changeset patch
# User Sebastien Jodogne <s.jodogne@gmail.com>
# Date 1594117960 -7200
# Node ID a983d7c639dd0a96877f564e0948abcbb219f17b
# Parent  235a5541e06ed677638fcc7db03c9a856ff4a3ea
fix links

diff -r 235a5541e06e -r a983d7c639dd Sphinx/source/users/support.rst
--- a/Sphinx/source/users/support.rst	Fri Jul 03 09:39:25 2020 +0200
+++ b/Sphinx/source/users/support.rst	Tue Jul 07 12:32:40 2020 +0200
@@ -11,34 +11,36 @@
 When you face a problem, you should first check out the following
 resources:
 
-1. Make sure to :ref:`check all the content of the Orthanc Book
+1. Make sure that you use the `latest version of Orthanc
+   <http://www.orthanc-server.com/download.php>`__.
+2. Make sure to :ref:`check all the content of the Orthanc Book
    <orthanc-book>`, and notably to :ref:`understand the basics of
    DICOM <dicom-guide>`.
-2. Carefully read your :ref:`log files in verbose mode <log>`.
-3. In the case of DICOM networking problems, carefully read the log
+3. Carefully read your :ref:`log files in verbose mode <log>`.
+4. In the case of DICOM networking problems, carefully read the log
    files from your remote modality. If you are :ref:`using Orthanc
    against a proprietary system <proprietary>`, contact the support
    team from the vendor of this system: You pay them to solve your
    setup issues.
-4. Follow the :ref:`general troubleshooting guide <troubleshooting>`.
-5. If the problem is related to the DICOM network protocol, follow
+5. Follow the :ref:`general troubleshooting guide <troubleshooting>`.
+6. If the problem is related to the DICOM network protocol, follow
    the :ref:`DICOM troubleshooting guide <dicom>`.
-6. Have a look at **all** the :ref:`frequently asked questions (FAQs)
+7. Have a look at **all** the :ref:`frequently asked questions (FAQs)
    <faq>` that are already available in the Orthanc Book.
-7. Make a search for similar problem previously discussed in the
+8. Make a search for similar problem previously discussed in the
    `Orthanc Users discussion forum
    <https://groups.google.com/forum/#!forum/orthanc-users>`__.
-8. Check out the ``Pending changes in the mainline`` section of the
+9. Check out the ``Pending changes in the mainline`` section of the
    `NEWS file
    <https://hg.orthanc-server.com/orthanc/file/default/NEWS>`__, as
    your issue might already be solved in the mainline of Orthanc (i.e.
    in the cutting-edge version of Orthanc since the last stable
    official release).
-9. Carefully read the `TODO file
-   <https://hg.orthanc-server.com/orthanc/file/default/TODO>`__ that
-   contains our roadmap, as you might be requesting a feature that is
-   currently pending in our backlog (i.e. not implemented yet).
-10. Look for similar issue in the `official bug tracker
+10. Carefully read the `TODO file
+    <https://hg.orthanc-server.com/orthanc/file/default/TODO>`__ that
+    contains our roadmap, as you might be requesting a feature that is
+    currently pending in our backlog (i.e. not implemented yet).
+11. Look for similar issue in the `official bug tracker
     <https://bugs.orthanc-server.com/query.cgi>`__ (make sure to
     select ``All`` in the ``Status`` field, as your issue might
     already have been solved).
@@ -46,8 +48,8 @@
 
 Importantly, for all the features that are pending in the ``TODO``
 file, if you are a company, please consider `buying professional
-services <https://www.orthanc-server.com/orthanc-pro.php>`__ in order
-to get the feature implemented faster.
+services <https://www.osimis.io/en/services.html>`__ in order to get
+the feature implemented faster.
    
    
 .. _support-mwe: