added source code link

docs/agave/guides/jobs/aloe-job-architecture.rst

@@ -107,7 +107,7 @@ This message routing algorithm allows requests to be segregated by workload char
 Asynchronous Communication
 """"""""""""""""""""""""""
 
-The first thing a job worker thread does when it reads in a job submission message is to spawn a *job-specific command thread* to handle asynchronous communication to that job.  The command thread creates a temporary *job-specific command topic* and waits for asynchronous messages to be sent to the job.  The most common message sent to a job is a cancellation message, usually originating from a REST call sent by the user that originally submitted the job.  The command thread delivers messages through shared memory to its parent worker thread, which is then takes action on the job it's processing.  To cover cases when jobs are in recovery and not assigned a worker, asynchronous messages destine for jobs are also sent to the *recovery queue* so they can be acted upon by `Tenant Recovery Readers`_. 
+The first thing a job worker thread does when it reads in a job submission message is to spawn a *job-specific command thread* to handle asynchronous communication to that job.  The command thread creates a temporary *job-specific command topic* and waits for asynchronous messages to be sent to the job.  The most common message sent to a job is a cancellation message, usually originating from a REST call sent by the user that originally submitted the job.  The command thread delivers messages through shared memory to its parent worker thread, which then takes action on the job it's processing.  To cover cases when jobs are in recovery and not assigned a worker, asynchronous messages destine for jobs are also sent to the *recovery queue* so they can be acted upon by `Tenant Recovery Readers`_. 
 
 In addition to the command topic, the Jobs service designates an *events topic* for each tenant.  The idea is that different system components can write well-defined events to the topic and interested parties can subscribe to the topic to receive some subset of those events.  Eventually, a REST API will be developed to allow external subscriptions to the events topic.  *The events topic is not used in the initial Jobs service release.*
 

docs/agave/guides/jobs/aloe-job-changes.rst

@@ -1,7 +1,7 @@
 Jobs Service Changes
 ====================
 
-This page discusses what has changed in the Jobs service between Agave 2.2.23 and Aloe 3.0.
+This page discusses what has changed in the Jobs service between Agave 2.2.23 and Aloe 3.0.  The Aloe source code is `here <https://bitbucket.org/tacc-cic/aloe/src/master/>`_.
 
 .. contents:: Table of Contents