I recommend Kyle Michell's Fast Path [0] terms. I'll grant that I'm familiar with Michell's work, but haven't read these particular terms. Kyle Michell publishes 'plain language' licenses. For example, compare how Blue Oak Model [1] and MIT [2] grant permission. Obviously, Michell has the benefit of lots of discourse following the induction of MIT's license and indicates a link can substitute for the full license text. I highlight this, not to argue for Blue Oak, but to indicate that Michell's Fast Path terms likely take half the space of typical software terms.

``` Blue Oak Model

Each contributor licenses you to do everything with this software that would otherwise infringe that contributor’s copyright in it.

You must ensure that everyone who gets a copy of any part of this software from you, with or without changes, also gets the text of this license or a link to https://blueoakcouncil.org/license/1.0.0.

``` MIT

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

[0] https://fastpathlicense.com/

[1] https://blueoakcouncil.org/license/1.0.0

[2] https://opensource.org/license/MIT