# HG changeset patch
# User Sebastien Jodogne <s.jodogne@gmail.com>
# Date 1550311219 -3600
# Node ID 66295dffbf3338089e85f8d3673a2f7b3cde32f6
# Parent  f6c812c4026f10a7d62fec1fdd2802aadf3c490a
fix

diff -r f6c812c4026f -r 66295dffbf33 Sphinx/source/users/rest.rst
--- a/Sphinx/source/users/rest.rst	Sat Feb 16 09:56:20 2019 +0000
+++ b/Sphinx/source/users/rest.rst	Sat Feb 16 11:00:19 2019 +0100
@@ -586,7 +586,7 @@
 
 You can perform a C-Move to retrieve all studies within the original
 query using a post command and identifying the Modality (named in this 
-example `"Orthanc"`), to be one to in the POST contents::
+example ``Orthanc``), to be one to in the POST contents::
 
   $ curl --request POST --url http://localhost:8042/queries/5af318ac-78fb-47ff-b0b0-0df18b0588e0/retrieve --data Orthanc
 
@@ -595,12 +595,17 @@
 
   $ curl --request POST --url http://localhost:8042/queries/5af318ac-78fb-47ff-b0b0-0df18b0588e0/answers/0/retrieve --data Orthanc
 
-If C-Moves take too long (for example, performing a C-Move of a big study)
-you may run the request in asynchronous fashion:
+If C-Moves take too long (for example, performing a C-Move of a big
+study), you may run the request in asynchronous fashion, which will
+create a job in Orthanc::
 
-  $ curl --request POST --url http://localhost:8042/queries/5af318ac-78fb-47ff-b0b0-0df18b0588e0/retrieve --data '{"TargetAet":"Orthanc","Synchronous":false}'
+  $ curl --request POST --url http://localhost:8042/queries/5af318ac-78fb-47ff-b0b0-0df18b0588e0/retrieve \
+    --data '{"TargetAet":"Orthanc","Synchronous":false}'
+
 
-The answer of this POST request is the job ID taking care of the C-Move
+.. highlight:: bash
+
+The answer of this POST request is the job ID taking care of the C-Move::
 
   {
       "ID" : "11541b16-e368-41cf-a8e9-3acf4061d238",