Commit b0787c994b7c12e6b51f258a839d66d5c061adfb

Thomas de Grivel 2024-10-14T20:54:12

remove syntax highlighting from LICENSE.md

diff --git a/LICENSE.md b/LICENSE.md
index 90ee1e8..4cffb94 100644
--- a/LICENSE.md
+++ b/LICENSE.md
@@ -289,6 +289,7 @@ If you develop a new program, and you want it to be of the greatest possible use
 
 To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the “copyright” line and a pointer to where the full notice is found.
 
+```plaintext
     <one line to give the program's name and a brief idea of what it does.>
     Copyright (C) <year>  <name of author>
         
@@ -305,13 +306,16 @@ To do so, attach the following notices to the program. It is safest to attach th
     You should have received a copy of the GNU General Public License
     along with this program.  If not, see <https://www.gnu.org/licenses/>.
     Also add information on how to contact you by electronic and paper mail.
+```
 
 If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode:
-    
+
+```plaintext
     <program>  Copyright (C) <year>  <name of author>
     This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
     This is free software, and you are welcome to redistribute it
     under certain conditions; type `show c' for details.
+```
 
 The hypothetical commands 'show w' and 'show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an “about box”.
 
@@ -319,6 +323,7 @@ You should also get your employer (if you work as a programmer) or school, if an
                                                                 
 The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read <https://www.gnu.org/licenses/why-not-lgpl.html>.
 
+
 ## Others
 
 See the LICENSE file in subdirectories.