Jordan points out that this was incorrect: clang should recover from
*errors* with fixits on them by following the recovery advised by the
fixit, but if it is a fixit on a warning, then obviously the AST
should be for the code as-written.
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@159980 91177308-0d34-0410-b5e6-96231b3b80d8
diff --git a/docs/InternalsManual.html b/docs/InternalsManual.html
index 6a67368..38cd849 100644
--- a/docs/InternalsManual.html
+++ b/docs/InternalsManual.html
@@ -453,8 +453,7 @@
<li>Since they are automatically applied if <code>-Xclang -fixit</code>
is passed to the driver, they should only be used when it's very likely they
match the user's intent.</li>
-<li>Clang must recover from the error or warning as if the fix-it had been
-applied.</li>
+<li>Clang must recover from errors as if the fix-it had been applied.</li>
</ul>
<p>If a fix-it can't obey these rules, put the fix-it on a note. Fix-its on