diff --git a/site/sigmaguides/src/developers_api_code_samples/assets/apics74.png b/site/sigmaguides/src/developers_api_code_samples/assets/apics74.png
new file mode 100644
index 00000000..f7f44529
Binary files /dev/null and b/site/sigmaguides/src/developers_api_code_samples/assets/apics74.png differ
diff --git a/site/sigmaguides/src/developers_api_code_samples/developers_api_code_samples.md b/site/sigmaguides/src/developers_api_code_samples/developers_api_code_samples.md
index 6e873aa7..384711da 100644
--- a/site/sigmaguides/src/developers_api_code_samples/developers_api_code_samples.md
+++ b/site/sigmaguides/src/developers_api_code_samples/developers_api_code_samples.md
@@ -200,7 +200,6 @@ It also exports a Javascript function to request a bearer token (token) each tim
-`
In the project root directory, open the file `get-access-token.js` and review it's contents. Each section is commented so it can be understood.
Start the VSCode debugger against this code by pressing `F5` on your keyboard.
@@ -1166,7 +1165,7 @@ Duration: 20
A common use case is to programmatically initiate an existing materialization job in Sigma, via API.
-This section demonstrates the code that was provided on the `API Code Samples` > `Workbook: Workbook: Initiate Materialization Job` page, [located here.](https://help.sigmacomputing.com/recipes/workbook-initiate-materialization-job)
+This section demonstrates the code that was provided on the `API Code Samples` > `Workbook: Initiate Materialization Job` page, [located here.](https://help.sigmacomputing.com/recipes/workbook-initiate-materialization-job)