diff --git a/public-site/docs/src/guides/jobs/configure-jobs.md b/public-site/docs/src/guides/jobs/configure-jobs.md
index de9a2312..d643ea08 100644
--- a/public-site/docs/src/guides/jobs/configure-jobs.md
+++ b/public-site/docs/src/guides/jobs/configure-jobs.md
@@ -81,7 +81,7 @@ The compute job in the example above has `payload.path` set to `/compute/args`.
 
 ### resources
 
-The resource requirement for a job can be sent in the request body to the job scheduler as a JSON document with an element named `resources`.
+The resource requirement for a job can be sent in the request body to the job manager as a JSON document with an element named `resources`.
 The content of the resources will be used to set the resource definition for the job [`radixconfig.yaml`](../../references/reference-radix-config/#resources-common).
 The data type of the `resources` is of type `ResourceRequirements` an requires this specific format.
 
@@ -89,7 +89,7 @@ The etl job in the example above has `resource` configured.
 
 ### node
 
-The node requirerement for a job can be sent in the request body to the job scheduler as a JSON document with an element named `node`.
+The node requirerement for a job can be sent in the request body to the job manager as a JSON document with an element named `node`.
 The content of the node will be used to set the node definition for the job [`radixconfig.yaml`](../../references/reference-radix-config/#node).
 The data type of the `node` is of type `RadixNode` an requires this specific format.
 
@@ -97,12 +97,12 @@ The etl job in the example above has `node` configured.
 
 ### timeLimitSeconds
 
-The maximum running time for a job can be sent in the request body to the job scheduler as a JSON document with an element named `timeLimitSeconds`.
+The maximum running time for a job can be sent in the request body to the job manager as a JSON document with an element named `timeLimitSeconds`.
 
-The etl job in the example above has `timeLimitSeconds` configured in its [`radixconfig.yaml`](../../references/reference-radix-config/#timelimitseconds). If a new job is sent to the job scheduler without an element `timeLimitSeconds`, it will default to the value specified in radixconfig.yaml. If no value is specified in radixconfig.yaml, it will default to 43200 (12 hours).
+The etl job in the example above has `timeLimitSeconds` configured in its [`radixconfig.yaml`](../../references/reference-radix-config/#timelimitseconds). If a new job is sent to the job manager without an element `timeLimitSeconds`, it will default to the value specified in radixconfig.yaml. If no value is specified in radixconfig.yaml, it will default to 43200 (12 hours).
 
 ### backoffLimit
 
-The maximum number of restarts if the job fails can be sent in the request body to the job scheduler as a JSON document with an element named `backoffLimit`.
+The maximum number of restarts if the job fails can be sent in the request body to the job manager as a JSON document with an element named `backoffLimit`.
 
-The etl job in the example above has `backoffLimit` configured in its [`radixconfig.yaml`](../../references/reference-radix-config/#backofflimit). If a new job is sent to the job scheduler without an element `backoffLimit`, it will default to the value specified in radixconfig.yaml.
+The etl job in the example above has `backoffLimit` configured in its [`radixconfig.yaml`](../../references/reference-radix-config/#backofflimit). If a new job is sent to the job manager without an element `backoffLimit`, it will default to the value specified in radixconfig.yaml.
diff --git a/public-site/docs/src/guides/jobs/job-scheduler-diagram.png b/public-site/docs/src/guides/jobs/job-scheduler-diagram.png
index 7690eccc..dd7b7afb 100644
Binary files a/public-site/docs/src/guides/jobs/job-scheduler-diagram.png and b/public-site/docs/src/guides/jobs/job-scheduler-diagram.png differ
diff --git a/public-site/docs/src/guides/jobs/jobs-in-web-console.md b/public-site/docs/src/guides/jobs/jobs-in-web-console.md
index d51a7559..4bdcaf66 100644
--- a/public-site/docs/src/guides/jobs/jobs-in-web-console.md
+++ b/public-site/docs/src/guides/jobs/jobs-in-web-console.md
@@ -6,7 +6,7 @@ next: openapi-swagger
 
 ## Managing Jobs in Web Console
 
-Batches and jobs can be found in the Web console under the "Batches" and "Jobs" tabs. Job scheduler manager pod status and its log can be found in the "Job manager" section
+Batches and jobs can be found in the Web console under the "Batches" and "Jobs" tabs. Job manager pod status and its log can be found in the "Job manager" section
 ![Batch job status](./batch-job-manager-status.png)
 * It shows batch and job states. When all jobs in a batch are completed, the batch is completed. If any job fails, the batch is failed. 
   ![Batch and job statuses](./batch-and-job-statuses.png)