[Sphinx Documentation] Edit text to Jenkins in Docker

docs/finn/_build/html/_sources/getting_started.rst.txt

@@ -36,7 +36,7 @@ Running the Jupyter notebooks
 
   sh run-docker.sh notebook
 
-This will launch the Jupyter notebook server inside a Docker container, and print a link on the terminal that you can open in your browser to run the FINN notebooks or create new ones. 
+This will launch the `Jupyter notebook <https://jupyter.org/>`_ server inside a Docker container, and print a link on the terminal that you can open in your browser to run the FINN notebooks or create new ones. 
 .. note:: The link will look something like this (the token you get will be different):
 http://127.0.0.1:8888/?token=f5c6bd32ae93ec103a88152214baedff4ce1850d81065bfc
 
@@ -52,10 +52,8 @@ FINN comes with a set of tests which can be launched using the command above. No
 
 Running the test suite using Jenkins
 ************************************
-`Jenkins <https://jenkins.io/>`_ is an open source automation server that can be used as support when building, deploying and automating a project.
-
 ::
 
   sh run-docker.sh jenkins
 
-This will launch Jenkins inside a Docker container and print an initial password for the user to use together with the username "admin" to open Jenkins in the webbrowser. The script forwards port 8080 for Jenkins and also configures a smee client to access port 8080. `Smee <https://smee.io/>`_ is a webhook payload delivery service and the FINN GitHub repository has a webhook set up to trigger the smee client (that is set in the run_docker script) when a push event is happening. Through Jenkins the user can set up a test for FINN, which is started at every push event.
+This will launch `Jenkins <https://jenkins.io/>`_ inside a Docker container and print an initial password for the user to use together with the username "admin" to open Jenkins in the webbrowser. The script forwards port 8080 for Jenkins and also configures a smee client to access port 8080. `Smee <https://smee.io/>`_ is a webhook payload delivery service and the FINN GitHub repository has a webhook set up to trigger the smee client (that is set in the run_docker script) when a push event is happening. Through Jenkins the user can set up a test for FINN, which is started at every push event.

docs/finn/_build/html/getting_started.html

@@ -205,7 +205,7 @@
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">sh</span> <span class="n">run</span><span class="o">-</span><span class="n">docker</span><span class="o">.</span><span class="n">sh</span> <span class="n">notebook</span>
 </pre></div>
 </div>
-<p>This will launch the Jupyter notebook server inside a Docker container, and print a link on the terminal that you can open in your browser to run the FINN notebooks or create new ones.
+<p>This will launch the <a class="reference external" href="https://jupyter.org/">Jupyter notebook</a> server inside a Docker container, and print a link on the terminal that you can open in your browser to run the FINN notebooks or create new ones.
 .. note:: The link will look something like this (the token you get will be different):
 <a class="reference external" href="http://127.0.0.1:8888/?token=f5c6bd32ae93ec103a88152214baedff4ce1850d81065bfc">http://127.0.0.1:8888/?token=f5c6bd32ae93ec103a88152214baedff4ce1850d81065bfc</a></p>
 <p>The run-docker.sh script forwards ports 8888 for Jupyter and 8081 for Netron, and launches the notebook server with appropriate arguments.</p>
@@ -219,11 +219,10 @@
 </div>
 <div class="section" id="running-the-test-suite-using-jenkins">
 <h3>Running the test suite using Jenkins<a class="headerlink" href="#running-the-test-suite-using-jenkins" title="Permalink to this headline">¶</a></h3>
-<p><a class="reference external" href="https://jenkins.io/">Jenkins</a> is an open source automation server that can be used as support when building, deploying and automating a project.</p>
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">sh</span> <span class="n">run</span><span class="o">-</span><span class="n">docker</span><span class="o">.</span><span class="n">sh</span> <span class="n">jenkins</span>
 </pre></div>
 </div>
-<p>This will launch Jenkins inside a Docker container and print an initial password for the user to use together with the username “admin” to open Jenkins in the webbrowser. The script forwards port 8080 for Jenkins and also configures a smee client to access port 8080. <a class="reference external" href="https://smee.io/">Smee</a> is a webhook payload delivery service and the FINN GitHub repository has a webhook set up to trigger the smee client (that is set in the run_docker script) when a push event is happening. Through Jenkins the user can set up a test for FINN, which is started at every push event.</p>
+<p>This will launch <a class="reference external" href="https://jenkins.io/">Jenkins</a> inside a Docker container and print an initial password for the user to use together with the username “admin” to open Jenkins in the webbrowser. The script forwards port 8080 for Jenkins and also configures a smee client to access port 8080. <a class="reference external" href="https://smee.io/">Smee</a> is a webhook payload delivery service and the FINN GitHub repository has a webhook set up to trigger the smee client (that is set in the run_docker script) when a push event is happening. Through Jenkins the user can set up a test for FINN, which is started at every push event.</p>
 </div>
 </div>
 </div>

docs/finn/getting_started.rst

@@ -36,7 +36,7 @@ Running the Jupyter notebooks
 
   sh run-docker.sh notebook
 
-This will launch the Jupyter notebook server inside a Docker container, and print a link on the terminal that you can open in your browser to run the FINN notebooks or create new ones. 
+This will launch the `Jupyter notebook <https://jupyter.org/>`_ server inside a Docker container, and print a link on the terminal that you can open in your browser to run the FINN notebooks or create new ones. 
 .. note:: The link will look something like this (the token you get will be different):
 http://127.0.0.1:8888/?token=f5c6bd32ae93ec103a88152214baedff4ce1850d81065bfc
 
@@ -52,10 +52,8 @@ FINN comes with a set of tests which can be launched using the command above. No
 
 Running the test suite using Jenkins
 ************************************
-`Jenkins <https://jenkins.io/>`_ is an open source automation server that can be used as support when building, deploying and automating a project.
-
 ::
 
   sh run-docker.sh jenkins
 
-This will launch Jenkins inside a Docker container and print an initial password for the user to use together with the username "admin" to open Jenkins in the webbrowser. The script forwards port 8080 for Jenkins and also configures a smee client to access port 8080. `Smee <https://smee.io/>`_ is a webhook payload delivery service and the FINN GitHub repository has a webhook set up to trigger the smee client (that is set in the run_docker script) when a push event is happening. Through Jenkins the user can set up a test for FINN, which is started at every push event.
+This will launch `Jenkins <https://jenkins.io/>`_ inside a Docker container and print an initial password for the user to use together with the username "admin" to open Jenkins in the webbrowser. The script forwards port 8080 for Jenkins and also configures a smee client to access port 8080. `Smee <https://smee.io/>`_ is a webhook payload delivery service and the FINN GitHub repository has a webhook set up to trigger the smee client (that is set in the run_docker script) when a push event is happening. Through Jenkins the user can set up a test for FINN, which is started at every push event.