fix alt text in ep2

fixing quotes to hopefully fix some errors

Author: jlcohoon

episodes/preparing.md

@@ -28,7 +28,7 @@ exercises: 5
 A task should be something that users actually want to do that can be accomplished in a short period of time. When defining tasks for your rapid usability test, keep in mind that you usually don’t want to test users’ reading comprehension—you want to test the usability of the interface. Thus, avoid using terms visible in the interface in your task description. Nielsen Norman [has additional advice](https://www.nngroup.com/articles/better-usability-tasks/) on how to craft good task prompts. 
 
 ### Example: Being goal oriented and avoiding language from the user interface
-![](fig/ep2ex_avoidLang.png){alt="Screenshot of an example Slack workspace, showing the #general channel open in desktop application window. The left sidebar lists Workspace, Home, DMs, Activity, Channels, and Apps. The main panel displays the top of the #general channel with a message from a user “hcohoon” that says “Hey everyone! What time should we meet tomorrow?” Below the message, near the timestamp, is a visible button labeled “Reply in thread” circled in red to emphasize it. At the top of the image, instructional text overlays the Slack workspace screenshot: a red “X” next to the phrase “Task: ‘Reply to a message using a thread’” and a green check mark next to the phrase “Task: ‘Show how you would participate in multiple, separate conversations in one channel.’” The figure contrasts giving the user a task that repeats interface wording with one that focuses on a user goal, illustrating how task phrasing can shape what is being evaluated in a usability test."}
+![](fig/ep2ex_avoidLang.png){alt="Screenshot of an example Slack workspace, showing the #general channel open in desktop application window. The left sidebar lists Workspace, Home, DMs, Activity, Channels, and Apps. The main panel displays the top of the #general channel with a message from a user 'hcohoon' that says, 'Hey everyone! What time should we meet tomorrow?' Below the message, near the timestamp, is a visible button labeled 'Reply in thread' circled in red to emphasize it. At the top of the image, instructional text overlays the Slack workspace screenshot: a red 'X' next to the phrase 'Task: Reply to a message using a thread’ and a green check mark next to the phrase 'Task: Show how you would participate in multiple, separate conversations in one channel.’ The figure contrasts giving the user a task that repeats interface wording with one that focuses on a user goal, illustrating how task phrasing can shape what is being evaluated in a usability test."}
 
 After you’ve selected tasks for your usability study, time yourself completing study tasks to establish a baseline. To prevent fatigue, you want to aim for your session to be under 30 minutes. Allowing 10 minutes for non-task activities like instructions and interview questions means you should have no more than 20 minutes for task completion. Reduce the number or complexity of tasks you have planned if needed.
 
@@ -62,7 +62,7 @@ Because you are likely evaluating success or counting errors, you should define
 
 ### Example: Success and Errors can mean multiple things
 Given a single task (“Show how you would participate in multiple, separate conversations in one channel”), success can still be achieved in multiple ways:
-![](fig/ep2ex_multiMeaning.png){alt="Graphic showing that success on a single usability task can be achieved in more than one way. On the right side is a partial Slack conversation. A user named “Chung” shares a link to a blog post and asks for recommendations. Below the message appears a small label reading “1 reply,” indicating a threaded response. Beneath that, another user, “Sam,” has posted a reply beginning with “@Chung,” suggesting a response in the main channel. On the left side of the image, large text reads, “Success can be achieved in multiple ways,” with arrows pointing toward both the threaded reply indicator and the channel reply. The figure illustrates that when defining evaluation metrics, researchers must decide what counts as successful task completion, since participants may accomplish the goal through different interaction paths."}
+![](fig/ep2ex_multiMeaning.png){alt="Graphic showing that success on a single usability task can be achieved in more than one way. On the right side is a partial Slack conversation. A user named Chung shares a link to a blog post and asks for recommendations. Below the message appears a small label reading '1 reply,' indicating a threaded response. Beneath that, another user, Sam, has posted a reply beginning with '@Chung,' suggesting a response in the main channel. On the left side of the image, large text reads, 'Success can be achieved in multiple ways,' with arrows pointing toward both the threaded reply indicator and the channel reply. The figure illustrates that when defining evaluation metrics, researchers must decide what counts as successful task completion, since participants may accomplish the goal through different interaction paths."}
 
 ## Developing a script
 It is important that you give each of your participants the same experience when they join your study, so that results are comparable across participants. You want to avoid giving hints or causing confusion. You also want participants to feel comfortable talking with you. Following a script and prepping the test environment will make sure you succeed in these goals. The script should cover everything you’ll say to a participant so that someone else can stand in for you and still run the exact same study.