Fix mac os spelling

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@24171 91177308-0d34-0410-b5e6-96231b3b80d8

diff --git a/docs/ReleaseNotes.html b/docs/ReleaseNotes.html
index 430200b..f557b12 100644 (file)
--- a/docs/ReleaseNotes.html
+++ b/docs/ReleaseNotes.html
@@ -64,7 +64,7 @@ href="http://llvm.org/releases/">releases page</a>.</p>
 release incorporates a large number of enhancements and additions (primarily in
 the code generator), which combine to improve the quality of the code generated
 by LLVM by up to 30% in some cases.  This release is also the first release to
-have first-class support for Mac OS/X: all of the major bugs have been shaken
+have first-class support for Mac OS X: all of the major bugs have been shaken
 out and it is now as well supported as Linux on X86.</p>
 
 </div>
@@ -172,7 +172,7 @@ this case, using "<tt>llc -march=ppc32 -mcpu=g5 -mattr=-altivec</tt>".</p>
     giving up completely.  In addition, <a href="http://llvm.org/PR576">the JIT
     debugging mode of bugpoint is much faster</a>.</li>
   <li>LLVM now includes Xcode project files in the llvm/Xcode directory.</li>
-  <li>LLVM now supports Mac OS/X on Intel.</li>
+  <li>LLVM now supports Mac OS X on Intel.</li>
   <li>LLVM now builds cleanly with GCC 4.1.</li>
 </ol>
 </div>
@@ -193,7 +193,7 @@ this case, using "<tt>llc -march=ppc32 -mcpu=g5 -mattr=-altivec</tt>".</p>
       we find that it often speeds up programs from 10-40% depending on the
       program.</li>
   <li>The code produced when exception handling is enabled is far more
-      efficient in some cases, particularly on Mac OS/X.</li>
+      efficient in some cases, particularly on Mac OS X.</li>
 </ol>
 </div>
 
@@ -229,7 +229,7 @@ this case, using "<tt>llc -march=ppc32 -mcpu=g5 -mattr=-altivec</tt>".</p>
 <div class="doc_text">
 <ol>
   <li>A vast number of bugs have been fixed in the PowerPC backend and in
-      llvm-gcc when configured for Mac OS/X (particularly relating to ABI
+      llvm-gcc when configured for Mac OS X (particularly relating to ABI
       issues).  For example:
       <a href="http://llvm.org/PR603">PR449</a>,
       <a href="http://llvm.org/PR594">PR594</a>,