Post History
The GNU site itself treats the name of the Make utility as an uppercased word: https://www.gnu.org/software/make/ There does seem to be a convention to frequently use make (the command) where Make...
Answer
#4: Attribution notice removed
Source: https://writers.stackexchange.com/a/23420 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#3: Attribution notice added
Source: https://writers.stackexchange.com/a/23420 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision
The GNU site itself treats the name of the Make utility as an uppercased word: [https://www.gnu.org/software/make/](https://www.gnu.org/software/make/) There does seem to be a convention to frequently use `make` (the command) where Make (the name) would seem more appropriate. The GNU Make manual seems to do this almost exclusively ([https://www.gnu.org/software/make/manual/make.html](https://www.gnu.org/software/make/manual/make.html)) but always with a font change to indicate that it is the command that is being used. So those examples would justify the second and third options for Make, though the manual seems to avoid using `make` at the beginning of a sentence. It is less clear that `cp` or `cat` can be treated this way, though. They are commands more than stand-alone products like Make. I'd be inclined to avoid using them as stand alone names and instead use "The `cat` command" as in: > The `cat` command is used to concatenate files.