===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/62.html,v
retrieving revision 1.92
retrieving revision 1.93
diff -u -r1.92 -r1.93
--- www/62.html	2019/05/27 22:55:18	1.92
+++ www/62.html	2019/06/01 22:54:16	1.93
@@ -296,8 +296,8 @@
 	<a href="https://man.openbsd.org/freezero.3">freezero(3)</a>
 	to easily clear and free memory holding sensitive data has been added.
     <li>Double free detection has been improved when the F
-    	<a href="https://man.openbsd.org/malloc.3">malloc(3)</a> option is used.
-    	The existing S option now includes F.
+	<a href="https://man.openbsd.org/malloc.3">malloc(3)</a> option is used.
+	The existing S option now includes F.
     <li>The <a href="https://man.openbsd.org/tty.4#TIOCSTI">TIOCSTI</a>
 	tty ioctl has been removed.  The I/O-loops in the last two consumers
 	<a href="https://man.openbsd.org/csh.1">csh(1)</a> and
@@ -342,10 +342,10 @@
     <li>Achieve higher levels of paranoia regarding structure packing, and
         clear many kernel objects before passing to userland.
     <li>Disable some optimizations in 
-    	<a href="https://man.openbsd.org/clang.1">clang(1)</a>
+	<a href="https://man.openbsd.org/clang.1">clang(1)</a>
 	due to incompatibility with security.
     <li>For instance, cope with 
-    	<a href="https://man.openbsd.org/clang.1">clang(1)</a>'s assumption 
+	<a href="https://man.openbsd.org/clang.1">clang(1)</a>'s assumption 
 	that static or const
         objects placed in unknown sections (such as .openbsd.randomdata)
         are surely always 0, and therefore such memory accesses can be