quotes direction

1 files changed, 2 insertions, 2 deletions

diff --git a/index.html b/index.html
index 3b1cded..673d756 100644
--- a/index.html
+++ b/index.html
@@ -44,7 +44,7 @@
 				<h3>A Lisp-like Operating System</h3>
 				<p>Anybody who has tried functional programming knows that Lisp and <a href="https://haskell.org">Haskell</a> are special and great programming languages.  Most Lispers and all Haskell programmers adhere to the functional style of programming, creating mathematically-provably-correct programs.  I love the fact that Haskell supports Monads well and that it's statically typed (having the debugger find your issues is much more comfortable than debugging mid-run, while it's true that <a href="https://ghc.haskell.org">GHC</a> has quite good debugging utilities.  On the other hand, Haskell and Common Lisp have so many pragmatics and syntax sugar.  Scheme (which I consider to be a dialect of Lisp) is much more uniform and symmetric (think of group theory) in syntax, but has bad support for lazy evaluation.</p>
 				<p>There are many modern operating systems, for example the BSDs, GNU+Linux, Plan 9, etc.  (Microsoft Windows and macOS don't count, they're nonfree.)   But security issues are discovered every year in each of them, even <a href="https://OpenBSD.org">OpenBSD</a>, which is considered the most secure operating system for general use.  A lot of this has to do with the programming language they're written in, C.</p>
-				<p>In C, you've got a heap of pointers, memory stacks, arrays, linked lists, structures, etc. that you all have to manage by yourself.  This leaves huge gaps for programmer error.  By contrast, it is possible to mathematically prove the correctness (or the lack thereof, though I only use "Possible" because of Godel Incompleteness) of a functional program.  This eases the work for programmers.</p>
+				<p>In C, you've got a heap of pointers, memory stacks, arrays, linked lists, structures, etc. that you all have to manage by yourself.  This leaves huge gaps for programmer error.  By contrast, it is possible to mathematically prove the correctness (or the lack thereof, though I only use &ldquo;Possible&rdquo; because of Godel Incompleteness) of a functional program.  This eases the work for programmers.</p>
 				<p>Most, if not all security issues in programs written in classical imperative programming languages are with bogus stacks, pointers, etc.  There are countless times when stack overflows are used in attacks.  By using functional languages, it just works!</p>
 				<p>There have been <a href="http://metamodular.com/Common-Lisp/lispos.html">great proposals by other people</a> on this ideea.  If you are into operating system development and programming in general, please read it, and share your thoughts with me.  If many people voice on this issue, I'll start an mailing list.</p>
 				<h3>What about a pure functional Lisp dialect, with monads and similar (Haskell) ideas?</h3>
@@ -78,7 +78,7 @@
 			</div>
 		</div>
 		<div id="footer">
-			<p>This is free and unencumbered software released into the public domain.  Anyone is free to copy, modify, publish, use, compile, sell, or distribute this software, either in source code form or as a compiled binary, for any purpose, commercial or non-commercial, and by any means.  In jurisdictions that recognize copyright laws, the author or authors of this software dedicate any and all copyright interest in the software to the public domain. We make this dedication for the benefit of the public at large and to the detriment of our heirs and successors. We intend this dedication to be an overt act of relinquishment in perpetuity of all present and future rights to this software under copyright law.  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.  For more information, please refer to <a href="https://unlicense.org/">https://unlicense.org</a></p>
+			<p>This is free and unencumbered software released into the public domain.  Anyone is free to copy, modify, publish, use, compile, sell, or distribute this software, either in source code form or as a compiled binary, for any purpose, commercial or non-commercial, and by any means.  In jurisdictions that recognize copyright laws, the author or authors of this software dedicate any and all copyright interest in the software to the public domain. We make this dedication for the benefit of the public at large and to the detriment of our heirs and successors. We intend this dedication to be an overt act of relinquishment in perpetuity of all present and future rights to this software under copyright law.  THE SOFTWARE IS PROVIDED &ldquo;AS IS&rdquo;, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.  For more information, please refer to <a href="https://unlicense.org/">https://unlicense.org</a></p>
 			<p>I know that this website is not a program and that HTML isn't considered a programming language.  Nevertheless, you can think of the HTML as code&mdash;even the plain text I write could also be considered code since languages are a code to give information.  Anyways, stuff on here that's supposed to be public (don't try to spoof my htaccess, don't hack my ssh, don't snoop on my email, etc) is public domain, including my projects and my git repos, unless otherwise specified by a file that looks like COPYING, LICENSE or licensing stuff in the source itself. <a href="https://stpeter.im/writings/essays/publicdomain.html">https://stpeter.im/writings/essays/publicdomain.html</a> is a good explanation on why people put stuff in the public domain.  However, you might want to see the GNU AGPL section on this page.</p>
 		</div>
 		<div id="memes">