I'm very soon going to submit my master's thesis, which consists of a manuscript and code. I plan to publish the code with an MIT license on a public GitHub repository. Because the manuscript also serves as conceptual, scientific and technical documentation to the code (a long whitepaper of sorts, if you will), I would like to add the manuscript to the GitHub repository. However, I'm concerned that doing so would effectively publish my manuscript under the MIT license as well, as that makes explicit mention of (emphasis mine):
[...] this software and associated documentation files [...]
Correct me if I'm wrong, but I feel like publishing the manuscript under the MIT license would not be desirable - I don't think you'd want "copying, merging, publishing, distributing, sublicensing and/or selling copies of" a scientific document "without restriction". (Not that I think my manuscript is so extraordinary that anyone would try to sell it.)
Are my concerns about the manuscript being included in the MIT license unfounded, one way or the other? If not, what would be the right approach in this case? Should I add an explicit exemption for the manuscript to the license, or should I include an additional license just for the manuscript, and if so, which one? Thank you for your time.