From 57132e88b7c3c8a4b2df063b92607e46c46dc846 Mon Sep 17 00:00:00 2001
From: Chris Lattner <sabre@nondot.org>
Date: Sat, 23 Jul 2011 17:18:57 +0000
Subject: [PATCH] how about that, StringRef doesn't allow any mutation, thanks
 to Frits for straightening me out.

llvm-svn: 135856
---
 llvm/docs/ProgrammersManual.html | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/llvm/docs/ProgrammersManual.html b/llvm/docs/ProgrammersManual.html
index 8e9141445afe..266c033bb4c4 100644
--- a/llvm/docs/ProgrammersManual.html
+++ b/llvm/docs/ProgrammersManual.html
@@ -1280,10 +1280,10 @@ something like that).</li>
 method if the method "computes" the result string.  Instead, use
 std::string.</li>
     
-<li>StringRef's allow you to mutate the pointed-to string bytes, but because it
-doesn't own the string, it doesn't allow you to insert or remove bytes from
-the range.  For editing operations like this, it interoperates with the
-<a href="#dss_twine">Twine</a> class.</li>
+<li>StringRef's do not allow you to mutate the pointed-to string bytes and it
+doesn't allow you to insert or remove bytes from the range.  For editing 
+operations like this, it interoperates with the <a 
+href="#dss_twine">Twine</a> class.</li>
 </ol>
   
 <p>Because of its strengths and limitations, it is very common for a function to