From 564e93eea1cfa7f8824de4a398b7fa8f40d211ef Mon Sep 17 00:00:00 2001
From: sandinak <1916398+sandinak@users.noreply.github.com>
Date: Sat, 7 Oct 2023 12:28:13 -0400
Subject: [PATCH] Update ShowfileDesign.md

---
 docs/ShowfileDesign.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/docs/ShowfileDesign.md b/docs/ShowfileDesign.md
index 929a5b3..36af86b 100644
--- a/docs/ShowfileDesign.md
+++ b/docs/ShowfileDesign.md
@@ -9,7 +9,7 @@ We use "folders" in the system to organize the layout of the data, and the tool
 We use this as the basic grouping of elements on the stage.  Typically this is fixutres of same location or type or combinations; which are used together during scenes to light the show.  In QLC+ are base set of groups created automatically when generating RGBMatrix features, however any seriues of fixtures anywhere on the stage can be grouped as desired.  
 
 <img src="./FixtureDefinitions.png" alt="Fixture Definitions" width="200">
-<img src="./FixtureDefinition.png" alt="Fixture Definitions" width="200">
+<img src="./FixtureDefinition.png" alt="Fixture Definition" width="200">
 
 If you're gonna be using these fixture sets in a chase or RGB Matrix, remember to lay them out correctly relative to their position on the stage.
 
@@ -26,7 +26,7 @@ To create these scenes, we define some basic settings in the tool, load the exis
 
 Sets of capablities for each fixture group are organized in to scenes that can then be used in collections to assemble the view
 
-<img src="./Colors.png" alt="Collection" width="200">
+<img src="./Colors.png" alt="Colors" width="200">
 
 The path is preserved in the name to avoid collisions and allow easy reference in when viewing an entire collection.
 
@@ -42,19 +42,19 @@ In this example it's the "preset" for the show so we have all the lights on and
 
 We organize collections by their use-case and timing in the show.   I use a cue naming format that allows easy expansion/extenssion {song}-{part}-{cue}; and song 0 is before-curtain.
 
-<img src="./Collections.png" alt="Collection" width="200">
+<img src="./Collections.png" alt="Collections" width="200">
 
 
 ## Chase
 
 The Show is then setup to be run via cue'ing using a "Chase".  Each cue is added with timings so that it can then be used as needed.  To do this a hold time of  &infin; is generally used so that the show can be cue'd via the virtual Console Cue List. Fade in/out timings can be set here as well .. and/or using a defined holdtime and duration can "auto-cue" where it makes sense.
 
-<img src="./Chase.png" alt="Collection" width="200">
+<img src="./Chase.png" alt="Chase" width="200">
 
 
 ## Cuelist
 
 Once you've assembled the parts, A Cuelist is used in the Virtual Console to allow the show to be cued.  Once added to the Virutal console, in the configuration we define a "Next Cue" button ( we use M ), and a "Previous Cue" button to allow the operator to move the show through time. 
 
-<img src="./Cuelist.png" alt="Collection" width="200">
+<img src="./CueList.png" alt="Cuelist" width="200">