docs: fixed typo

Author: will-break-it

docs/workshop/day-3-recap.md

@@ -35,7 +35,7 @@ Each of the following approaches describes a solution where an Input Block (IB)
 
 #### IB-to-RB Reference Approach
 
-The simplified diagram below shows respective lower and upper bounds for selecting an RB as ledger state reference for IB validation - each showing the extreme ends of trading off latency for security. Realistically, both are not good choices and some RB such as tip-6 might be more suitable. Note, that even the tip-3 example would introduce on average a delay of 3×20s = 90s before a user could reference outputs from a previously submitted transaction.
+The simplified diagram below shows respective lower and upper bounds for selecting an RB as ledger state reference for IB validation - each showing the extreme ends of trading off latency for security. Realistically, both are not good choices and some RB such as tip-3 might be more suitable. Note, that even the tip-3 example would introduce on average a delay of 3×20s = 60s before a user could reference outputs from a previously submitted transaction.
 
 ![RB Reference Approach](rb-reference.svg)
 

docs/workshop/eb-dag-detailed.d2

@@ -20,11 +20,6 @@ chain: {
     label: "Genesis"
   }
 
-  RBs: {
-    class: rb_stacked
-    label: "RBs"
-  }
-
   RB1: {
     class: rb
     label: "RB 1"
@@ -134,10 +129,7 @@ IB9: {
 
 # RB references
 
-chain.RBs -> chain.Genesis: {
-  class: to_rb_arrow
-}
-chain.RB1 -> chain.RBs: {
+chain.RB1 -> chain.Genesis: {
   class: to_rb_arrow
 }
 chain.RB2 -> chain.RB1: {