Software licenses try to avoid ambiguity, which results in them being rather lengthy and hard to read. Would I be okay with flippantly summarizing the gist or spirit of a license in another place (like a code file)? I don't want the summery to be binding in any way.
Something like this for instance, which refers to the actual license text at the very end?
// legal: // This code is free to use for any purpose. // I don't promise this code will do anything right or nothing wrong, // and is given "as is", see license.txt