From aeaebd133f610820e715cea0eff950d705a26860 Mon Sep 17 00:00:00 2001 From: Madhu Nunna Date: Fri, 24 Apr 2026 18:23:29 -0700 Subject: [PATCH] fix: add missing space in 'output,custom' in BDA blueprints notebook Adds missing space after comma in the job metadata explanation in 03_combining_project_blueprints_with_multipage_documents.ipynb so readers parse 'standard output, custom output' rather than run-together words. The companion 'chan'/'can' typo was already fixed upstream; only the missing-space typo remained. Fixes #522 --- ..._combining_project_blueprints_with_multipage_documents.ipynb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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." ] }, {