diff --git a/data-automation-bda/workshops/01-document/03_combining_project_blueprints_with_multipage_documents.ipynb b/data-automation-bda/workshops/01-document/03_combining_project_blueprints_with_multipage_documents.ipynb
index 3ad1af0b1..4cd02eac8 100644
--- a/data-automation-bda/workshops/01-document/03_combining_project_blueprints_with_multipage_documents.ipynb
+++ b/data-automation-bda/workshops/01-document/03_combining_project_blueprints_with_multipage_documents.ipynb
@@ -581,7 +581,7 @@
    "metadata": {},
    "source": [
     "### View Job Metadata\n",
-    "Let's retrieve the job metadata. The Job metadata contains the S3 uri's for the standard output,custom output and the status of custom output. The custom output status could be either of `MATCH` or `NO_MATCH`. `MATCH` indicates BDA was able to find a matching blueprint for the specific segment from the list of blueprint we associated with the project. If BDA was unable to match the segment to a blueprint associated with the project then the `custom output status` is `NO_MATCH` and in this case BDA would only have a standard output extracted from that specific segment of the input file."
+    "Let's retrieve the job metadata. The Job metadata contains the S3 uri's for the standard output, custom output and the status of custom output. The custom output status could be either of `MATCH` or `NO_MATCH`. `MATCH` indicates BDA was able to find a matching blueprint for the specific segment from the list of blueprint we associated with the project. If BDA was unable to match the segment to a blueprint associated with the project then the `custom output status` is `NO_MATCH` and in this case BDA would only have a standard output extracted from that specific segment of the input file."
    ]
   },
   {