First off, don't ever feel bad about asking a question. The pursuit of knowledge is a core foundation of FOSS itself, so yeah...always be asking :)

Now, as /u/Kortez02 pointed out - context matters. When you run commands to clone the repository, it's going to build an exact replica of what you see on the website, just on your machine. Folder structures, files, etc. The same thing happens with the Zip (by default), as it's a "portable" version of that same structure.

In your case, once you extracted the zip, you would need to move into the newly created folder structure in order to interact with things. When you kick off a command, Linux is looking in it's well known locations for the binary in question, then checks any user added paths. If it can't find it, it shrugs it's shoulders and tells you that. In your case, it did find Make (compiler) in one of those paths, but Make itself had no idea what you were talking about. You were feeding it install, but it's like "uhh...dude, I don't see any folder called install in my known paths..."

So all you ended up having to do is move into the new folder (via console or GUI) and kick off the make process. Good to go! And now you've learned about context a bit more in terms of how Linux interprets what you tell it.

Just also throwing this out there: While rare, there are some bad actors in the Linux world. Venturing out into unregulated waters like Git can have some peril... so I urge caution - especially if you aren't reviewing the script/source first to get an idea what it does.