Read the whole thing first.
The most common cooking failure is not a burned pan
It is getting halfway through a recipe and discovering that the onions should have been diced twenty minutes ago, the oven should already be preheated, or the ingredient list says "2 cups cooked rice" and you are looking at a bag of dry rice. The fix is almost embarrassingly simple: read the entire recipe before touching the stove.
A recipe is a plan, not a script
A good reader of recipes does three things before any burner goes on. First, they identify what needs to happen before heat: washing, chopping, measuring, draining, thawing, preheating. Second, they figure out the order of operations during cooking: what goes in when, what simmers while something else browns, when to check the temperature. Third, they note what the recipe does not say: serving dishes, resting time, how long the whole process actually takes from start to table.
That mental walkthrough is worth more than any culinary skill. It turns a recipe from a set of instructions you chase into a plan you control.
The ten minutes you spend reading are cheaper than the forty minutes you spend restarting.
Pick one and break it down
The action step for this module is deliberately simple. Choose a recipe you want to cook, something you have been meaning to try or something you already make but have never planned out on paper. Before you go near the kitchen, write down what it requires: ingredients, equipment, prep steps, cooking steps, and the temperatures that matter. That written breakdown is your proof that you can read a recipe as a plan rather than following it one line at a time.
The reading for this module
This is the core reading for the module. Take it with your earlier work beside you.
Break a recipe into its parts.
Pick one recipe you want to learn. Before touching the stove, break it into its parts: what you need, what happens before heat, what happens during cooking, and what the finish-line temperatures are.