I hear you; it was my intent to put `displaySuccessMessage` and `handleErrors` at the same level: end of promise chain loggers, one for success, one for error. People are going to need to read more about promises anyway to wrap their heads around common patterns/gotchas, but I think we're doing people less of a disservice by constructing the example this way than to through in a `null, handleErrors` and spend another paragraph talking about promise gotchas when a cursory overview is the goal.