--- a/Sphinx/source/faq/compiling.rst	Tue Jul 02 12:01:55 2019 +0200
+++ b/Sphinx/source/faq/compiling.rst	Tue Aug 06 09:51:59 2019 +0200
@@ -11,6 +11,21 @@
   inside the source package.
 * Orthanc <= 0.7.0: See the :ref:`compiling-old`.
 
+**Note for packagers:** As explained :ref:`below on this page
+<compiling-infrastructure>`, the CMake scripts of Orthanc and its
+associated plugins may have to download the source code of third-party
+dependencies. This is an undesirable feature if packaging Orthanc for
+some GNU/Linux distribution, as network connections are forbidden in
+such situations to enable reproducible builds. To prevent the CMake
+scripts to download from Internet, package maintainers can manually
+download third-party dependencies by themselves (by checking what is
+downloaded by CMake during a fresh build), then put them in a
+subfolder named ``ThirdPartyDownloads/`` in the same folder as the
+``CMakeLists.txt`` file of the project. If the third-party packages
+are already in that subfolder, the CMake script will not try and
+download them from Internet.
+
+
 Under Microsoft Windows
 -----------------------
 
@@ -39,6 +54,8 @@
 
 
 
+.. _compiling-infrastructure:
+
 Please explain the build infrastructure
 ---------------------------------------
 

--- a/Sphinx/source/faq/debian-daemon.rst	Tue Jul 02 12:01:55 2019 +0200
+++ b/Sphinx/source/faq/debian-daemon.rst	Tue Aug 06 09:51:59 2019 +0200
@@ -7,7 +7,7 @@
 you can:
 
 1. Download this `service script
-   <http://anonscm.debian.org/cgit/debian-med/orthanc.git/tree/debian/orthanc.init>`_
+   <https://salsa.debian.org/med-team/orthanc/raw/master/debian/orthanc.init>`_
    (this file is part of the `official Debian package
    <https://tracker.debian.org/pkg/orthanc>`_ of Orthanc),
 2. Adapt some of its variables to reflect the configuration of your

--- a/Sphinx/source/plugins/dicomweb.rst	Tue Jul 02 12:01:55 2019 +0200
+++ b/Sphinx/source/plugins/dicomweb.rst	Tue Aug 06 09:51:59 2019 +0200
@@ -459,7 +459,7 @@
 argument as for QIDO-RS and WADO-RS. This might be useful e.g. for
 cookie-based session management.
 
-Internally, this call results in creating an :ref:`Orthanc job <job>`
+Internally, this call results in creating an :ref:`Orthanc job <jobs>`
 that is executed synchronously (the REST call only returns once the 
 STOW-RS request is finished). You can run the job in asynchronous 
 mode as follows::