svn commit: r307639 - head

[Warner Losh]

Author: imp
Date: Wed Oct 19 15:13:08 2016
New Revision: 307639
URL: https://svnweb.freebsd.org/changeset/base/307639

Log:
  After deeper software archaeology, reports that 10.3R was affected
  turned out to be mistaken. Adjust the entry and fix a few typos.

Modified:
  head/UPDATING

Modified: head/UPDATING
==============================================================================
--- head/UPDATING	Wed Oct 19 14:51:25 2016	(r307638)
+++ head/UPDATING	Wed Oct 19 15:13:08 2016	(r307639)
@@ -29,21 +29,22 @@ NOTE TO PEOPLE WHO THINK THAT FreeBSD 12
 	machines to maximize performance.  (To completely disable malloc
 	debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
 	disable the most expensive debugging functionality run
-	"ln -s 'abort:false,junk:false' /etc/malloc.
+	"ln -s 'abort:false,junk:false' /etc/malloc.conf".)
 
 
 ****************************** SPECIAL WARNING: ******************************
 
 	Due to a bug in some versions of clang that's very hard to workaround in
 	the upgrade process, to upgrade to -current you must first upgrade
-	either stable/9 after r286035 or stable/10 after r286033 or current
-	after r286007 (including stable/11 and 11.0-RELEASE). These revisions
-	post-date 10.3-RELEASE and 9.3-RELEASE, so you'll need to take the
-	unusual step of upgrading to the tip of the stable branch before moving
-	to 11 or -current via a source upgrade.  stable/11 and 11.0-RELEASE
-	post-date the fix so you can move from them to -current. This differs
-	from the historical situation where one coule upgrade from anywhere on
-	the last couple of stable branches, so be careful.
+	either stable/9 after r286035 or stable/10 after r286033 (including
+	10.3-RELEASE) or current after r286007 (including stable/11 and
+	11.0-RELEASE). These revisions post-date the 10.2 and 9.3 releases, so
+	you'll need to take the unusual step of upgrading to the tip of the
+	stable branch before moving to 11 or -current via a source upgrade.
+	stable/11 and 11.0-RELEASE post-date the fix so you can move from them
+	to -current. This differs from the historical situation where one could
+	upgrade from anywhere on the last couple of stable branches, so be
+	careful.
 
 ****************************** SPECIAL WARNING: ******************************