Update Blog “open-sourcing-workshops-on-demand-part-5-create-a-workshop”

pattdepanick · pattdepanick · commit 475edeb1a145 · 2024-10-21T14:34:36.000Z
diff --git a/content/blog/open-sourcing-workshops-on-demand-part-5-create-a-workshop.md b/content/blog/open-sourcing-workshops-on-demand-part-5-create-a-workshop.md
@@ -96,11 +96,11 @@ A﻿ new entry will need the following:
 * **D﻿escription:** Same description as the one available in the workshop's table entry
 * **P﻿resenter:** Name of the presenter
 * **Role:** Role of the presenter (the workshop developer in fact: Solution Architect, Fullstack Developer, etc...)
-* **V﻿ideoLink:** Youtube link of the recorded video to be used as a replay
-* **W﻿orkshopId:** Id of the workshop linked to the video
+* **V﻿ideoLink:** YouTube link of the recorded video to be used as a replay
+* **W﻿orkshopId:** ID of the workshop linked to the video
 * **A﻿ctive:** Tag to set to enable visibility of the replay in registration portal
 
-One could create these entries manually or leverage a simple wod.yml file containing them and that can be later parsed in order to feed the database with the relevant info, quite handy,no ?
+One could create these entries manually or leverage a simple wod.yml file containing them and that can be later parsed in order to feed the database with the relevant info. Quite handy, no?
 
 Here is an exampe of such a file:
 

-Original file line number
+Diff line change
 * **Description:** Same description as the one available in the workshop's table entry
 * **Presenter:** Name of the presenter
 * **Role:** Role of the presenter (the workshop developer in fact: Solution Architect, Fullstack Developer, etc...)
 -* **VideoLink:** Youtube link of the recorded video to be used as a replay
 -* **WorkshopId:** Id of the workshop linked to the video
 +* **VideoLink:** YouTube link of the recorded video to be used as a replay
 +* **WorkshopId:** ID of the workshop linked to the video
 * **Active:** Tag to set to enable visibility of the replay in registration portal
 -One could create these entries manually or leverage a simple wod.yml file containing them and that can be later parsed in order to feed the database with the relevant info, quite handy,no ?
 +One could create these entries manually or leverage a simple wod.yml file containing them and that can be later parsed in order to feed the database with the relevant info. Quite handy, no?
 Here is an exampe of such a file: