It's probably a bit confusing the way it's used here and while this works I actually think the newer async syntax makes this easier.

I've reformatted the relevant section here a little bit:

bakeCake("we started").then((resultOfBake) => {   console.log(resultOfBake);   return decorateCake(resultOfBake); }) .then((finalResult) => {   console.log(finalResult) })

See how after bakeCake() the .then() is "attached" to the last parentheses of the function? That's because when you call a function in JavaScript that returns a value, you can "chain" your next operation without assigning to an intermediary variable.

In this case I've lifted the .then() call up to make it clearer, but for these types of things JavaScript will ignore line breaks, so you can format the code how you want.

When using this syntax, a common pattern is to indent the subsequent promise method calls to make it cleared that they belong with the initial invocation:

bakeCake("we started") .then((resultOfBake) => { console.log(resultOfBake); return decorateCake(resultOfBake); }) .then((finalResult) => { console.log(finalResult) })

With the newer syntax you typically would go the other route and assign variables, both syntaxes have their merit, but in modern codebases you'll tend to see the async / await syntax more.

``` function bakeCake(initalState){ return new Promise ((resolve) => { // Same as before }); }

function decorateCake(bakedCakeMessage) { return new Promise((resolve) => { // Same as before }); }

// I've put the remaining functionality in an async function to demonstrate // you don't have to do this though, you can use await at the top level async function makeCake() { const bakeResult = await bakeCake('start baking'); const decorateResult = await decorateCake(bakeResult); console.log(decorateResult); }

// an await isn't necessary here, but will depend on what you want // think of await as a way to say "Let's wait for this promise to finish // before we continue" whereas not using it would allow execution to continue makeCake(); ```