Inconsistent syntax for exporting functions

[Sequoia]

Some do this:

function repeat(operation, num) {
  // SOLUTION GOES HERE
}
module.exports = repeat

Some do this:

module.exports = function(input) {
  // SOLUTION GOES HERE
}

Some do this:

module.exports = function getShortMessages(messages) {
  // SOLUTION GOES HERE
}

There's not a functional issue here, and maybe these are intentionally written to expose the learner to multiple syntaxes for CommonJS exports, but I think this could trip up & confuse a beginner: "Why are there three ways to do this? Which one's better?" etc..

In my opinion either:
a) an explanation of modules/exports & their syntax should be included early on (probably via a lesson) or
b) these should all be standardized to one syntax, so the learner can focus on the lesson at hand and not "why is this boilerplate different from the last lesson"

I'm happy to fix these up and create a PR if such a change is welcome - just let me know. 👍

[timoxley]

@Sequoia thanks for the feedback! I think this is valid, I'd accept a PR for the first style if you wanted to submit it 👍

[Sequoia]

Will do this week, thanks for quick follow up!

[Sequoia]

Waiting for #43 to land or get rejected to do this one. (In that PR, I rename all the files in question in this issue).

[timoxley]

@Sequoia done