From: Nick Lewycky <nicholas@mxc.ca>
Date: Wed, 26 May 2010 21:48:10 +0000 (+0000)
Subject: Grammar fix: s/it's/its/g in
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=77561e584ac4dc4041cc8ff65fbb92dcb1a8f2ec;p=clang

Grammar fix: s/it's/its/g in
  "it's spelling location and it's instantiation location"


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

diff --git a/docs/InternalsManual.html b/docs/InternalsManual.html
index daec6b0194..5ef5dd842a 100644
--- a/docs/InternalsManual.html
+++ b/docs/InternalsManual.html
@@ -532,12 +532,12 @@ source code of the program.  Important design points include:</p>
 </ol>
 
 <p>In practice, the SourceLocation works together with the SourceManager class
-to encode two pieces of information about a location: it's spelling location
-and it's instantiation location.  For most tokens, these will be the same.  However,
-for a macro expansion (or tokens that came from a _Pragma directive) these will
-describe the location of the characters corresponding to the token and the
-location where the token was used (i.e. the macro instantiation point or the 
-location of the _Pragma itself).</p>
+to encode two pieces of information about a location: its spelling location
+and its instantiation location.  For most tokens, these will be the same.
+However, for a macro expansion (or tokens that came from a _Pragma directive)
+these will describe the location of the characters corresponding to the token
+and the location where the token was used (i.e. the macro instantiation point
+or the location of the _Pragma itself).</p>
 
 <p>The Clang front-end inherently depends on the location of a token being
 tracked correctly.  If it is ever incorrect, the front-end may get confused and