Update

LICENSE

@@ -8,8 +8,8 @@ For comments, corrections and updates, please contact [email protected]
 
 	Parts of Mono are dual licensed, they are available to the
 	public in GPL or LGPL forms, but we also offer those pieces
-	under commercial terms from Novell for when the GPL and the
-	LGPL are not suitable.
+	under commercial terms from Xamarin for the cases wher the GPL
+	and the LGPL are not suitable.
 
 	We have tried to pick the licenses that will maximize adoption
 	of Mono, so we tend to use the MIT X11 or LGPL liceses.
@@ -22,6 +22,9 @@ For comments, corrections and updates, please contact [email protected]
 	Contributions for other modules should be under the same license
 	terms as the rest of the module, or under MIT X11 terms. 
 
+	For the actual license links in the Mono distribution see the
+	bottom of this file.
+
 	If you need further information, please contact [email protected]
 
 * The Modules
@@ -31,15 +34,15 @@ For comments, corrections and updates, please contact [email protected]
 	This code is dual licensed under the LGPL or commercial licenses. 
 
 	The LGPL ensures that Mono can be used in most scenarios, but
-	gives Novell the flexibility to relicense the code for
+	gives Xamarin the flexibility to relicense the code for
 	embedded systems, static linking or commercial settings where
 	the LGPL can not be used.
 
 	We consider non-LGPL use instances where you use this on an
 	embedded system where the end user is not able to upgrade the
 	Mono VM or Moonlight installation or distribution that is part
 	of your product (Section 6 and 7), you would have to obtain a
-	commercial license from Novell (consider software burned into
+	commercial license from Xamarin (consider software burned into
 	a ROM, systems where end users would not be able to upgrade,
 	an embedded console, a game console that imposes limitations
 	on the distribution and access to the code, a phone platform