Update job-submission.rst

docs/agave/guides/jobs/job-submission.rst

@@ -102,7 +102,7 @@ As mentioned previously, jobs are submitted by making a HTTP POST request either
     In this tutorial we will use JSON for our examples, however, one could replace the JSON object with a HTML form mapping JSON attribute and values to HTML form attributes and values one for one and get the same results, with the exception of the ``notifications`` attribute which is not accepted using HTML form submission and would need to be added after submitting the job request by sending each of the notification objects with the returned job id to the :raw-html-m2r:`<a href="https://tacc-cloud.readthedocs.io/projects/agave/en/latest/agave/guides/notifications/introduction.html" title="Notification Management Tutorial">Notifications API</a>`.
     In addition to the standard fields for all jobs, the application you specify in the ``appId`` field will also have its own set of inputs and parameters specified during registration that are unique to that app. (For more information about app registration and descriptions, see the :raw-html-m2r:`<a href="
 https://tacc-cloud.readthedocs.io/projects/agave/en/latest/agave/guides/apps/introduction.html" title="Apps API">Apps section</a>`..
-    The following snippet shows a sample JSON job request that could be submitted to the Jobs service to run the ``pyplot-0.1.0`` app. :raw-html-m2r:`<!-- from the <a href="http://agaveapi.co/documentation/tutorials/app-management-tutorial/advanced-app-example/" title="Advanced App Example">Advanced App Example</a> tutorial. -->`
+    The following snippet shows a sample JSON job request that could be submitted to the Jobs service to run the ``pyplot-0.1.0`` app. from the :raw-html-m2r:`<a href="http://agaveapi.co/documentation/tutorials/app-management-tutorial/advanced-app-example/" title="Advanced App Example">Advanced App Example</a>` tutorial. 
 ..
 
 .. container:: foldable